agentsclimarketplace

Docs & writing

16,632 rows, by stacks then stars

3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid

  • Prompt writer

    Ken-Technology/cold-email-skills/prompt-writer Skill

    2★ repo

    Generate AI personalization prompts for cold email campaigns. Reads the AI variables from a campaign strategy and outputs detailed prompts you can run in any personalization tool or LLM to tailor each email per prospect. Use after campaign strategy, or when creating prompts for an existing sequence. Triggers on "write prompts for this campaign", "generate personalization prompts".

  • Minecraft testing

    AIKUSAN/minecraft-agent-skills-bundle/.agents/skills/minecraft-testing Skill

    2★ repo

    Write automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.

  • Minecraft testing

    AIKUSAN/minecraft-agent-skills-bundle/.codex/skills/minecraft-testing Skill

    2★ repo

    Write automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.

  • Minecraft testing

    AIKUSAN/minecraft-agent-skills-bundle/plugins/minecraft-codex-skills/skills/minecraft-testing Skill

    2★ repo

    Write automated tests for Minecraft mods and plugins for 1.21.x. Covers NeoForge GameTests (@GameTest annotation, GameTestHelper assertions, test structure placement), Fabric game tests (fabric-gametest-api-v1), unit testing non-Minecraft logic with JUnit 5, MockBukkit for Paper/Bukkit plugin testing (mock server, mock player, event dispatching, inventory checking), integration testing with a test server via Gradle, and GitHub Actions CI workflows that run GameTests headlessly. Includes patterns for mocking registries, testing event handlers, testing commands, and test-driven development for Minecraft projects. Use when the user asks about testing Minecraft mods or plugins, writing GameTests, setting up MockBukkit, or configuring CI for Minecraft projects.

  • Backlog refine

    carinyaparc/skills/skills/backlog-refine Skill

    2★ repo

    Use to groom an existing backlog or judge whether a breakdown is ready to commit to — reprioritise, split oversized epics or stories, re-estimate, defer misaligned items, and check sprint readiness of docs/product/backlog.md or docs/work/{epic}/tasks.md. Triggers on "groom the backlog", "refine the backlog", "is this sprint-ready", "are these stories ready", "reprioritise", "this epic is too big", "clean up the backlog". Amends in place and reports a verdict. Do NOT use to create a backlog or write new stories and tasks (tasks), plan a sprint (sprint-planning), review a finished sprint (sprint-retro), or verify an epic against its acceptance criteria (validate).

  • Design

    carinyaparc/skills/skills/design Skill

    2★ repo

    Use when the user wants epic-level technical design at docs/work/{epic}/design.md, walking-skeleton or TDD design. Pass epic slug or ID (CHK01). Cite solution.md — do not re-narrate architecture. Triggers on "design CHK01", "write the epic design", "how should we build this epic". For reviewing an existing design.md, use docs-review instead. Do NOT use for epics or stories (tasks), task Gherkin (tasks), system-wide architecture (solution), ADR write (adr), or code implementation (implement).

  • Docs review

    carinyaparc/skills/skills/docs-review Skill

    2★ repo

    Use when the user wants a set of documents reviewed — a docs folder, a wiki, a handbook, a repo's markdown, or any collection of written material. Checks that each document is well written and well structured, that boundaries between documents are clear with no duplication, and that the set is consistent and cohesive. Triggers on "review the docs", "are these docs any good", "is our documentation consistent", "do these docs overlap", "audit the documentation". Works on any doc set in any format or tool. Read-only: produces a report and changes nothing. Do NOT use to write or amend a document, to review code (code-review), or to review rendered UI (ux-design-review).

  • Implement

    carinyaparc/skills/skills/implement Skill

    2★ repo

    Use when the user wants to implement a task in code against an approved design.md and docs/work/{epic}/tasks.md. Triggers on "implement CHK01-01", "build this task", "write the code for this story". Reads the design and acceptance criteria, writes code and tests, runs the project's full validation suite, and commits in logical units. Do NOT use for code review (code-review), addressing review feedback (code-review-fix), changing how existing UI looks or behaves (ux-design-fix), writing tasks (tasks), or writing a design (design).

  • Product

    carinyaparc/skills/skills/product Skill

    2★ repo

    Use when the user wants a product strategy doc, PRD, pitch, vision, personas, or outcomes at docs/product/product.md. Drafts or re-authors the document. Triggers on "write the PRD", "draft a product pitch", "who are our personas". For reviewing or critiquing an existing product.md, use docs-review instead. Do NOT use for phased delivery plan (roadmap), epics or backlog (tasks), architecture (solution), tasks or Gherkin (tasks), or implementation (implement).

  • Roadmap

    carinyaparc/skills/skills/roadmap Skill

    2★ repo

    Carinya Parc Agent Skills

  • Solution

    carinyaparc/skills/skills/solution Skill

    2★ repo

    Use when the user wants to write system architecture at docs/architecture/solution.md (stub or full arc42-lite). Drafts or re-authors the document. Triggers on "write the architecture", "solution design", "arc42". For reviewing or critiquing an existing solution.md, use docs-review instead. Do NOT use for business strategy (product), delivery phases (roadmap), epic list (tasks), per-epic design.md (design), task Gherkin (tasks), or ADR files (adr write). Story AC belongs in docs/work/{epic}/tasks.md.

  • Sprint planning

    carinyaparc/skills/skills/sprint-planning Skill

    2★ repo

    Use when the user wants to plan a sprint before it starts — set the sprint goal, pull committed scope from the backlog and epic tasks.md files, account for carry-over and capacity, and record dependencies, risks, and the sprint definition of done at docs/work/sprint-{id}/plan.md. Triggers on "plan sprint 3", "what should we commit to", "set up the next sprint", "sprint planning". Do NOT use to review a finished sprint (sprint-retro), write stories or task Gherkin (tasks), groom the backlog (backlog-refine), re-sequence delivery phases (roadmap), or sign off an epic (validate).

  • Sprint retro

    carinyaparc/skills/skills/sprint-retro Skill

    2★ repo

    Use when the user wants to run a retrospective after a sprint ends — compare what was committed in plan.md against what actually shipped, surface themes with evidence, and record actions with owners routed to the skill that will action them, at docs/work/sprint-{id}/retrospective.md. Triggers on "run the retro", "sprint retrospective", "what went wrong last sprint", "how did sprint 3 go". Do NOT use to plan the next sprint (sprint-planning), sign off an epic against its acceptance criteria (validate), run a cross-document alignment pass (docs-review), or review a diff (code-review).

  • Tasks

    carinyaparc/skills/skills/tasks Skill

    2★ repo

    Use to decompose anything into delivery work — a product strategy and roadmap into epics, an epic or its design into stories and tasks with Gherkin acceptance criteria, or an external spec, RFC, or PRD into both in one pass. Writes docs/product/backlog.md and docs/work/{epic}/tasks.md. Triggers on "break this spec into a backlog", "write the epics", "decompose checkout-foundation", "turn this RFC into tickets", "write tasks for CHK01", "what stories do we need". EARS with --ears. Do NOT use to groom an existing backlog or check sprint readiness (backlog-refine), write epic design (design), write architecture (solution), phase the delivery (roadmap), implement code (implement), or sign off an epic (validate).

  • Ux design review

    carinyaparc/skills/skills/ux-design-review Skill

    2★ repo

    Carinya Parc Agent Skills

  • Validate

    carinyaparc/skills/skills/validate Skill

    2★ repo

    Use when the user wants final epic completion sign-off: every task in docs/work/{epic}/tasks.md verified against Gherkin AC and roadmap phase exit criteria. Triggers on "validate CHK01", "is this epic done", "sign off the epic". Builds an acceptance matrix with evidence, updates task and epic status, and produces a validation report. Do NOT use for PR or branch code review (code-review), writing tasks (tasks), sprint retrospective (sprint-retro), or drafting the breakdown (tasks) or design.

  • Weekly update

    bogdanbaciu21/skills/weekly-update Skill

    2★ repo

    Draft a weekly stakeholder update for any software project. Use when the user asks for a weekly update, Friday email, status report, sprint summary, or stakeholder progress report. Pulls commits from git and issue counts from the project's tracker (GitHub Issues by default; Linear or Jira when an MCP server, API token, or CLI is available), asks a short set of clarifying questions, and produces a draft markdown file in docs/weekly-updates/. Optionally renders an HTML email using a brand template if one is configured.

  • Analytics reporting review

    jukrap/ai-agent-playbook/skills/data/analytics-reporting-review Skill

    2★ repo

    Use when reviewing metrics, dashboards, reports, KPI definitions, chart/table consistency, analytics queries, segmentation, freshness, or reporting caveats.

  • Legacy reporting printing

    jukrap/ai-agent-playbook/skills/legacy/legacy-reporting-printing Skill

    2★ repo

    Use when maintaining report generation, print preview, PDF/Excel export, barcode/label printing, invoices, templates, or printer/device-specific output flows.

  • Documentation artifact package

    jukrap/ai-agent-playbook/skills/project/documentation-artifact-package Skill

    2★ repo

    Use when bundling docs, runbooks, reports, evidence, or handoffs into a documentation package.

  • Natural writing humanization

    jukrap/ai-agent-playbook/skills/project/natural-writing-humanization Skill

    2★ repo

    Use when editing Korean or English prose so it reads naturally while preserving facts, meaning, technical terms, and author intent.

  • Project doc system

    jukrap/ai-agent-playbook/skills/project/project-doc-system Skill

    2★ repo

    Use when creating, reorganizing, or reviewing project AI docs such as AGENTS.md, .ai-agent-playbook, project specs, plans, maps, runbooks, worklogs, or local-only documentation.

  • Release notes changelog

    jukrap/ai-agent-playbook/skills/project/release-notes-changelog Skill

    2★ repo

    Use when preparing release notes, changelogs, migration notes, rollback notes, or known issues.

  • Spec audit docs

    ainova-systems/intelligence-dev-packs/packs/spec/skills/spec-audit-docs Skill

    2★ repo

    Audit documentation claims against the code; report drift vs violation

  • Spec document

    ainova-systems/intelligence-dev-packs/packs/spec/skills/spec-document Skill

    2★ repo

    Write or update one docs-substrate artifact - feature, rule, glossary, model, or architecture - from code, for owner review

  • Truestack task scheduling

    adtn0810/truestack/skills/truestack-task-scheduling Skill

    2★ repo

    Set up work that runs automatically later or on a recurring cadence — a daily check, a weekly report, a periodic sync, a deferred run — instead of doing it once now. Use whenever the user says "every day", "each morning", "weekly", "nightly", "cron", "schedule this", "remind me", "run this at", or wants a task to recur or fire in the future. (A standing behavior rule — hooks or settings config — is not a schedule.) Produces a self-contained job spec (trigger, the exact prompt the run executes, delivery, and failure policy) and wires it to the host's scheduler.

  • Consulting problem solving

    sfrangulov/skills/consulting-problem-solving Skill

    2★ repo

    **Consulting Problem Solving Framework**: An interactive, user-led approach to solving complex business and organizational problems using structured consulting methodology. You act as a consulting associate; the user acts as the consulting partner who drives decisions. Walks through problem definition, MECE structuring, prioritization, work planning, analysis, synthesis, recommendations, and communication — with the user providing input, making choices, and reviewing deliverables at every step before moving forward. Produces deliverables at each stage — markdown working docs, spreadsheets for data analysis, and final slide content (.md) or approved content for a vertical document. This skill owns content and structure only — visual rendering, styling, and deck/document generation are handled by downstream builder skills. All final prose is polished using an integrated Strunk & White writing style guide. Use this skill whenever the user mentions: strategy consulting, problem solving framework, issue tree, MECE, hypothesis-driven, pyramid principle, 80/20 analysis, root cause analysis, business case analysis, strategic recommendation, case interview prep, structured thinking, or any request to systematically break down and solve a complex problem. Also trigger when someone says things like 'help me think through this problem', 'I need a structured approach to X', 'how would a consultant approach this', or 'analyze this business situation'. Trigger when the request clearly calls for structured analytical problem solving with deliverables.

  • Research pipeline

    sfrangulov/skills/research-pipeline Skill

    2★ repo

    Disciplined multi-source research pipeline that produces a verifiable, citation-backed report — orchestrated subagents, source-discipline, content-addressed snapshots, a deterministic→judge verification funnel, and a mandatory adversarial fact-check pass. Use when a deep-research document (best-practices canon, technology evaluation, claims that downstream code or decisions will lean on) must be source-grounded, fact-checked, and reproducible across sessions or machines — not a quick lookup. Explicit-invocation only.

  • Engifoundry docs

    caoyuan-fire/engi-foundry-skill/skills/engifoundry-docs Skill

    2★ repo

    Create a detailed human-readable document from EngiFoundry project records when the user explicitly requests documentation, a report, guide, specification, detailed summary, or handoff document.

  • Docs memory maintainer

    rumotion/ai-agent-project-template/.agents/skills/docs-memory-maintainer Skill

    2★ repo

    Updates project documentation and Memory Bank files after meaningful changes. Use after features, refactors, setup changes, architecture decisions, or user requests to update memory.

  • Docs memory maintainer

    rumotion/ai-agent-project-template/.cline/skills/docs-memory-maintainer Skill

    2★ repo

    Updates project documentation and Memory Bank files after meaningful changes. Use after features, refactors, setup changes, architecture decisions, or user requests to update memory.

  • Weekly report

    14790897/my-skills/public/weekly-report Skill

    no license2★ repo

    AI Agent 小团队实习生每周工作周报生成器。用户输入本周做了什么,AI 按结构化模板输出完整周报,直接输出到对话中,不创建文件。周报原则:先给结论,再给证据;风险需写影响+动作+决策需求;下周计划按优先级排列,明确可验收产物。

  • Daily report

    14790897/my-skills/skills/daily-report Skill

    no license2★ repo

    AI Agent 小团队实习生每日工作记录生成器。用户输入当天做了什么,AI 按结构化模板输出完整日报,直接输出到对话中,不创建文件。

  • Docx work report

    14790897/my-skills/skills/docx-work-report Skill

    no license2★ repo
  • Weekly report

    14790897/my-skills/skills/weekly-report Skill

    no license2★ repo

    AI Agent 小团队实习生每周工作周报生成器。用户输入本周做了什么,AI 按结构化模板输出完整周报,直接输出到对话中,不创建文件。周报原则:先给结论,再给证据;风险需写影响+动作+决策需求;下周计划按优先级排列,明确可验收产物。

  • Intel competitor monitoring

    b2bforce/b2bforce/.agents/skills/intel-competitor-monitoring Skill

    2★ repo

    Files-only competitor website monitoring for a shared B2BForce workspace. Use to maintain competitor profiles, monitored page lists, page snapshots, change notes, and weekly report inputs under workspace/intelligence/. Read firm profile first; for firm profile setup, see firm-context.

  • Intel weekly report

    b2bforce/b2bforce/.agents/skills/intel-weekly-report Skill

    2★ repo

    Generate a weekly competitive-intelligence report from monitored competitor page changes within a date range, with an AI business-impact summary and per-page change list. Use when the user wants a weekly digest, monitoring summary, or shareable intel report. Read firm profile and monitoring files first.

  • Marketing content blog post

    b2bforce/b2bforce/.agents/skills/marketing-content-blog-post Skill

    2★ repo

    Write an 800-1500 word B2B blog post in Markdown from a content idea. Use when content_type is blog_post. Applies stage-specific frameworks and Exa reference articles. Output to workspace/marketing/content/drafts/blog/. For LinkedIn or X use marketing-content-linkedin-post or marketing-content-x-post instead.

  • Tool weasyprint

    b2bforce/b2bforce/.agents/skills/tool-weasyprint Skill

    2★ repo

    Render a Markdown document to a print-ready PDF with WeasyPrint — proposals, case studies, reports. Use when a workspace artifact has to leave the repo as a client-facing document, or when the user asks for a PDF, a sendable proposal, or branded output. Strips frontmatter; CSS-overridable for firm branding.

  • Generate tech profile

    jasonChen0604/codebase-to-portfolio/skills/generate-tech-profile Skill

    2★ repo

    Generate a personal tech profile and project mapping from all latest-version project docs. Produces one Markdown file per configured language (tech-profile-<lang>.md), each a structured Markdown suitable for building a personal website skill tree / mind map. Triggers when the user says "generate tech profile", "build tech profile", "generate skill tree", "生成技術檔案", "產出個人技術樹", or "建立技術側寫".

  • Clinical reports

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/clinical-reports Skill

    2★ repo

    Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.

  • Docx

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/docx Skill

    2★ repo

    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.

    The same file is in 31 other repositories

  • Markdown mermaid writing

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/markdown-mermaid-writing Skill

    2★ repo

    Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.

  • Peer review

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/peer-review Skill

    2★ repo

    Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.

  • Scientific writing

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/scientific-writing Skill

    2★ repo

    Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.

  • Xlsx

    Lord1Egypt/scientific-agent-toolkit/scientific-skills/xlsx Skill

    2★ repo

    Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

    The same file is in 29 other repositories

  • Asa reader layer writer

    3yesore/LetUenforskills/skills/asa-reader-layer-writer Skill

    2★ repo

    Use when turning structured skill decomposition artifacts into beginner, expert, report, or Obsidian reading layers.

  • Bmob mcp

    bmob/agent-skills/skills/bmob-mcp Skill

    2★ repo

    Use when the user has the Bmob MCP server configured (http://mcp.bmobapp.com/mcp) and wants to perform LIVE operations against their Bmob backend cloud project from the IDE. Triggers: 'list bmob tables', 'show bmob schema', 'create bmob table', 'add a row to bmob', 'update bmob record', 'delete bmob data', '生成 bmob curl', 'design bmob schema', '上传云函数', '部署云函数', '发布云函数', '同步云函数', '同步函数', '拉取云函数', '下载云函数', '调用云函数', '执行云函数', 'invoke cloud function', 'run cloud function', '一键部署网站', '静态托管', '部署静态站点', 'deploy static site', 'deploy website'. Provides 12 tools: get_project_tables (ALWAYS call first to discover schema before any write), create_table, add_single_data, update_single_data, delete_single_data, generate_code, deploy_cloud_function, invoke_cloud_function, list_cloud_functions, get_cloud_function, deploy_static_site, mcp_endpoint_mcp_post. NOT for writing client/SDK code that will ship in the user's app — for that use bmob-database-{javascript,android,ios,swift,flutter,restful}. NOT for ACL / role design (use bmob-acl-and-roles) or cloud function development (use bmob-cloud-function-development).

  • Bmob

    bmob/agent-skills/skills/bmob Skill

    2★ repo

    Use whenever the user mentions Bmob backend cloud (Bmob, BmobApp, bmobapp.com, Bmob 后端云) for ANY task: design data tables, perform CRUD, sign up / login users, upload files, push notifications, send SMS, accept payments, write or invoke cloud functions, configure ACL / roles, debug error codes, or operate the project via the Bmob MCP server. This is the routing entry — it dispatches to platform-specific skills: bmob-database-{javascript,android,ios,swift,flutter,restful}, bmob-auth-*, bmob-storage-*, bmob-cloud-function-*, bmob-mcp, bmob-error-codes, bmob-bql, bmob-acl-and-roles. For operation-level MCP vs SDK vs REST routing, read shared/operation-routing.md. NOT a substitute for those sub-skills — once the platform and feature are clear, read and follow the matching sub-skill before writing code.

  • Keeping docs fresh

    gg-mo/repo-hygiene/skills/keeping-docs-fresh Skill

    2★ repo

    Use when changing a public API surface — renamed export, changed signature/return type, new or removed flag/route/env var, schema migration, deprecation — before committing, so README, docs/, CHANGELOG, and inline references stay coherent with the code

  • Writing commit messages

    gg-mo/repo-hygiene/skills/writing-commit-messages Skill

    2★ repo

    Use when drafting any commit message — sets format (imperative subject under 72 chars, explanatory body when the why isn't obvious from the diff) and prevents the "Fix X" one-liner reflex for non-trivial fixes

  • Writing docstrings

    gg-mo/repo-hygiene/skills/writing-docstrings Skill

    2★ repo

    Use when writing or modifying any function, method, class, or source file in a repo using repo-hygiene — public API, internal helpers, and new files all require docstrings; only one-line lambdas and trivial accessors are excluded

  • Lean proof

    r-irbe/proof-skills/skills/_overrides/lean-proof Skill

    2★ repo

    USE FOR: writing Lean 4 proofs one tactic at a time, fixing tactic errors by priority, planning sorry placeholders, cleaning a working proof, resolving dependent-type rewriting failures. DO NOT USE FOR: reviewing existing proofs (use @lean-proof-review), project-wide quality assessment (use @lean-quality-engine), minimising an error into a bug report (use @lean-mwe), discovering tactics or API (use @lean-research), authoring new theorem statements (use @lean-specification), repairing toolchains (use @lean-setup). TRIGGERS: prove, tactic, sorry, unsolved goals, motive is not type correct.

  • Lean doc feedback

    r-irbe/proof-skills/skills/lean-doc-feedback Skill

    2★ repo

    USE FOR: reviewing a Lean documentation draft, flagging undefined terms, suggesting cross-links, scoring readability against a rubric. DO NOT USE FOR: rewriting prose end-to-end (use @lean-doc-improvement), generating new blueprints (use @lean-blueprint). TRIGGERS: doc-review, readability, doc-feedback.

  • Lean doc improvement

    r-irbe/proof-skills/skills/lean-doc-improvement Skill

    2★ repo

    USE FOR: Update academic papers, technical reports, and documentation based on results from Lean 4 formalization. Use when formal verification reveals paper imprecisions, missing hypotheses, sharper bounds, new insights, or when metrics need synchronization. Covers paper appendix updates, verification tables, erratum entries, insight propagation, and metric synchronization between Lean and documents. DO NOT USE FOR: extracting requirements from papers (use @lean-doc-requirements); blueprint generation (use @lean-blueprint); report compilation (use @lean-report). TRIGGERS: update paper, doc improvement, paper revision, documentation update from Lean, doc-feedback consumer.

  • Lean quality engine

    r-irbe/proof-skills/skills/lean-quality-engine Skill

    2★ repo

    USE FOR: assessing overall Lean 4 project quality across seven dimensions (soundness, faithfulness, completeness, novelty, elegance, integration, documentation); preparing for milestones; orchestrating QA gates that wrap enforcement scripts, council reviews, coverage tracking, and health monitoring. DO NOT USE FOR: running a single enforcement script (use @lean-enforcement); reviewing one proof (use @lean-proof-review); council deliberation itself (use @lean-review-council); writing retros (use @lean-retro-methodology). TRIGGERS: QA, quality gate, milestone check, project health, qa-engine, quality score, QA lifecycle.

  • Lean report

    r-irbe/proof-skills/skills/lean-report Skill

    2★ repo

    USE FOR: converting a Lean 4 project blueprint into a publication-grade LaTeX report — blueprint artifact ingestion (extracted LaTeX nodes, dependency DAG, JSON metadata), per-chapter narrative generation with mathematical prose, dependency-driven cross-referencing, figure generation (dependency graphs, module maps, coverage tables), and LaTeX → PDF compilation via the 6-stage INGEST → PLAN → NARRATE → ILLUSTRATE → ASSEMBLE → COMPILE pipeline. DO NOT USE FOR: generating the blueprint itself (use @lean-blueprint); writing one chapter without the pipeline (use @lean-doc-improvement); reviewing a finished report (use @lean-review-council); spec lifecycle (use @lean-specification). TRIGGERS: blueprint to report, generate report, latex pdf, project-report.tex, narrate chapter, dependency figure, blueprint compile.

  • Lean specification

    r-irbe/proof-skills/skills/lean-specification Skill

    2★ repo

    USE FOR: Design theorem specifications for Lean 4 proofs. Use when planning new theorems, lemmas, definitions, or tactics. Covers the three-part specification (requirements, design, documentation), lifecycle management, dependency analysis, and integration with the review council. DO NOT USE FOR: actual proof writing (use @lean-proof); requirement extraction (use @lean-doc-requirements); review (use @lean-proof-review). TRIGGERS: specification, theorem spec, three-part spec, lemma plan, tactic plan.

  • Spec

    JeanIsahakyan/skills/plugin/skills/spec Skill

    no license2★ repo

    Turn a fuzzy product idea into a precise, written feature spec / PRD BEFORE any code — by interviewing the user with plain-language PRODUCT questions only and deriving every technical decision automatically from the existing codebase (never asking the user a tech question). The output is a single SPEC.md with a hard wall: narrative product behaviour on top (reads like a PM wrote it), a derived technical appendix sealed at the bottom (reads like an engineering handoff). Use this whenever the user wants to spec a feature, write a PRD, formalize requirements, design a flow, document how a behaviour should work, or turn a vague ask into a contract before implementation: "spec this", "write a spec for X", "design the X flow", "PRD for X", "how should this feature work", "let's spec out X", "formalize requirements for Y". Runs a codebase-context agent (reads the repo) + a product-interviewer loop (open-ended questions until coverage converges) + a spec-writer agent. Best for any non-trivial feature where the product intent is fuzzy but the stack is already established.

  • Research paper writing

    john-data-chen/hermes-agent-backup/skills/research/research-paper-writing Skill

    2★ repo

    Write ML papers for NeurIPS/ICML/ICLR: design→submit.

    The same file is in 1 other repository