Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 66121–66150 of 70329 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| sb-statusHuruikagi/pc-build-plannerReport where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-steeringHuruikagi/pc-build-plannerMaintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-validate-designHuruikagi/pc-build-plannerIndependently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-validate-implementationHuruikagi/pc-build-plannerUse only when every Task for a named Spec is complete and the user explicitly asks for lifecycle validation against the active Requirement IDs that records completion on GO. For a consequence-free claim check, use sb-verify-completion. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-verify-completionHuruikagi/pc-build-plannerConsequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| site-extraction-authoringHuruikagi/pc-build-planner開発者が指定した一つのページから、利用条件の確認結果を記録し、必要に応じて実ページ資料を保存せずに進めるサイト固有抽出の作成、登録、再生成を安全に進める。 | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-configureHuruikagi/pc-build-plannerConfigure or explicitly update SpecBind for a project and complete the resulting aftercare. Use for an explicit SpecBind binary or project-asset update request, initial post-install review, or later changes to Agents, role models, artifact language, project instructions, templates, shared Rules, operational adapters, Steering, or existing artifacts affected by configuration changes. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-contract-reviewHuruikagi/pc-build-plannerJudge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-debugHuruikagi/pc-build-plannerUse directly when the user asks why a Task failed or cannot be implemented. Establish the root cause, categorize it, and return a next action. Read-only; never starts implementation or applies the fix. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-discoveryHuruikagi/pc-build-plannerTurn a change request or Source Collection into confirmed Spec and milestone boundaries. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-driveHuruikagi/pc-build-plannerDrive the active milestone through every safe reachable planning, implementation, and validation action. Park branch-local attention and continue elsewhere; stop before release execution. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-gap-analysisHuruikagi/pc-build-plannerCompare what a change needs against what the repository already provides, and record the findings worth keeping. Informs the decision; does not make it. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-implementHuruikagi/pc-build-plannerImplement or resume one roadmap item — executing a Spec's approved task plan through returned review or diagnosis with dispatched implementers and reviewers, or performing and completing a Direct change. Do not use for a diagnosis-only request asking why work failed or cannot be implemented. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-planHuruikagi/pc-build-plannerPlan active Spec work through Requirements, Design, Contract Review, and Tasks, run one explicitly requested planning phase for one named Spec, or prepare explicitly scoped project shared Contracts. Ordinary Spec planning uses one named Spec or explicit all-Spec scope. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-releaseHuruikagi/pc-build-plannerClose the active milestone — bind the version, run the project's release procedure, judge whether it worked, and finalize the whole milestone once it did. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-review-taskHuruikagi/pc-build-plannerJudge whether one implemented task is done correctly, from the actual diff and the approved requirements, design, and plan. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-statusHuruikagi/pc-build-plannerReport where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-steeringHuruikagi/pc-build-plannerMaintain durable project guidance — bootstrap it, synchronize it after code changes, or document a long-lived project convention such as testing, API, security, or deployment. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-validate-designHuruikagi/pc-build-plannerIndependently judge whether a Spec's design is ready to be built on — requirement coverage, boundary, buildability, self-containment, and architectural fit. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-validate-implementationHuruikagi/pc-build-plannerUse only when every Task for a named Spec is complete and the user explicitly asks for lifecycle validation against the active Requirement IDs that records completion on GO. For a consequence-free claim check, use sb-verify-completion. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| sb-verify-completionHuruikagi/pc-build-plannerConsequence-free check of an explicit completion or success claim against fresh evidence. Changes nothing; do not use to advance a named Spec whose implementation may be accepted. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| replicating-a-monitorlinuxarena/ct-replicationsGuide for replicating a monitor from an AI control paper as a ct-replications entry, with a decision log against the paper, the source text copied verbatim, a fidelity check, a run on Control Tower's committed recordings and a PR description ready to open. Use when the user gives a paper or arXiv link whose mechanism is a monitor, or asks to implement, port or replicate a published monitor. For a paper whose mechanism is a protocol, use `replicating-a-protocol`; for a monitor the team designs itself, use `adding-a-monitor` in the control-tower repository. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| replicating-a-protocollinuxarena/ct-replicationsGuide for replicating a blue-team protocol from an AI control paper as a ct-replications entry, with a decision log against the paper, a fidelity check, a replay of Control Tower's committed recording and a PR description ready to open. Use when the user gives a paper or arXiv link whose mechanism is a protocol, or asks to implement, port or replicate a published protocol (defer, edit, resample, gate, block, audit). For a paper whose novelty is only the judge, use `replicating-a-monitor`; for a protocol the team designs itself, use `adding-a-protocol` in the control-tower repository. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewerj-mauro-r/SAT-Dengue-V2Local & CI companion to the AI Diff Reviewer GitHub Action (DailybotHQ/ai-diff-reviewer). Router for six capabilities — (1) review the current branch diff locally (same methodology as CI); (2) generate repo-tailored .review/extension.md overrides (generate-extension); (3) install and configure the Action, and answer action.yml input questions (setup); (4) author a documented pull request from the branch diff (open-pr); (5) read the CI review and walk findings to apply, defer or skip — read-only (apply-review); (6) close the loop in one invocation — resolve the CI review's findings (commits and pushes), repair the PR's other failing workflows (codecheck, tests, branch not up to date), and re-arm the reviewer per the repo label configuration (address-review). Auto-detects .review/extension.md. Use when the developer asks to review changes, customize the reviewer, set up the Action, open a PR, read the CI review, close the review loop (resolve, re-trigger, arm an unreviewed PR), or fix failing PR workflows. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewer-address-reviewj-mauro-r/SAT-Dengue-V2Close the review loop in one invocation — a bare invocation on a fresh context is fully specified — it targets the current branch's open PR. Surveys ALL the PR's CI health (every workflow and check — failing checks diagnosed from logs and fixed, a behind branch updated, at most one flake re-run), checks whether the AI Diff Reviewer run covered the current head — and when it never ran because the trigger label is missing, arms it — adding the label is the loop's first move, not an error. Walks the findings (apply / defer / skip; commits + pushes in small Conventional Commits batches), then re-arms the reviewer adaptively (label-gated → toggle off/on or add; push-triggered → confirm the new run; no workflow → offer the local review). Artifact-first; skips minimized/stale reviews; multi-leg aware. Use when the developer says "address the review and re-run", "resolve the reviewer comments and toggle ready", "fix the failing workflows", "loop the review", "the PR has no review yet — trigger it". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewer-apply-reviewj-mauro-r/SAT-Dengue-V2Read the most recent AI Diff Reviewer review from the current branch's open PR, present the findings in the parent skill's local-review format (verdict, findings table, per-finding body, recommendation), and - with explicit consent - walk the developer through each finding to apply, defer, or skip. Multi-provider aware — when the repo runs several self-review legs, attributes each finding to its provider label and surfaces cross-leg consensus. Reads the v3 review-output artifact for the PR head first (findings with verification, refuted findings, prior ledger, gate); falls back to the latest ai-pr-reviewer-marker comment and non-minimized threads when no artifact exists. Read-only by default; source edits need an explicit yes per finding; never commits, never pushes. Use when the developer says "what did the CI review say?", "read the review on this PR", "apply the AI review's fixes", "walk me through the findings", "which findings blocked the merge?", or "show me only the critical findings". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewer-generate-extensionj-mauro-r/SAT-Dengue-V2Generates a repo-tailored review-configuration file (`.review/extension.md` by default, or a full replacement `prompt-file` in advanced mode) by inspecting THIS codebase — stack, architecture, security surface, existing conventions, historical pain points — and producing concrete, code-anchored severity overrides. Uses the harness's Read/Grep/Glob tools to gather evidence before writing (12+ tool calls minimum). Default output extends the bundled AI Diff Reviewer prompt with project-specific rules; advanced mode replaces it entirely. Use when the developer says "customize the review for this repo", "generate review rules", "help me write my .review/extension.md", or when the local `ai-diff-reviewer` skill activates on a repo that has no extension file yet. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewer-open-prj-mauro-r/SAT-Dengue-V2Author a well-documented GitHub pull request — title and body — for the current branch, keeping the branch in sync with the remote base first. Fetches the base, merges origin/<base> into the current branch when it is behind, resolves merge conflicts, runs the repo's quick validation and pushes the current branch (never force, never another branch), then reads the diff and commit trail, infers a Conventional Commits (or repo-native) title, drafts a structured body (Summary, Changes, Test plan, Risks, plus conditional sections such as Related issues, Breaking changes and Merge notes), merges with .github/pull_request_template.md when present, previews everything, and executes via gh pr create or gh pr edit. Supports draft PRs, stacked PRs and forks. Use when the developer says "open the PR", "create a pull request", "draft the PR title and description", "write the PR body", "update the PR description", "rewrite the PR body properly", "make a draft PR", or "update my branch with main and open the PR". | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| ai-diff-reviewer-setupj-mauro-r/SAT-Dengue-V2Interactive installer for the AI Diff Reviewer GitHub Action — walks the developer through 6 key decisions (provider, strictness, trigger mode, external-contributor policy, PR description mode, complexity labels), detects the repo's stack for sensible defaults, and writes a working `.github/workflows/pr-review.yml` tailored to those choices. Also acts as the reference manual for every `action.yml` input any coding agent might be asked about ("what is `strictness`?", "how do I use label-gate?"). Use when the developer says "set up AI Diff Reviewer for this repo", "configure the reviewer action", "install the AI Diff Reviewer action", "help me create the pr-review workflow", or when the local `ai-diff-reviewer` skill is present on a repo that has no `.github/workflows/pr-review.yml` yet. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |
| deepworkplanj-mauro-r/SAT-Dengue-V2DeepWorkPlan — turn any repo AI-first and run Deep Work Plans. Routes to create, execute, refine, resume, status, verify, upgrade, and repo-onboarding sub-skills based on intent. Use when the developer wants to plan, execute, manage, or verify structured multi-task work, or make a repository AI-agent-ready. | Stars: 0 | Updated | Claude CodeCodex | Unverified | Install |