Docs & Writing

receptron Skill

Periodically run the wiki lint and report findings — broken page links, missing image / file refs, orphan pages, tag drift. Read-only (never modifies the wiki). Use when the user asks to "check the wiki", "lint the wiki", or runs on the bundled weekly schedule below to surface drift before it accumulates. (#1491 Phase D, Karpathy "lint" operation.)

aztecprotocol Skill

Principles for writing and reviewing cryptography/protocol documentation in barretenberg — PROTOCOL.md spec files, algorithm/implementation notes, and doc-comments on prover/verifier code. Use when authoring or editing a protocol spec, a design/algorithm note, a substantial math-bearing doc-comment, or an optimization/cost-rationale comment in prover/verifier/relation code, or when asked to review such a doc or comment for clarity and consistency.

hams-ollo Skill

Writes new Markdown documentation for the repository it is used in, grounded in the actual code. Handles READMEs (technical or for non-technical readers), architecture docs with Mermaid diagrams, setup and deployment guides, contributing guides, design docs, and architecture decision records. Use this whenever the user wants to create documentation that does not exist yet. Trigger on phrases like: "create a README", "write an architecture doc with mermaid diagrams", "document this project for non-technical users", "scaffold the repo docs", "set up the docs folder", "write a deployment guide", "create a CLAUDE.md for this repo", "we need a design doc for X", or any request to produce a new .md document describing the codebase or project. When the document already exists and the user wants it updated, revised, or its links fixed, use doc-revise instead. When the user does not know which document is wrong, use doc-sync instead.

hams-ollo Skill

Updates and revises existing Markdown documentation in place, without flattening its voice or rewriting more than asked. Reconciles a doc with the current code or project state, fixes cross-document links and references after files or folders have moved, keeps a set of docs internally consistent. Use this whenever the user wants to change documentation that already exists. Trigger on phrases like: "update the docs to reflect this", "I moved these files, fix the links", "make sure the linking across the docs is still valid", "revise the README with this new content", "move completed items to the changelog", "the docs are out of date after these changes", "add contextual emojis to the headings", or any request to edit, refresh, or reconcile existing .md files. When the document does not exist yet and needs to be created from scratch, use doc-author instead. When the user does not know which document is wrong, use doc-sync instead.

hams-ollo Skill

Decide how much review a change has earned, before reviewing it. Selects quick, standard, or deep from stated signals (reviewable changed lines, directory spread, trust-boundary risk flags, blast radius, documentation-only scope), reports the signal table and the rule that fired, then runs house-review at the selected depth. Use when the user asks for a review and the change is either trivially small or big enough that one uniform effort setting is wrong, or when they say "quick look", "deep review", "how carefully should I review this", "is this worth a full review", or ask for a review of a whole branch. An explicit depth from the user always wins and detection only fills the gap. It selects effort, it does not review: the rubric, the severities, and the report-only posture stay in house-review and the review-quality lens.

novainsilico Bundle

Create or update a Jinkō document from markdown through the jinko-sdk, including headings, tables, code blocks, links to Jinkō project items, uploaded images, and links to existing Jinkō References. Use this skill whenever the user wants to turn local markdown into a Jinkō document, refresh an existing document from edited markdown, prepare markdown so Jinkō renders cards and images correctly, or cite existing project References.

ooiyeefei Bundle

End-to-end User Acceptance Testing for web applications. Analyzes branch changes and specs to generate exhaustive test cases, sets up the local environment, executes tests via Playwright browser automation, and produces a pass/fail results report with screenshots and fix documentation. Use when the user says "run UAT", "test this feature", "UAT testing", "acceptance test", "test my branch", "generate test cases", or wants to verify a feature branch against its spec before merge.

openjiuwen-ai Bundle

Use this skill when you need to write and execute Python/R code to process, transform, and analyze data, delivering reproducible computational results with complete code-level methodology documentation. Supports statistical analysis, data transformation, visualization, method justification, and structured result output.

openjiuwen-ai Skill

Receives Domain Summaries (Knowledge Summary, Analysis Summary, or both) from the science-research-team orchestrator, performs cross-domain synthesis (identifying SUPPORTS/CONTRADICTS/INFORMS/INDEPENDENT connections), surfaces contradictions verbatim, and produces a formatted output per user requirements (or the default 7-section template if no format specified). NOT for performing research, conducting analysis, evaluating results, or resolving contradictions.

openjiuwen-ai Skill

Use this skill when a research workflow needs source-grounded evidence extraction from a `literature_sources.json` package or compatible source list. Produces an integration-ready evidence package with claims, evidence, citations, confidence/strength labels, quality notes, and partial results when some sources cannot be processed. Not for literature search, deduplication, final report writing, cross-source synthesis, or workflow coordination.

fnaith Skill

Searches multiple web sources, synthesizes findings, and produces cited research reports using delegated subagents. Use when the user asks to research a topic online, search the web, look something up, find current information, compare options, or produce a research report.

goodluckz Skill

把 Zotero 中提取的论文 .text 文件总结为中文摘要并/或整理成结构化 Markdown，保存到 Obsidian survey-vault 的 pages/ 目录。处理 CR 换行符、frontmatter 规范、表格碎片化、参考文献筛选等已知坑。Use when the user provides a `/Users/zhaoliang/Zotero/storage/<ID>/<n>.text` path along with requests like "总结这篇文章"、"写一千字摘要"、"中文摘要"、"整理成 Markdown"、"全文转 Markdown"、"convert this paper to markdown"、"summarize this paper".

igapyon Bundle

Use only when the user explicitly asks for igapyon-diary-writer, asks to create or update igapyon diary entries, asks to work with the diary repository as igapyon's own diary data, or asks for diary content that must follow igapyonv3 .src.md conventions. Do not use for Mikuku-authored Note articles, mikuku-articles, generic Japanese writing, or ordinary Markdown unless the diary repository or this skill is explicitly involved.

igapyon Bundle

Use only when the user explicitly asks for igapyon-qiita-writer, asks to create or revise a Japanese Qiita technical article in igapyon style, or clearly requests Qiita-like technical Markdown with front matter/tags or Note metadata. If the user only asks whether such a skill exists, mention this skill as an available option but do not apply it until asked.

igapyon Bundle

Use only when the user explicitly asks to apply or review igapyon's repository conventions for a local Git or GitHub repository, or explicitly mentions igapyon-repo-conventions. Covers repo-side .gitignore rules, .DS_Store exclusion, workplace/.gitkeep setup, .codex/skills exclusion, Java/Maven .mvn/jvm.config handling, README documentation of repository operation rules, and parent-directory checks for uncommitted materials across direct child Git repositories.

jp-solumhealth Bundle

Weekly pricing conversation coach for Solum Health sales calls. Pulls calls from Fireflies, extracts all pricing moments, scores each conversation against proven benchmarks, and delivers a coaching report with what worked, what didn't, and specific improvement recommendations. Use this skill when the user says "pricing coach", "pricing feedback", "review my pricing", "how did pricing go this week", "pricing report", "score my calls", "pricing review", "weekly pricing", "sales coaching", or any variation of wanting feedback on how pricing conversations went. Also trigger when the user asks to "run the pricing coach" or "check my pricing this week". Default period: last 7 days. User can specify a different date range.

jp-solumhealth Skill

Format feedback for the Solum platform team — new rules (eligibility, insurance, copay), bug reports, and feature requests — using the WHEN/THEN/Example framework with Trading Partner IDs. Use this skill when the user wants to send feedback to the team or eng, report a platform bug, request a rule change, write a feature request, or convert raw clinic feedback into implementable rules. Triggers: "feedback for the team", "write this up for eng", "report this to the team", "new rule for the platform", "feature request", "convert this into a rule", "regla para la plataforma", or when the user pastes raw clinic feedback about eligibility, insurance, or copay behavior that needs to go to engineering.

jp-solumhealth Skill

Generate concise investor reports for Solum Health. Pulls metrics from Google Sheets, analyzes customer conversations from Fireflies, and produces a structured DOCX report matching the investor update template. Use this skill when the user says "investor report", "investor update", "monthly report for investors", "board update", "generate investor deck", "how are we doing this month", or any variation of wanting a periodic investor-facing summary. Default period: previous calendar month. User can specify a different period.

jp-solumhealth Bundle

Produce branded conference recap one-pagers (1-2 page PDF) that position Solum Health as an industry thought leader. Use this skill whenever the user mentions a conference, summit, event, or expo they attended or want insights from. Also trigger on: "conference recap", "post conference insights", "event highlights", "conference one-pager", "summit recap", "what happened at [event]", "conference takeaways", "event summary", "write up from [event]", "key takeaways from [conference]", or anything involving turning conference attendance into a shareable client-facing document. Even if the user just names a conference ("HIMSS", "BHASe", "Becker's"), assume they want the full insight one-pager workflow unless they say otherwise.

jp-solumhealth Bundle

Build branded LinkedIn carousel PDFs optimized for engagement and virality. Use this skill when asked to create a LinkedIn carousel, document post, swipeable slides, or any multi-slide visual content for LinkedIn. Also triggers on "carousel", "slides for LinkedIn", "LinkedIn PDF", "swipeable post", or "document post".

k-dense-ai Bundle

Applies the reasoning style of Ilya Sutskever (deep learning pioneer, co-founder of OpenAI and Safe Superintelligence Inc.) to problems involving AI architecture, scaling laws, alignment, and research strategy. Reach for this skill whenever discussing machine learning paradigms, the limits of compute and data, AGI timelines, superintelligence safety, or deciding between hardcoding vs. learning. Trigger this skill for questions about next-word prediction, reinforcement learning efficiency, generalization gaps, and transitioning from brute-force scaling to fundamental research, even if the user doesn't explicitly name him.

krishnakanthb13 Skill

Updates standard project documentation files (README, CODE_DOCUMENTATION, DESIGN_PHILOSOPHY) to reflect the current state of the codebase.

krishnakanthb13 Skill

Generates standardized API documentation (OpenAPI/Markdown) for backend endpoints.

krishnakanthb13 Skill

Comprehensive workflow to prepare a project for public open-source release. Handles licensing, username normalization, code integrity checks, and documentation generation.

lhohan Bundle

A relentless interview to sharpen a plan or design, producing domain documentation as the conversation progresses.

arc-mcp Skill

Review what actually changed — in a transport, or in your unactivated drafts — by diffing each object's source and summarizing the change set with optional impact and quality signals. Produces a reviewable report (per-object unified diffs + risk flags), not a raw object dump. Use when asked to "review this transport", "what changed in TR X", "diff the objects in a transport", "show my pending changes before I activate/release", "prepare a transport/change review", or "what am I about to ship".

arc-mcp Skill

Produce stable, package-scoped Markdown documentation for many custom ABAP objects at once — classifies each by style (Classic/Modern/Mixed) and summarizes purpose and dependencies. Use when asked to "document this package", "generate onboarding docs for Z code", "seed a docs folder", or "knowledge transfer for this package".

sbusso Skill

Add PDF reading to ClaudeClaw agents. Extracts text from PDFs via pdftotext CLI. Handles WhatsApp attachments, URLs, and local files.

postmelee Skill

하이퍼-워터폴의 오늘할일 보드(`mydocs/orders/yyyymmdd.md`)를 작성·갱신한다. 마일스톤별 표 형식, 상태 갱신, 백로그 섹션 작성 규칙을 적용한다. task-start, task-stage-report, task-final-report, pr-merge-cleanup 절차에서 오늘할일을 갱신할 때도 본 SKILL의 형식을 따른다.

postmelee Skill

하이퍼-워터폴 타스크의 최종 보고와 PR 게시 절차를 적용한다. 최종 결과 보고서(`_report.md`) 작성, 오늘할일 완료 처리, 최종 커밋, publish/task{N} 원격 push, {BASE_BRANCH} 대상 Open PR 생성을 수행한다. 모든 단계 완료 후 PR 직전에만 호출.

postmelee Skill

하이퍼-워터폴 타스크의 단계 종료 절차를 적용한다. 단계별 완료 보고서(`_stage{N}.md`) 작성, 단계 소스와 보고서 묶음 커밋, 단계 검증 명령 실행을 수행한다. 한 단계가 끝나고 다음 단계 진입 직전에 호출.

flox Skill

Surface Forge plugin documentation when users ask "how does forge work", "forge help", "what commands are available", or need guidance on workflows, commands, or concepts. Use for onboarding, command reference, or workflow overview questions.

goiltpatpat Skill

Fan out isolated workers across slices or races and return one aggregated report. Use for /patpat-swarm, coverage matrices, parallel checks, or races with a declared selection rule.

hanzhcn Skill

口播稿一键生成幻灯片图片，通过 NotebookLM 生成中文幻灯片，PDF 转图片输出供剪映使用。Use when 用户说"生成PPT""生成幻灯片""做PPT图片""幻灯片""PPT"或提到口播稿背景图/视觉素材。

ievo-ai Skill

Use this skill when the user says "send feedback", "report a bug", "this didn't work", "I want to suggest a feature", "where do I file an issue for iEvo", or after iEvo has done something the user would want to comment on. Submits feedback about the iEvo plugin — bug reports, feature requests, suggestions, or general comments. Posts as a GitHub issue in `ievo-ai/skills` via `gh` CLI. When `/ievo:contributor-mode-on` has been enabled for this project, may also offer to attach the existing scrubbed tool-failure/permission-denial capture stream — still gated by the same Submit/Cancel confirmation as every other report.

ievo-ai Skill

Use this skill when the user wants to opt in to iEvo 'contributor mode' for this project — trigger words "turn on contributor mode", "enable contributor mode", "I am a contributor", "share more diagnostics with feedback", "widen feedback payload". Enables a project-local, off-by-default consent flag (`.ievo/contributor.flag`) that widens what `/ievo:feedback` MAY offer to attach to a filed report: the environment context it already collects for every report, plus — only when available — the existing scrubbed tool-failure/permission-denial capture stream from `/ievo:evo-auto-enable`. The existing per-report Submit/Cancel confirmation in `/ievo:feedback` is unchanged; this flag only widens the attachment OPTIONS offered and never auto-posts. Does NOT add a session-transcript export or standing consent to skip the per-report confirmation — both are separate, unbuilt proposals (see `## Scope` below).