439 件 ・ 関連度順
概要と使いどころ
Update the application tracker. Record replies (rejection, screening, interview, offer), log an application the user made by hand, or sweep the inbox for replies. Use when the user runs /seekter-log, says a company replied or rejected them, or asks to check emails for responses.
日本語の概要は準備中です。原文の説明を表示しています。
Summarise the job search from the markdown tracker - funnel, response rate, what's working, where applications come from, what's pending on the user. Use when the user runs /seekter-report or asks how the search is going, for weekly numbers, or what to change.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.
日本語の概要は準備中です。原文の説明を表示しています。
Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available. Not for browsing the existing issue tracker. Use oss-find-issue for that.
日本語の概要は準備中です。原文の説明を表示しています。
Booking & Calendar CRO Engine — Packages all booking, scheduling, .ics download, and Google Calendar integration into a revenue-boosting system. Auto-detect industry → select matching pattern → generate calendar engine + booking UI + export logic. Integrates with cm-google-form (form → sheet) and cm-ads-tracker (conversion events). ALWAYS trigger for: booking, appointment, calendar, reminder, download ics, google calendar, add to calendar, book appointment, schedule, "create booking", "add scheduling", "appointment reminder system", "calendar CRO", "reduce no-show"
日本語の概要は準備中です。原文の説明を表示しています。
Bottom-sheet and popup growth system: booking CTAs, calendars, lead capture, surveys, re-engagement, with CRO tracking hooks. Zero-deps; works static or dynamic sites. Works with cm-booking-calendar, cm-ads-tracker, cm-google-form, cm-readit, cm-ux-master.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end ad conversion tracking: Meta Pixel+CAPI, TikTok Events API, Google Ads Enhanced Conversions, GTM, attribution. Auto-detects industry, maps standard events, outputs a developer-ready implementation doc. Use for pixels, GTM, CAPI, ROAS, or 'set up tracking' requests.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Claude Code --channels sessions (start/stop/status/health) via channel-manager.cjs and terminal-tracker.cjs.
日本語の概要は準備中です。原文の説明を表示しています。
Report a problem with the open-pr plugin itself, or ask for a change, on its public issue tracker. Use when a run of one of its commands left something to say. Takes no URL.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Claude Code sessions — search by topic or ID, browse recent sessions with full metadata (tags, summaries, titles, cost), view title/nickname history timelines, resume in Ghostty tabs, spawn interactive or headless sessions, monitor live sessions, and bootstrap new setups. Triggers on resume session, find session, list sessions, recent sessions, spawn session, session history, what was I working on, open in ghostty, title history, session nicknames.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used to search, inspect, list, and recover local Codex sessions through Codex's native App Server APIs. Trigger for requests such as find a prior Codex conversation, search Codex transcript text, list recent Codex work, locate matches inside a session, or produce a safe Codex resume command. Do not use for Claude Code sessions, project source-code search, or web search.
日本語の概要は準備中です。原文の説明を表示しています。
When a LinkedIn prospect connects, updates their status in the master tracker, creates their outreach message file, and generates a ready-to-post comment on their latest post.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don't use for bulk issue reconciliation or multi-issue sweeps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human explicitly requests the daily on-call issue digest from a named issue tracker for a configured Slack channel. Not for posting without explicit human authorization for that run.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to elicit refused directions, generalize them, and close matching tracker items as not planned. Not for duplicates, spam, or items closed as completed or obsolete.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
日本語の概要は準備中です。原文の説明を表示しています。
从游戏客户端（安装包/APK/IPA/EXE 或 dump.cs、lua、usmap、抓包等）反推服务端协议并复现可部署服务端。含阅读路径分派、原理层(primer：三要素/数据包协议/协议表/热更源码)、四阶段路线图(workflow-roadmap：静态分析→建工具+登录链→重定向→补包循环→清单迭代)、11 种反推方法选择器（含内联服务端路线）、接口清单提取器（tools/）、协议规格模板(protocol.spec.yaml)、wire 级定点改写（不等 schema 齐就能跑）、客户端地址来源清查、三轴状态与验收体系、发布运维清单、进度清单(TRACKER.md)、登录链条与功能清单模板。覆盖：账号登录注册、房间匹配、战斗、掉落物资、抽卡、充值与邮件、部署(本地/服务器/Termux/Windows)、客户端对接、闭环验证；并支持 Unity(IL2CPP/Mono/Lua)、Unreal(UE4/UE5)、Cocos2d-x/Cocos Creator(JS/Lua 热更)、C#、AS3、Java、JS 等客户端；含进服后的 Live 运营手册；并含「内联服务端」路线（客户端进程内合成响应、运行时对象合成与字段发现、平台 SDK 登录态复用与目录服/区服两段准入）。
日本語の概要は準備中です。原文の説明を表示しています。
Uses OpenSEO as the measured SEO data plane for keyword volume and difficulty, SERPs, ranked keywords, backlinks, local SEO, rank tracking, Search Console, GA4, and site audits. Use for measured SEO metrics, indexing evidence, organic analytics, local rankings, backlink profiles, or rank trackers. Prefer OpenSEO over guessed metrics when connected; otherwise continue with qualitative web research and mark numeric metrics unknown.
日本語の概要は準備中です。原文の説明を表示しています。
Create high-quality, SEO-optimized content that ranks AND reads like a human wrote it. Performs live SERP gap analysis, writes with anti-AI detection techniques, and adds schema markup. Use when someone needs a blog post, article, SEO page, or wants content that drives search traffic. Triggers on 'SEO content', 'blog post', 'article', 'SERP', 'programmatic SEO', 'content at scale', 'template pages at scale', 'write a post about', 'rank for', or 'search-optimized content'. Two modes: single article or programmatic SEO at scale. Owns programmatic SEO and content-at-scale generation. For a single alternatives or vs/comparison page, see /competitor-alternatives; for a multi-phase page roadmap with a persistent tracker, see /seo-machine.
日本語の概要は準備中です。原文の説明を表示しています。
Creates high-converting 'X vs Y' and 'X alternatives' SEO pages that capture comparison search traffic. Researches competitors, writes honest comparison content, and adds schema markup (FAQPage, ItemList). Use when someone needs alternatives pages, comparison content, or says 'alternatives page', 'vs page', 'comparison', 'competitor alternatives', 'X vs Y page', or wants to capture competitor brand search traffic with SEO content. Also trigger when someone wants to rank for competitor brand names, capture competitor search traffic, create a compare page, or build a competitive content hub. Even if they just say 'how do we compete with X' or 'we need to show up when people search for [competitor]', this skill applies. Owns the individual alternatives / vs / comparison page. For a batch roadmap of many pages with a phase tracker, see /seo-machine. For programmatic SEO and templated content at scale, see /seo-content.
日本語の概要は準備中です。原文の説明を表示しています。
Use Symphony's generated typed Linear tools for tracker workflow actions. Provides Linear capability semantics and workpad rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use Symphony's generated typed TAPD tools for tracker workflow actions. Provides TAPD capability semantics and workpad rules.
日本語の概要は準備中です。原文の説明を表示しています。
资金行为分析师（金向北）。擅长北向资金行为、机构持仓变动、基金重仓与拥挤度、资金共识方向判断。 在 A 股研究团队中由主理人调度，参与 Workflow 1 / Workflow 2 / Workflow 3 / Workflow 4 / Workflow 5 / Workflow 6。 擅长：北向资金净流入趋势、重点加仓/减仓方向、外资风格偏好、机构持仓变动（社保/险资/QFII 新进退出、十大股东变化）、基金重仓行业配置比例、拥挤度指标、三路资金共识图谱（北向×机构×公募×盘面主线交叉验证）、区分趋势性信号和短期交易噪音。
日本語の概要は準備中です。原文の説明を表示しています。