2,773 件 ・ 関連度順
概要と使いどころ
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
日本語の概要は準備中です。原文の説明を表示しています。
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
日本語の概要は準備中です。原文の説明を表示しています。
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
日本語の概要は準備中です。原文の説明を表示しています。
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
日本語の概要は準備中です。原文の説明を表示しています。
Fetch external documents linked in SCF submissions — Google Docs, Google Drive PDFs, GitHub, Notion, IPFS. Use when a submission links to an architecture doc, whitepaper, or technical spec hosted externally. Handles URL transformation for Google services.
日本語の概要は準備中です。原文の説明を表示しています。
VenTu is a static export on GitHub Pages — no Node runtime at request time. Use when adding routes, auth, alerts, forms, API endpoints, or anything that could depend on a server.
日本語の概要は準備中です。原文の説明を表示しています。
Downloads CARLA so nothing has to be fetched by hand — an official release package for any published version (resolved live from the GitHub releases, with AdditionalMaps), the rolling nightly Dev build, a shallow source checkout of a branch or tag, or the carlasim/carla Docker image. Reports exactly what was obtained and where, plus the environment variables the other skills read. Use when the user asks to "download CARLA", "get CARLA 0.9.16", "install CARLA", "clone the carla repo", "fetch the latest CARLA", or has no CARLA at all yet.
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses and fixes CI failures and re-runs GitHub Actions jobs. Use when CI is failing, tests break in CI, lint errors block merging, a build fails, or jobs need re-running.
日本語の概要は準備中です。原文の説明を表示しています。
Create an implementation plan and a GitHub Issue based on the task description provided as an argument. Use this when the user supplies a natural-language task description (not an issue number) and wants a new implementation-ready Issue. If the input is an existing issue number, use create-issue-from-issue-number (re-analyze) or update-issue (reflect comments) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.
日本語の概要は準備中です。原文の説明を表示しています。
Execute tasks based on GitHub Issue content
日本語の概要は準備中です。原文の説明を表示しています。
INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by breakdown-issues. It formats a scope GitHub Issue body (label cc-triage-scope, used before code analysis), runs the pre-posting checklist, and executes `gh issue create`. Invoke this skill ONLY from one of the parent skills via the Skill tool, after the parent has finalized the task breakdown. If a user asks to 'create a scope issue' or similar, route them to the parent skill (/breakdown-issues) rather than invoking this one directly.
日本語の概要は準備中です。原文の説明を表示しています。
Triage a single GitHub PR by PR number. Check out the PR's branch, detect conflicts with the target branch via `gh pr status` (and label the PR with `cc-resolve-conflict` if any are found), collect unresolved review comments and CI status and judge only whether each item must be fixed, then take action (add cc-fix-onetime label if fixes are needed; if release-ready, add cc-release-ready label for an Epic PR marked `cc-epic-issue` instead of merging, otherwise merge the PR).
日本語の概要は準備中です。原文の説明を表示しています。
Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.
日本語の概要は準備中です。原文の説明を表示しています。
Re-analyze an existing GitHub Issue using its current title and body, refresh the implementation plan against the latest code state, and update the Issue in place. Use when the user provides an Issue number (numeric, `#`-prefixed, or Issue URL) and wants to regenerate the code analysis via the explore-agent subagent. For reflecting comment-driven updates, use update-issue. For creating a brand-new Issue from a natural-language task description, use create-issue.
日本語の概要は準備中です。原文の説明を表示しています。
INTERNAL/HELPER skill — do NOT invoke directly from a user query. This is the shared formatter/poster used by create-issue, create-issue-from-issue-number, and update-issue. It formats an implementation-ready GitHub Issue body, runs the pre-posting checklist, executes `gh issue create` or `gh issue edit`, and optionally posts a 確認事項 follow-up comment. Invoke this skill ONLY from one of the three parent skills via the Skill tool, after the parent has completed analysis. If a user asks to 'format an issue body' or similar, route them to the appropriate parent skill (/create-issue, /create-issue-from-issue-number, or /update-issue) rather than invoking this one directly.
日本語の概要は準備中です。原文の説明を表示しています。
Builds an interactive HTML dashboard visualizing the Agent Skills ecosystem by fetching live data from github.com/agentskills/agentskills. Use this skill whenever the user wants to explore, research, or visualize Skills architecture, the SKILL.md spec, ecosystem adoption, repo stats, or any Skills intelligence dashboard. Trigger when the user mentions "skills dashboard", "skills ecosystem", "skills architecture overview", "agentskills repo", or wants to analyze how different tools implement Agent Skills. Optimized for Perplexity Computer — Computer fetches all data live, no static files required.
日本語の概要は準備中です。原文の説明を表示しています。
Gate a build on browser fingerprint regressions with liarjs - save a baseline scan as JSON, diff later runs against it, and fail the job when the consistency score falls below a floor. Use when asked to add a fingerprint or headless-detection check to GitHub Actions, GitLab CI or another pipeline, to catch a regression in a Chromium build or scraping harness before it ships, or to track how a fingerprint score changes across commits.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks which PRDs exist — 'listar PRDs', 'quais PRDs temos', 'list PRDs' — with status, version, roadmap state and GitHub Project. Read-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user, inside an Orca terminal, asks Hermes to resolve, dispatch, orchestrate or supervise GitHub issues with Orca workers — 'orquestrar as issues 12, 15 e 18 no Orca', 'despachar as issues com label ready', 'coordenar workers do Orca para estas issues', or to resume such a Run after compaction. Do NOT use for a single unsupervised hand-off to another agent (Orca CLI directly), for working on one issue in this session (pwdev-feat feat-loop), or outside Orca.
日本語の概要は準備中です。原文の説明を表示しています。
Verify and configure the development environment — GitHub account, org membership, and marketplace access. Run once per staff member, or re-run to diagnose issues.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for adding new OAuth-based integrations to Fabric. Use when implementing OAuth providers like Microsoft Teams, GitHub, Google Drive, Slack, or similar services that need OAuth 2.0 authentication for user data access.
日本語の概要は準備中です。原文の説明を表示しています。