AGENT SKILLS · MISSION KIT
Useful agent skills ranked by real adoption
Browse verified skills from public repositories. Compare what each skill does, package contents, install activity, and source evidence before adding it to your agent.
- CATALOG SCOPE
- VERIFIED
- skills
- 22,719
- repositories
- 3485
- last synced
- Oct 31, 2026
crontapcrontap-replace-github-actions-cron
Replace a GitHub Actions schedule trigger with a Crontap HTTP dispatch while keeping the workflow, runner, and logs on GitHub. Use when a user needs a timezone-aware external clock or wants to avoid scheduled-workflow drift.
- 1h installs
- 1
- GitHub stars
- 1
- Updated
- Sep 16
crontapcrontap-retries-and-idempotency
Configure Crontap retry policy safely and design scheduled endpoints so repeated requests do not duplicate side effects. Use when a user needs reliable delivery, exponential backoff, or help diagnosing duplicate work.
- 1h installs
- 1
- GitHub stars
- 1
- Updated
- Sep 16
crontapcrontap-uptime-monitor
Create and operate a Crontap uptime monitor, tune its failure threshold, pause it during deployments, and inspect probe evidence. Use when a user wants availability checks and down or recovery alerts for an HTTP endpoint.
- 1h installs
- 1
- GitHub stars
- 1
- Updated
- Sep 16
replicas-groupreplicas-agent
Guide for background coding agents running inside Replicas cloud workspaces
- 1h installs
- 1
- GitHub stars
- 1
- Updated
- Sep 8
fandhe-aicreate-html-report
分析・比較・調査結果・進捗・計画を、意思決定しやすい自己完結 HTML レポートとして生成する。 「HTML レポート作って」「レポートにまとめて」「比較を可視化」「グラフで見せて」「ガントチャート作って」 「ダッシュボード風にまとめて」「見やすくまとめて」で使用。 データと伝えたい関係に応じて KPI・表・bar・line・scatter・heatmap・waterfall・donut・radar・gantt から適切な表現を選び、アクセシブル・レスポンシブ・印刷対応の単一 HTML ファイルを生成する。
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 14
golden-frijolesrefine
The front door for any new ask — feature, bug, spike, or chore. Use when the product owner has a raw idea in their head (or a seed in Roadmap/00-ideas/seeds) and wants to turn it into shippable, sliced work. Runs orientation → appetite → classification → "can we already do this?" → disambiguation → platform-first reframe → slicing, lands a Definition- of-Ready pitch in 00-ideas/seeds, and on approval funds the bet, scaffolds + commits the epic + sprint docs and emits the builder kickoff — epic-m
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
golden-frijolesreport
Posts a project report to a chat destination, at the cadence asked for. Daily: a delta-only standup of overnight signals across every repo the project spans (opened/merged PRs and CI, the latest browser smoke, BUILD-ORDER drift, open-PR state, stale previews). Weekly: an executive recap/retro (merged PRs, shipped epics, deploys per app repo, a retro digest). PMO: the weekly operational report with scrum/DORA/doc-ops metrics and a story deck, or the on-demand monthly stakeholder packet with a met
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
golden-frijolessmoke
Verifies real, rendered behavior on this project's frontend (local/preview/staging/prod, unauthed or authed) via a real headless-Chromium Playwright browser — the DEFAULT way to check "does this render correctly / does this look right / is this actually live" for any coding agent, not just Claude Code. Use when asked to "smoke test", "verify the live/prod page", "check if X actually rendered", "run a browser smoke", "does this look right on preview", "verify an authed role's flow", or as a post-
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
jmbhkimdiagram-design
Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, pyramid/funnel, treemap and marimekko, heatmap, bar and dumbbell, waterfall, line (slopegraph, ridgeline, streamgraph, bump), Gantt and scatter charts (bubble, beeswarm), high-level, process, medallion,
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksclose-roadmap
Close out a finished roadmap or feature execution by retiring its planning docs into canonical documentation and carrying what is still owed into the next roadmap — you are the archivist and the architect of the next round, not the coder. Use when the user invokes /close-roadmap , or asks to clean up a feature's docs, retire a roadmap, prepare for the next roadmap, or tidy docs/ / after execute-roadmap or build-feature has finished. Reviews ACCEPTANCE.md check by check, triages every item of ROA
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksdraft-experience
Shape a feature as a product before anyone plans how to build it — the sentence, the ladder of use cases smallest to largest, what stays hidden, and the open product questions. Use when the user invokes /draft-experience , asks what a feature should be, asks whether something is simple enough, or wants the experience document that a technical design, roadmap or plan is then written from. Also use to check an existing feature, bug or proposal against the product shape it claims to serve. Writes d
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksdraft-technical
Design how a feature is built as an engineering conversation with the user before any plan document exists — discover the architecture together, find what the codebase already has to build on, challenge complexity, record every decision with its reason, and write docs/ /TECHNICAL.rev1.md only when the user says the design is ready. Use when the user invokes /draft-technical , or asks to design, architect, or think through how to build a feature, subsystem, integration, migration or infrastructur
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksexecute-plan
Execute a signed-off PLAN.final.md for a single feature yourself, phase by phase, on the current branch — you are the engineer, not a delivery lead. Use when the user invokes /execute-plan, or asks to implement, build or continue an approved plan that is small enough for one person, e.g. "/execute-plan spell-check", "/execute-plan spell-check p1-p3", "build the rest of the plan while I sleep". Resolves the requested phases against the final doc, builds each as its own verified increment, runs it
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksexecute-roadmap
Execute an approved roadmap or plan by orchestrating sub-agents — in parallel, in isolated checkouts, where the runtime allows — you are the delivery lead, not the coder. Use when the user invokes /execute-roadmap, or asks to implement, execute, or oversee an approved roadmap or plan after draft-roadmap or build-feature has produced a signed-off final doc, e.g. "/execute-roadmap implement m2, plans 3.1-3.4, parallelize" or "oversee the roadmap until it is complete". Resolves the requested scope
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksmerge-branch
Merge changes from another branch while reviewing them against the project's principles — a merge is a review gate, not a mechanical operation. Use when the user asks to merge a branch, bring changes in from another branch, or resolve a merge. Flags unclear intent, unnecessary complexity and likely bug sources before merging, asks the user about any product decision a conflict would settle, and recommends merging the main integration branch into the other branch first when that is the easier dir
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksresume-handoff
Pick up unfinished work from docs/ /HANDOFF.md in a fresh session — you are the agent the handoff was written for, and you verify it against the tree before you trust it. Use when the user invokes /resume-handoff , points at a HANDOFF.md, or asks to continue, resume, or pick up where the last session stopped on a plan or roadmap built by execute-plan, execute-roadmap or build-feature, e.g. "/resume-handoff cloud-sync", "/resume-handoff spell-check p4", "pick up the handoff and keep going while I
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworksreview-doc
Review an experience, technical, plan, roadmap, or implementation doc from draft-experience, draft-technical, build-feature or draft-roadmap — you are the reviewer, not the author. Use when the user asks to review a plan, roadmap, design or experience document, or invokes /review-doc . Reads docs/ / .revN.md, writes .revN.notes.md grounded in the product shape, the project's principles and the actual code, and iterates with the user until the doc is ready to become .final.md.
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
koruworkswrite-acceptance
Write docs/ /ACCEPTANCE.md — the ordered checklist a person works through by hand to deploy, test and accept finished work, because a machine could not do it. Use at the end of every implementing skill (execute-plan, execute-roadmap, build-feature), or when the user invokes /write-acceptance or asks for a test plan, an acceptance checklist, or "tell me how to verify this". Covers only what could not be automated — consoles and accounts, physical devices, GUI surfaces, two-machine and multi-user
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 13
linyeegiongacademic-deai
中英文学术写作去AI化与去防御性表述（通用，不限学科）。用于润色期刊/会议论文、学位论文、基金申请书、审稿回复中由 AI 辅助生成或带有 AI 腔的文字：删除套话、空泛强调、机械连接词、排比堆砌和多余的自我保护式限定，同时保留与证据相称的必要谨慎表述，不改动任何数值、公式、引用和术语。Use when the user asks to 去AI味/去AI化/降AI/去防御性表述/去套话/humanize/de-AI/remove hedging/make it sound less like AI in academic prose (Chinese or English; .tex/.md/.txt or pasted text).
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 14
mercatorprojaudit-anything
Run an evidence-first domain audit by pairing with another available skill, such as frontend, UX, architecture, database, IA, or AI workflow. Use for explicit audit requests, not ordinary implementation or a quick code review.
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 10
mercatorprojc4-structurizr
Analyze a codebase and produce seven Structurizr-styled C4-PlantUML diagrams rendered with Java PlantUML.
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 10
mercatorprojcodebase-architecture-governance
Analyze and improve a software project's module boundaries, dependency direction, file organization, code duplication, oversized modules, and unnecessary indirection. Use when a repository has become hard to navigate, files are proliferating, responsibilities are scattered, or a safe architecture/refactoring plan is needed. Supports analysis-only recommendations and incremental implementation across languages and frameworks.
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 10
mercatorprojproject-prd-doc-builder
根据现有项目目录、源代码、测试、产品说明、用户故事和架构资料，逆向梳理并编写完整、易读、可追溯的 PRD 与项目综合文档站点。适用于“根据代码库生成 PRD”“把项目资料整理成 VitePress 文档”“补全用户故事、用例、业务流程、Mermaid/C4 图表、验收标准”等任务。
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 10
mercatorprojskill-publisher
Validate, version, package, and safely publish owned Codex skills from a skill monorepo to their configured GitHub repositories. Use when preparing or releasing a skill; do not use to discover or install unrelated third-party skills.
- 1h installs
- 1
- GitHub stars
- 0
- Updated
- Oct 10