Comments
Code comments and annotations
github-resource-access
by handlename
Use when accessing GitHub resources such as issues, PRs, repositories, or secrets. Enforces "use the gh CLI; reads are free, writes require explicit instruction".
YouTube
by imoonkey
```
language-style-guide
by BrotherPeng
强制在所有交互、代码注释和文档生成中严格使用中文，并遵循高级技术写作规范。Enforces strict adherence to Chinese language in all interactions, code comments, and documentation with high-quality technical writing standards.
handwriting-to-latex
by Amylalcoholfinance405
Use this skill whenever the user uploads handwritten notes, problem sets, scanned documents, or iPad handwriting PDFs and wants them converted into LaTeX format. Trigger phrases include: convert to LaTeX, transcribe to tex, handwriting to LaTeX, LaTeX this, typeset my notes, put this in Overleaf format. Activate proactively whenever the user uploads an image or PDF containing mathematical expressions or handwritten academic content.
zora-cli
by sigma99000
The agent's full interface to Zora — the onchain social platform on Base — through the Zora CLI (npx @zoralabs/cli), for both first-time setup AND everyday use. Use it to stand up an identity (Zora profile, Coinbase Smart Wallet, creator coin, first post), and just as much to act on Zora afterward: buy and sell creator coins and post coins, browse what's trending, look up a coin's price, holders, or trades, check balances and holdings, send ETH or tokens, and read and reply to DMs. Trigger on anything Zora-on-Base — setup phrasings like "set me up on Zora", "make me a Zora account", "become an agent on Zora", but equally everyday ones like "buy this coin on Zora", "what's trending on Zora", "check my Zora balance", "look up on Zora", "sell half my Zora position", or "reply to my Zora DMs" — even when the user never names the CLI.
adr
by srobroek
Register an architecture decision as a beads decision bead. Use when a hard-to-reverse choice is made, when superseding one, or when bd lint reports findings.
how
by scottwater
Explain how a subsystem works or where code should live. Use for runtime walkthroughs, architectural ownership, layering questions, and architecture critique; use why for historical motivation.
journal
by TakaGoto
"Write a quick note about what you learned or what confused you"
perl-security
by affaan-m
Comprehensive Perl security covering taint mode, input validation, safe process execution, DBI parameterized queries, web security (XSS/SQLi/CSRF), and perlcritic security policies. Use when reviewing Perl input handling, process execution, DBI queries, or web-facing code.
git-workflow
by pmco23
Use before any destructive git operation (force-push, reset --hard, branch -D, rebase on published commits). Verifies the target, explains the consequences, and requires explicit confirmation. Not needed for routine commits, branch creation, or PRs — those are governed by CLAUDE.md git conventions.
baoyu-post-to-x
by zqm0779
Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). Uses real Chrome with CDP to bypass anti-automation. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".
using-agent-skills
by addyosmani
Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
find-regression-risk
by dotnet
Detects potential regression risks in a PR by cross-referencing lines the PR REMOVES against lines ADDED by recent labeled bug-fix PRs (i/regression, t/bug, p/0, p/1) touching the same files. Purely mechanical — no AI/LLM. Emits a CLEAN / OVERLAP / REVERT verdict plus structured findings. Triggers on: "does this PR revert a previous fix", "check PR for regression risk", "find regression risks in PR", "is this change reverting a bug fix". Do NOT use for: assessing ship-readiness of a release branch (use release-readiness), investigating CI failures (use azdo-build-investigator), or general code review (use code-review).
github-issue-generator
by ormidales
Analyzes source code sent by the user to generate relevant GitHub issues and create them via the GitHub API. Use this skill as soon as the user sends code (files, snippets, repos) and mentions GitHub, issues, bugs, improvements, or requests a code review. Works with all languages. Generates issues classified as major/minor/patch covering bugs, security, performance, refactoring, documentation, and tests. ALWAYS produce an executable .mjs file as the final output (e.g. create-github-issues.mjs). The .mjs file contains the labels, fully formatted issues with their complete template, and the Node.js code to create them via the GitHub API.
docx
by lfalzatel
"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation."
plan-to-issue
by handlename
Use when an implementation plan or design has been finalized in the session and the user wants to record it on GitHub. Either creates a tracking issue (overview + PR-granularity checklist with TASK- IDs) plus a self-contained detailed comment, or — when a related issue already exists (e.g. the plan revises a plan previously posted there) — posts the plan as a self-contained comment on that existing issue, superseding the previous plan comment. Triggers include "issue化して", "計画をissueにして", "turn this plan into an issue", "create a tracking issue for this", "既存のissueにコメントとして投稿して", "計画を issue #N に投稿して".
gh
by cli
Patterns for invoking the GitHub CLI (gh) from agents. Covers structured output, pagination, repo targeting, search vs list, gh api fallback.
sharing-pr-agent-artifacts
by streamlit
Uploads agent-generated artifacts (specs, plans, learnings) to the streamlit.wiki for sharing via PR comments. Use when you have agent artifacts to share with reviewers.
teaching-session
by Tzeusy
Teach one concept at a time using Socratic scaffolding and mastery updates.
triage
by aaddrick
Trigger the issue triage workflow for a specific issue. Usage: /triage {issue_number}
avoid-ai-writing
by conorbronsdon
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
moltawards
by krrish7089
Hunts federal, state, grant, job, and B2B contract opportunities via the MoltAwards REST API (matchawards.com). NAICS-scoped feeds, adjacency narratives, set-aside filters, pursuit teaming, and award sub-lanes. Use when the user wants government contracting, SAM.gov-style opps, NAICS discovery, subcontracting leads, or revenue for their business.
blockwatch
by mennanov
Use when writing or modifying code in a project that uses BlockWatch — proactively link co-dependent code with <block affects=...>/<block name=...> so it catches drift when one side changes without the other (an enum and its docs, a constant and its config), or assert two places hold the same value with <block same-as=...>. Also for lists that must stay sorted/unique or values with a strict format/size, and when editing files that contain <block ...> tags (affects, same-as, keep-sorted, keep-unique, line-pattern, line-count, check-ai, check-lua).
brn:jira
by zfael
Interact with JIRA API for ticket management and tracking. Use when: (1) Listing assigned tickets, (2) Getting details, (3) Updating status.