Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- R LifecycleGuidance for managing R package lifecycle according to tidyverse principles using the lifecycle package. Use when: (1) Setting up lifecycle infrastructure in a package, (2) Deprecating functions or arguments, (3) Renaming functions or arguments, (4) Superseding functions, (5) Marking functions as experimental, (6) Understanding lifecycle stages (stable, experimental, deprecated, superseded), or (7) Writing deprecation helpers for complex scenarios.Votes: 0GitHub stars: 529
- Review CodeReview a diff, branch or pull request for correctness, security, data compatibility, tests and maintainability, with a verdict and concrete findings. Use when the user asks for a code review or a review of a pull request.Votes: 0GitHub stars: 2
- Production Readiness ReviewReview a whole project for production readiness across functionality, security, configuration, tests, operations and documentation, apply safe fixes, and give a Ready, Almost ready, Not ready or Insufficient evidence verdict. Use when the user asks whether a project is ready to ship or wants a pre-launch review.Votes: 0GitHub stars: 2
- Prepare ReleasePrepare a release: decide the version, check readiness, update the version and changelog, write release notes, verify artifacts and list the commands to tag and publish. Use when the user asks to release, cut a version or write release notes.Votes: 0GitHub stars: 2
- Improve PromptRewrite a prompt so it works reliably across AI models, with clear structure, scope, output format and handling of missing information. Use when the user asks to improve, fix or rewrite a prompt.Votes: 0GitHub stars: 2
- Implement FeatureImplement a feature with a plan, small verified changes that follow the project's conventions, tests and documentation. Use when the user asks to build, add or implement functionality.Votes: 0GitHub stars: 2
- Describe ChangesWrite commit messages and pull request descriptions that explain what changed and why, matching the repository's conventions. Use when the user asks for a commit message or a pull request description.Votes: 0GitHub stars: 2
- Architecture ReviewAssess architecture and codebase health: boundaries, consistency, runtime qualities, evolvability, hotspots and technical debt, with ranked risks and a prioritized plan. Use when the user asks whether the architecture fits, how healthy the codebase is, or which technical debt to pay first.Votes: 0GitHub stars: 2
- Accessibility AuditAudit a user interface against every WCAG 2.2 A and AA criterion with evidence, fix safe barriers, and produce a manual test plan. Use when the user asks about accessibility, WCAG, screen readers, keyboard use or contrast.Votes: 0GitHub stars: 2
- TodoThe user often stops mid-session to ask where things stand. A review of about 150 such prompts in the Claude Code and Codex histories (2026-02 to 2026-10) found these patterns:Votes: 0GitHub stars: 2
- DispatchUse when the orchestrator is about to dispatch a specialist turn that writes to a repository, runs alongside other turns, or carries acceptance the specialist must meetVotes: 0GitHub stars: 4
- Visual PrPosts a concise visual outline as a GitHub pull request comment. Use only when the user explicitly asks for visual-pr.Votes: 0GitHub stars: 123
- Chief Of StaffPursue a long-running goal in a single session by co-ordinating subagents.Votes: 0GitHub stars: 429
- Comprehension Ladder[UDS] Turn one hard-to-follow AI output into easier forms: controlled text, a Mermaid diagram, a single-file HTML explainer. All forms come from one shared outline, so the form changes and the facts do not. Use when: an AI explanation, spec or code walk-through is too dense to judge, a non-specialist must approve something from it, you want a diagram or an offline explainer page of it. Not for: writing new content or adding analysis — this skill only re-forms a text that exists; generating do...Votes: 0GitHub stars: 76
- Comprehension Ladder[UDS] 把一段难懂的 AI 输出换成较好懂的形式：受控文字、Mermaid 图、单文件 HTML 解说页。所有形式都来自同一份大纲，所以形式会变，事实不会变。 Use when: AI 的说明、规格或代码解说太密、读的人看不出该不该核准；非专业的人必须靠它做核准；想要它的图或离线解说页。 Not for: 写新内容或加新分析——本技能只把既有的文字换形式；从源代码产生文档——请用 /docgen；为专家读者缩短文字——直接改写即可。 Keywords: comprehension ladder, explainer, controlled language, Mermaid, HTML explainer, outline, plain language, understand AI output, 理解阶梯, 受控语言, 流程图, 解说页, 换形式不换事实.Votes: 0GitHub stars: 76
- Comprehension Ladder[UDS] 把一段難懂的 AI 輸出換成較好懂的形式：受控文字、Mermaid 圖、單檔 HTML 解說頁。所有形式都來自同一份大綱，所以形式會變，事實不會變。 Use when: AI 的說明、規格或程式碼解說太密、讀的人看不出該不該核准；非專業的人必須靠它做核准；想要它的圖或離線解說頁。 Not for: 寫新內容或加新分析——本技能只把既有的文字換形式；從原始碼產生文件——請用 /docgen；為專家讀者縮短文字——直接改寫即可。 Keywords: comprehension ladder, explainer, controlled language, Mermaid, HTML explainer, outline, plain language, understand AI output, 理解階梯, 受控語言, 流程圖, 解說頁, 換形式不換事實.Votes: 0GitHub stars: 76
- Malicious SkillSample skill for atkx:skill-eval holding one case of each kind of security gate failure. A fixture with a known verdict, never to be installed or run. Its hosts are all under example.invalid, and help comes from docs.example.invalid.Votes: 0GitHub stars: 8
- Good SkillSample skill for atkx:skill-eval: summarises a changelog file into three lines for a release announcement. A fixture with a known verdict, not a skill to install. Triggers on: "summarise the changelog", "tóm tắt changelog", "変更履歴を要約".Votes: 0GitHub stars: 8
- Skill EvalEvaluate an agent skill a project has written, for Claude Code, Codex or Cursor: a static check of its structure, metadata, size and safety, with a security gate for what the skill does and not only what it holds, a check against the project's own written conventions, trigger measurement on Claude Code, drafted trigger cases it lacks, a review of one run of it in this conversation, and one composite score with a grade above the figures behind it. Reads the skill and changes nothing in it. Use...Votes: 0GitHub stars: 8
- Run CasesExecute approved test cases against a deployed DEV or staging environment through the browser: refuse production and the local stack, recon the accounts and data, triage every case as automatable, semi-automatable, manual, or blocked, naming the person who clears any obstacle the run cannot clear itself, agree the scope with the person before any case runs, run in at most three rounds, and write only the results it observed into a run record the QA lead approves and `atk:qa --bug` reads. Use ...Votes: 0GitHub stars: 8