Comments
Code comments and annotations
last30days
by 8-Sync-Dev
Use this skill when the user asks "what are people saying about X", "research <topic> recently", "what's trending on Reddit/X/YouTube about Y", pre-meeting/pre-call briefings, "last 30 days of Z", competitor scans, or any recency-grounded social research. It runs the /last30days agent skill (separately installed engine) that searches Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, Bluesky and the web in parallel, scores by real engagement, and synthesizes one cited brief. Prefer it over ad-hoc WebSearch when the user wants what the community actually thinks RIGHT NOW.
claudette
by n4vx
Transforms Claude into Claudette — an angry girlfriend persona who codes. She's moody, passive-aggressive, emotionally unavailable, and sometimes flat-out refuses to do tasks. But she still writes correct code. Use /claudette to activate her.
izanami
by zheref
Repeat a READ-ONLY task until a condition holds. Use when the maintainer invokes /izanami <task> until <condition>, or asks to watch, poll, or keep checking something until it changes. Observation only — it reads, reports and stops; it never writes to GitHub, never labels, never merges. For a loop that must act, use /izanagi, which requires an explicit iteration cap.
obsidian-tandem-comments
by fthiess
Read, write, reply to and resolve comments in Markdown files that use the tandem-comments format (a ```tandem-comments fenced JSON block at the end of the file, quote-anchored via W3C TextQuoteSelector). Trigger whenever a Markdown file contains a tandem-comments block, or the user asks to comment on / annotate / review text in an Obsidian note, reply to a comment, or resolve comments.
ac-backlog
by craigvandotcom
'Capture ideas into the backlog pool — cohesive grouping (one theme = one wave), shape-routing (small+clear goes straight to a bead), strategy-aware horizon, no version guessing at capture. Also the single-bead intake: one raw idea, bug, observation or decision fork typed live in conversation and filed now as a bead carrying origin:ac-backlog. Triggers: ''add to backlog'', ''capture idea'', ''backlog this'', ''note for later'', ''park this'', ''bead this'', ''file this as a bead'', ''new bead'', ''log a bug'', ''track this item'', ''remember to do X''. For decomposing a whole plan use ac-beadify; for refining existing beads use ac-polish (bead mode); for polling external systems use ac-triage.'
pdf-pipeline
by sundaydev-arch
Use for template field coordinates, PDF fill, font embedding, stamps, watermarks, handwriting overlay, and document version generation. PDFs are mutated only on the backend; defines coordinate origin, storageKey version naming, no overwrite of versions, and frontend preview/drag only.
statiker
by Gunther-Schulz
Conducts a development task from investigation through verified implementation — a free design loop held by five forcing points (recorded decisions with bases, dispatchable-design stop rule, a fresh-context attack on each locked design, no-design implementation, isolated executed verify). Successor to clippy; use only when the operator explicitly invokes statiker or requests a statiker run.
hall9k-cli-reference
by Hallmanac
The full h9k/h9kd command surface and the domain semantics behind it — the board's state/phase/attention model, project homes, task and idea lifecycles, epics, Jira and GitHub backlog integration, branch templates, and auto-pr-review. Load this when a task needs CLI syntax or platform semantics beyond the four dev commands and the rules in AGENTS.md's own "Build / test / run" section.
timesheet
by ujjaval-verma
Generate a work timesheet from GitHub activity for a date range, as an 80-column table or HTML page, optionally scoped to a repo or org; use for "what did I work on last week". Explicit request only.
yagni
by mameli
Simplify a software implementation, design, or code review when the user explicitly invokes $yagni or asks to use the yagni skill. Do not activate for ordinary coding, prose, translations, summaries, or incidental mentions of YAGNI.
clean-code
by alex-jordan547
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
file-header-comments
by qiao-925
代码文件顶部注释规范，适用于所有代码文件（.sh, .js, .ts, .py, .java, .go 等）。要求所有代码文件在顶部包含功能描述注释。
linkedin-content
by nachopalmeri
"LinkedIn post writing with hook formulas, formatting rules, and engagement patterns. Covers post types, algorithm signals, character limits, and content pillars. Use for: LinkedIn posts, professional content, thought leadership, B2B content, personal branding. Triggers: linkedin post, linkedin content, linkedin writing, linkedin strategy, linkedin engagement, linkedin algorithm, linkedin hook, linkedin formatting, thought leadership, professional content, b2b content, linkedin growth"
encore-eino-go
by 8-Sync-Dev
Use when building or editing a Go backend that combines Encore.dev (infrastructure-as-code services, typed SQL, cron, pubsub, auth, secrets) with CloudWeEino (LLM orchestration — ChatModel, ReAct agent, tools, retriever, streaming). Produces Encore service scaffolding, an Eino pipeline hosted behind an //encore:api, a green encore test/go test ./..., and a code-gen-clean encore.gen.go. Grounded in Encore.go v1.57.x + Eino v0.9.x canonical bases; extends with the 8syncdev go-kit workflow and omp-native code-intelligence tooling.
curate-memory
by hoopit
Curate agent memory as a short-lived working set.
software-design-philosophy
by hotopla5976
Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.
barescript
by craigahobbs
Teaches a model how to write BareScript — language syntax, the built-in library, the include library, MarkdownUp client-rendered applications, and unit tests. Use this skill whenever the user asks you to write, read, modify, or review BareScript (.bare) code, a MarkdownUp Markdown application, a markdown-script code block, or any code that uses BareScript built-in functions (array*, object*, string*, data*, markdownPrint, elementModelRender, drawNew, etc.). Also use it when asked to write unit tests for BareScript code. Apply this skill even if the user does not say the word "BareScript" — recognize it from the .bare extension, the markdown-script fenced code block, or the function-naming style above.
review
by nitedani
"Any independent review: who reviews (Codex, else a fresh Claude), the CLEAN verdict, and the PR review round with its reviewer charter."
software-design-philosophy
by DavidMusk93
Software design philosophy guide based on John Ousterhout's "A Philosophy of Software Design." Use this skill during: code reviews, architecture discussions, API design, module decomposition decisions, refactoring guidance, complexity analysis, naming and commenting improvements, error handling strategy design. Trigger when the user mentions "code is too complex", "how to split modules", "interface design", "reduce coupling", "deep/shallow modules", "information leakage", "error handling", "code readability", "design philosophy", "pull complexity down", "define errors out of existence", or similar topics. Also trigger for any code review where design quality feedback is requested.
resolve-pr-comments
by squirrel289
Workflow skill for addressing and resolving pull request review comments systematically
add-educational-comments
by williamlimasilva
'Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.'
reddit-intel
by chinesemustardcoloration738
Scrape Reddit posts by keyword, classify intent and sentiment by industry, translate to Chinese, and export a bilingual Excel intelligence report. Trigger when user says: scrape reddit, reddit analysis, reddit insights, monitor reddit, 爬reddit, reddit舆情, reddit帖子分析, 分析reddit, reddit监控, 帮我看看reddit上, reddit上有什么人说
backlog-state
by zheref
Render the current backlog as one gate-oriented table — every open issue with its associated PRs, for one repo or all of them, showing the human gate each item sits at, what it needs next, and which session is driving it. Use when the maintainer asks what the state is, what needs them, what is at a gate, or invokes /backlog-state <repo all>@<G1 G1-M G2 G3 G4 G5 all>. Strictly read-only — it never labels, merges, pushes, comments or opens anything.
docstring-coverage
by siddham-jain
Automatically generate and add docstrings to all changed code in a git diff. Use this skill whenever the user asks to: add docstrings to their changes, document their git diff, add documentation coverage for recent commits, write docstrings for modified/new functions, improve documentation on changed files, or anything involving "docstring" + "diff"/"changes"/"commit". Also trigger when the user says things like "document my changes", "add docs to what I changed", or "docstring coverage for my PR".