agentsclimarketplace

Docs & writing

16,621 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

  • Board reporting

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/board-reporting Skill

    0★ repo

    When to activate: board deck, board meeting, board of directors, board update, board materials, pre-read, board presentation, governance reporting

  • Copywriting

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/copywriting Skill

    0★ repo

    When to activate: copywriting, conversion copy, headlines, AIDA, PAS, BAB, CTA writing, sales pages, landing page copy, ad copy, storytelling, persuasion

  • Prd patterns

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/prd-patterns Skill

    0★ repo

    When to activate: PRD, product requirements document, feature spec, functional spec, requirements writing, acceptance criteria, edge cases

  • Swift localization

    Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/swift-localization Skill

    0★ repo

    When to activate: Swift localization, String Catalogs, NSLocalizedString, pluralization, date/number formatting, multi-language apps

  • Hhh dialect verify report

    Srltas/claude-skills/hhh-dialect-verify-report Skill

    0★ repo

    One-shot CUBRID dialect verification + report. Runs the hibernate-core test suite against one or ALL CUBRID versions, diffs pass/fail vs a baseline (a prior run's JSON, results dir, or .tgz), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use when you want the full 'verify → measure → report' pipeline for a CUBRIDDialect change in one go, or to test across all CUBRID versions. Composes the hhh-dialect-verify and report skills. Triggers on phrases like 'dialect 검증하고 리포트까지', 'CUBRID 전체 버전 테스트 + 보고서', 'verify the dialect and write the report', 'run all CUBRID versions and report'.

  • Jdbc ctp verify report

    Srltas/claude-skills/jdbc-ctp-verify-report Skill

    0★ repo

    One-shot CUBRID JDBC driver verification + report. Builds the CUBRID JDBC driver, runs the CTP JDBC test suite against CUBRID, diffs pass/fail vs a baseline (a prior run's JSON, CTP result dir, or test-jdbc.xml), classifies broken cases (VerifyError, conversion, broker/env, …), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use to verify a JDBC driver change or a Java-version/build-target change (e.g. v50 1.6 vs v52 1.8) end to end. Composes parse_ctp.py + the report skill. Triggers on phrases like 'JDBC 드라이버 검증', 'CTP 돌려', 'ctp jdbc 실행하고 리포트', 'verify the JDBC driver with CTP', 'build driver and run CTP'.

  • Jira draft

    Srltas/claude-skills/jira-draft Skill

    0★ repo

    Draft a CUBRID JIRA issue (bug or task) with a concise English title and a Korean body under English section headers (Description as easy-to-read prose; the other sections in bullet style, 개조식). Use when you need to write up a CUBRID JIRA issue from the current work: a bug report (Description / Test Build / Repro / Expected / Actual / Additional Info) or a task/improvement (Description / Specification Changes / Implementation / Acceptance Criteria / Definition of Done). Produces a copy-paste draft only; it does not post to JIRA. It is the reverse of jira-fetch (which downloads an issue). Triggers on phrases like 'CUBRID JIRA 이슈 작성', 'jira 버그 리포트 초안', '이 작업 jira 이슈로 정리', 'draft a CUBRID jira issue', 'write a jira bug report'.

  • Jira fetch

    Srltas/claude-skills/jira-fetch Skill

    0★ repo

    Download a JIRA issue to a local Markdown file to use as working context, via the Srltas/jira-to-md-downloader tool. Give it one or more issue keys (e.g. CBRD-1234, TOOLS-4888, APIS-1079, CUBRIDQA-123) and it fetches each issue's summary + description as <KEY>.md, then loads it into the session so you can work against the ticket. Built for Jira Server/Data Center (REST API v2 + HTTP Basic auth); the target is CUBRID's Jira Server at jira.cubrid.org (any project: CBRD, TOOLS, APIS, CUBRIDQA, ...), and any other Jira Server instance works by setting JIRA_URL. Atlassian Cloud (e.g. Hibernate HHH at hibernate.atlassian.net) is NOT supported as-is. It is the reverse of writing an issue up to JIRA. Triggers on phrases like 'CBRD-1234 내용 가져와', '이 이슈 md로 내려받아', 'jira 이슈 다운로드해서 참고', 'fetch jira issue as markdown'.

  • Note

    Srltas/claude-skills/note Skill

    0★ repo

    Record an exploration note (PoC, review, code analysis, or any work without a JIRA issue) as a Markdown file in your public work-docs repo. Give it a free-form category and a slug and it scaffolds <category>/<YYYY-MM-DD>-<slug>.md from an exploration template (목적/배경/범위·방법/발견/결론/다음 단계/참고), fills it from the session, and commits it. While researching, actively use the collection's lookup/analysis skills (cubrid-manual, cmt-manual, and Understand-Anything if installed) so findings are verified, not asserted from memory. Complements the worklog skill, which is for issue-keyed work. The repo is PUBLIC, so keep internal-only detail in the master DOCX. Triggers on phrases like 'PoC 노트 남겨', '검토 노트 작성', '코드 분석 기록', 'record an exploration note', 'note this analysis'.

  • Report

    Srltas/claude-skills/report Skill

    0★ repo

    Generate a CUBRID-house-style Korean analysis report as a Word (.docx): error analyses, code analyses, issue write-ups, before/after comparisons, and status/investigation reports. Builds the .docx with docx-js (the engine behind Anthropic's docx skill) from a JSON spec, embedding matplotlib charts, reproducing the exact design: centered cover (navy 23pt title), auto table of contents, navy/blue numbered headings, and bordered tables with row-level color coding (sky-blue header, green pass rows, red fail rows). Use when the user wants a Word report or structured document summarizing analysis, findings, comparisons, or current status of Hibernate/JDBC/CUBRID work. Triggers on phrases like 'write a report', '보고서 만들어', 'Word 문서로 정리', 'docx로 작성', 'analysis report', '검증 보고서', '비교 분석 문서'.

  • Worklog

    Srltas/claude-skills/worklog Skill

    0★ repo

    Record a piece of issue work as a Markdown note in your public work-docs repo, for a shareable, PR-linkable trail (the GitHub-visible record that complements the internal master DOCX). Give it a CUBRID Jira key (CBRD, TOOLS, APIS, CUBRIDQA, ...) or a Hibernate HHH key (or a topic slug) and it scaffolds <KEY>/<KEY>-<slug>.md from a consistent template (배경/원인/변경/검증/결과/링크), fills it from the session's work, and commits it. Pairs with jira-fetch for issue context. The repo is PUBLIC: keep internal-only detail in the master DOCX. Triggers on phrases like '작업 기록 남겨', 'worklog 작성', '이 이슈 문서로 정리해서 커밋', 'record this issue's work as markdown', 'publish a work note for CBRD-1234'.

  • Readme writer

    Punpun1643/claude-skills/readme-writer Skill

    no license0★ repo

    Write, generate, overhaul, or fix a project's README.md (or any "readme", repo front page, or top-level project documentation). Use this skill whenever the user wants to create or improve a README, document a repo, or figure out how to present a codebase to readers — covering libraries and packages, CLI tools, research/ML repos, web apps, services, and developer tooling. Trigger even when the user only says things like "document this project", "write docs for my repo", "make a readme", or points at a codebase and asks how to present it, even if the word "README" never appears.

  • Repurpose

    lumizone/social-content-os-claude-skill/skills/repurpose Skill

    0★ repo

    Break one long-form asset into a batch of social posts across formats and channels (the Content Flywheel). Use when the user has a YouTube script, podcast transcript, newsletter, blog post, or webinar and wants to turn it into social content, or says "repurpose ten artykul", "z tego long-forma zrob posty", "rozbij na content", "turn this into posts", "make social content from this", "atomize this", "content flywheel". Deconstructs the source into N carousels, N text/ caption posts, N short-video hooks+scripts, and a thread, each mapped to a channel and funnel stage, following Best of Nine and multi-channel architecture. Hands pieces off to hook-lab, carousel-builder, and caption-writer.

  • Draft writer

    robdasi/skills/content-pipeline/draft-writer Skill

    0★ repo

    Write the article to the outline, in the site's real voice, with every number sourced and nothing recycled. Holds the voice defaults and the anti-detection blocklist, front-loads the citable answer, weaves links into real sentences, uses the one unique E-E-A-T story, and never invents a statistic. Run after outline-drafter. This is the method, not a magic writer. Produces a draft and stops.

  • Content preflight

    robdasi/skills/content-preflight Skill

    0★ repo

    Run the 12-point pre-write checklist before writing any SEO article or page. Turns a target keyword into a research-backed content brief: search intent, content gaps, real People Also Ask, semantic terms, entities to cite, internal links, the EEAT angle, and an outline. Use this BEFORE writing any piece of SEO content so the page is built on what actually ranks, not a guess. It stops at the brief. Writing to the brief is the next step (yours, or your writer's).

  • React docs writing

    jaballer/react-claude-skills/react-docs-writing Skill

    0★ repo

    Documentation patterns for React take-home projects and interview builds where documentation is an explicit deliverable — README structure (Overview / Decisions / Tradeoffs / How to Run / What's Next), in-code "why" comments (sparse, surgical), the brief-restate header at the top of the entry file, DESIGN.md / decisions log format, the "considered and rejected" template, PR description writeups, what NOT to document. Use whenever the project asks for documentation, especially for take-home interviews like the Netlify Senior UX Engineer technical project. Triggers on "README", "documentation", "design doc", "decision log", "DESIGN.md", "PR description", "code comments", "explain my code", "write docs", "take-home", "project deliverable", "Netlify project", "interview docs".

  • React onboarding docs

    jaballer/react-claude-skills/react-onboarding-docs Skill

    0★ repo

    React patterns for product onboarding flows and documentation sites — multi-step flows, progress indicators, empty states, contextual hints, code-block components, TOC sidebars, on-this-page nav, callouts, copy-buttons, search, syntax highlighting. Use when building onboarding UI, product tours, documentation pages, knowledge bases, or developer-facing reference sites. Triggers on "onboarding", "tour", "walkthrough", "empty state", "tooltip", "documentation", "docs site", "code block", "TOC", "table of contents", "callout".

  • React resources

    jaballer/react-claude-skills/react-resources Skill

    0★ repo

    Curated authoritative documentation URL library for React 19, accessibility (WAI-ARIA APG, WebAIM), performance (web.dev Core Web Vitals), HTML/CSS platform (MDN), forms (Zod, react-hook-form), testing (Testing Library, Playwright), Next.js App Router, TypeScript, and tooling — indexed by problem keyword for quick lookup during interview builds. Claude can WebFetch any of these URLs for current authoritative content when inline knowledge isn't enough. Use when you need to verify a pattern, look up a spec, or pull in primary-source docs mid-build. Triggers on "where to find", "documentation for", "spec for", "look up", "research", "reference", "WAI-ARIA", "MDN", "web.dev", "React docs", "Next docs", "Tailwind docs", "what does X say about", "authoritative".

  • React senior ux

    jaballer/react-claude-skills/react-senior-ux Skill

    0★ repo

    Senior UX Engineer-level React orchestrator — opening moves, decision framework, and routing to specialized React skills (component design, a11y, styling, performance, marketing patterns, onboarding/docs, interview narration). Use when starting any React component build, UI feature, technical interview task, marketing-site work, product onboarding, or documentation site work. Triggers on "React", "component", "UX engineer", "interview build", "landing page", "onboarding", "docs site", or any prompt that mixes UI + code judgment.

  • Error handling

    SkillMedev/ai-engineer-toolkit/skills/error-handling Skill

    0★ repo

    Designs typed, observable, recoverable error handling - an explicit taxonomy of retryable vs terminal failures, Result types at boundaries, single-point logging, and retry policies with real backoff numbers. Use when someone asks "should I retry this error", "how do I structure error types", "why are my logs full of duplicate stack traces", "where do I put the try/catch", or is designing failure paths for an API, job, or client. Do NOT use for building the circuit breaker component itself - use circuit-breaker-builder instead; do NOT use for handling 429s against third-party APIs - use rate-limit-handler instead; do NOT use for writing user-facing error copy - use error-message-writer instead.

    The same file is in 1 other repository

  • Llm evaluation

    SkillMedev/ai-engineer-toolkit/skills/llm-evaluation Skill

    0★ repo

    Builds evaluation harnesses for LLM products - golden datasets, deterministic checks, calibrated LLM-as-judge rubrics, and CI regression gates that turn "seems good" into a tracked number. Use when someone asks "how do I know this prompt change didn't break anything", "set up evals for my RAG pipeline", "is LLM-as-judge reliable", "why did quality drop after the model swap", or is shipping an LLM feature with no quality measurement. Do NOT use for classical ML model reporting (precision/recall, ROC curves, confusion matrices on trained classifiers) - use model-evaluation-report instead; do NOT use for analyzing online A/B experiments - use ab-test-analyzer instead.

    The same file is in 1 other repository

  • Landing page cro

    SkillMedev/performance-marketing/skills/landing-page-cro Skill

    0★ repo

    Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.

    The same file is in 2 other repositories

  • Write

    Lemonaderrrrr/flow-kit/skills/write Skill

    0★ repo

    Turn ideas into deliverable writing, split into two tracks — 📚 Academic (adds a mandatory evidence-gathering step; every claim gets a traceable source) and ✍️ Regular (emails, posts, docs, narrative). Each track runs in 🧠 Philosopher (default) or ⚙️ Engineer mode. Saves drafts to outputs/drafts/. Use when the user says "help me write/draft X", "write a paper", "write an email", or invokes the skill.

  • Manuscript prose immersion audit

    dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-prose-immersion-audit Skill

    0★ repo

    Line-level prose and scene-immersion auditor for any narrative manuscript — the deep craft pass beneath the publisher's read. Diagnoses scenes for the failures that keep prose at draft level: information dialogue, talking-heads, filter words, furniture-inventory description, missing micro-reactions, weak environmental presence, and emotion stated instead of threaded. Use when the author says "line audit", "prose immersion audit", "prose pass", "diagnose this scene", "is this immersive", "does this read like a draft", "craft pass", or "kill the info-dumping". It diagnoses at the line level — it does NOT rewrite prose, grade marketability, check canon, or judge mystery logic. For rewritten prose, route to the author's writing/voice skill.

    The same file is in 1 other repository

  • Manuscript publisher critique

    dinaf2026-web/manuscript-editorial-suite-plugin/skills/manuscript-publisher-critique Skill

    0★ repo

    The publisher's read for any manuscript — an acquisitions verdict plus a developmental craft breakdown, delivered as a scored report card graded against the markers of a great book in its genre (set by the project profile). Use for a single craft/acquisitions read of a scene, chapter, outline, full manuscript, or query: "publisher's read", "acquisitions verdict", "critique this", "score this", "grade this", "editor's letter", "would a publisher take this", "what's weak here", "read this like an editor". For a broad "review my book / full editorial pass" that may need several checks, use manuscript-editorial-router. NOT for canon checking (continuity-audit), mystery-fairness logic (fair-play-audit), line-level immersion (prose-immersion-audit), or blurb/listing copy (listing-critique). Diagnoses and scores; does not rewrite prose.

    The same file is in 1 other repository

  • Figmahandoff

    saurabhshuklagrowisto/saurabh-ai-systems/claude-skills/figmahandoff Skill

    0★ repo

    Use this skill EVERY TIME a Figma URL is mentioned or pasted in any message. Triggers on any figma.com link, any mention of "figma", or any request to implement/build/code a design. Before writing any code or reading any design, this skill intercepts the request and asks two required questions: (1) which tech stack — React or Shopify Liquid, and (2) whether to show the Figma design system first or proceed directly. Do NOT skip these questions. Do NOT write any code before both are answered. This is mandatory for all Figma-related implementation tasks at Acme.

  • Feedback writer

    SkillMedev/remote-team-toolkit/skills/feedback-writer Skill

    0★ repo

    Drafts specific, observable, kind workplace feedback using the SBI model - Situation, Behavior, Impact - for both praise and correction. Use when someone asks "help me give feedback to a teammate", "how do I tell my report they keep missing deadlines", "make this feedback less vague", or wants to reinforce a good behavior specifically. Do NOT use for formal performance review documents - use performance-review-writer instead; for feedback on student work, use student-feedback-writer; for mediating an active interpersonal dispute, use conflict-resolution.

    The same file is in 3 other repositories

  • Stakeholder update

    SkillMedev/remote-team-toolkit/skills/stakeholder-update Skill

    0★ repo

    Writes project stakeholder updates readable in under 60 seconds - honest RAG status, decisions made, explicit asks with owners and dates, next milestones - tiered to the audience. Use when someone asks "write my weekly project update", "how do I tell stakeholders we're at risk", "draft a status email for leadership", or "my updates get ignored, fix the format". Do NOT use for aggregating many teams' statuses into one engineering-wide report - use eng-status-rollup instead. For monthly investor letters with metrics and asks to VCs, use investor-update-writer; for customer-facing incident status, use status-page-update.

    The same file is in 1 other repository

  • Model card writer

    SkillMedev/data-science-ml/skills/model-card-writer Skill

    0★ repo

    Produces a complete model card - intended use, training data provenance, evaluation results with slices, limitations, and usage guidance - for any model shared beyond its team or affecting people. Use when someone asks "write a model card", "document this model before release", "what should our model documentation include", or is preparing a model for deployment, handoff, or external publication. Do NOT use for producing the underlying evaluation numbers - use model-evaluation-report instead; for ongoing production monitoring plans use data-drift-monitor.

    The same file is in 1 other repository

  • Model evaluation report

    SkillMedev/data-science-ml/skills/model-evaluation-report Skill

    0★ repo

    Produces a rigorous, honest evaluation report for an ML model - real baselines, business-matched metrics with confidence intervals, slice-level error analysis, calibration checks, and a go/no-go recommendation. Use when someone asks "is this model good enough to ship", "write up the eval for this model", "did we actually beat the old model", or before any model promotion, stakeholder demo, or retraining decision. Do NOT use for evaluating LLM or prompt outputs - use llm-evaluation instead; for analyzing randomized product experiments use ab-test-analyzer; for documenting a shipped model for consumers use model-card-writer.

    The same file is in 1 other repository

  • Expense policy

    SkillMedev/finance-accounting-ops/skills/expense-policy Skill

    0★ repo

    Drafts a clear, enforceable expense and approval policy - per-category spend limits, a dollar-tiered approval matrix, receipt and documentation rules, 30/90-day submission deadlines, and audit sampling. Use when someone says "write our expense policy", "who should approve what spend", "set reimbursement rules", or is onboarding a finance system or preparing for a compliance review. Do NOT use for building a departmental or personal budget - use budget-builder instead; do NOT use for the monthly close checklist - use month-end-close instead; do NOT use for general internal SOPs outside spend - use process-doc instead.

    The same file is in 1 other repository

  • Legal plain

    Frog1205/OPC-Skills/skills/legal-plain Skill

    0★ repo

    Translates every clause of a contract from legalese into clear, plain English with flags for deliberately confusing or misleading language

  • Legal report pdf

    Frog1205/OPC-Skills/skills/legal-report-pdf Skill

    0★ repo

    OPC-Skills — AI 一人公司(One-Person Company)Claude Code 技能合集。一个人 + AI = 一支团队。战略/法务/内容/文档等虚拟部门,18 个开箱即用的 AI 技能。

  • Changelog

    usrrname/agent-skills/skills/changelog Skill

    no license0★ repo

    Generates a changelog by analyzing git history and tags. Use when the user asks to generate, write, or update a changelog.

  • Rfp response writer

    SkillMedev/outbound-sales-engine/skills/rfp-response-writer Skill

    0★ repo

    Answers RFPs and security questionnaires with discipline - a go/no-go score before any writing (win probability times deal size against effort, under 30 percent win chance means decline), a compliance matrix mapping every requirement to a response, answer-library reuse, and win themes threaded through every section. Use when a user says "we got an RFP, help us respond", "should we even bid on this RFP", "build a compliance matrix for this RFP", "answer this security questionnaire", or "our RFP responses take weeks and we keep losing". Do NOT use for proactive proposals sent without a formal solicitation - use sales-proposal-writer instead.

    The same file is in 1 other repository

  • Sales proposal writer

    SkillMedev/outbound-sales-engine/skills/sales-proposal-writer Skill

    0★ repo

    Writes a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a proposal", "how should I present pricing in this proposal", or when a deal needs a document to move from discovery to close. Do NOT use for a one-page internal decision brief - use one-pager-designer instead; for investor decks use pitch-deck-builder; for setting the underlying price model use pricing-strategy.

    The same file is in 3 other repositories

  • Documentation

    muxammadmamajonov/dot-claude/.claude/skills/documentation Skill

    0★ repo

    Use when writing or updating specs, READMEs, API/reference docs, ADRs, or runbooks — record an ADR per decision, update docs when a feature ships, fix drifted docs.

  • Prototype spec

    SkillMedev/design-system-builder/skills/prototype-spec Skill

    0★ repo

    Turns a static design into a numbered, testable, dev-ready specification covering every state, interaction, breakpoint, motion detail, and edge case the mockup cannot show. Use when someone asks "write the spec for this screen", "engineering keeps asking what happens when", "document the interactions before handoff", "what states does this component need", or a build came back wrong because behavior was never written down. Do NOT use for the motion token details themselves - use motion-spec instead; for verifying a finished build against the spec, use design-qa-checklist.

    The same file is in 2 other repositories

  • Investor update writer

    SkillMedev/founder-fundraising-os/skills/investor-update-writer Skill

    0★ repo

    Drafts a monthly or quarterly investor update - TL;DR, consistent metric block (revenue, growth rate, burn, runway), highlights, honest lowlights, a specific ask, and next-period priorities - in a repeatable one-screen format. Use when someone asks "write my investor update", "what should go in my monthly update", "how do I tell investors about a bad month", or when a founder is due to report to their cap table. Do NOT use for updates to internal teams, executives, or non-investor stakeholders - use stakeholder-update instead. Do NOT use for crafting the fundraising story for new investors - use fundraising-narrative instead.

    The same file is in 2 other repositories

  • Vc pitch email

    SkillMedev/founder-fundraising-os/skills/vc-pitch-email Skill

    0★ repo

    Writes cold investor outreach under 100 words - a subject line built on the company's strongest verifiable metric, a personalized why-them opening line, traction before the ask, and a low-friction meeting request - delivered as three subject options, the email body with word count, and a follow-up line for five days later. Use when a founder asks "write a cold email to this VC", "how do I get an investor meeting", "pitch my seed round over email", or is starting investor outreach. Do NOT use for choosing which investors to contact - use investor-targeting instead - or for post-investment monthly updates - use investor-update-writer instead - or for non-investor sales outreach - use cold-email-craft instead.

    The same file is in 2 other repositories

  • Ordito delete page

    karuhi/ordito/.claude/skills/ordito-delete-page Skill

    0★ repo

    Delete a whole Ordito IR document (page) from the store. Use this when the user has agreed to remove an entire page from the docs. Deletes the IR file and, by default, also removes the page's entry from the collection nav (pruning now-empty groups). Already-generated out/<id>.html is NOT deleted (it just stops being regenerated) — the skill notes this. Does NOT regenerate HTML (ordito-generate is separate) and does NOT ask for confirmation itself; the calling agent owns that decision.

  • Ordito move block

    karuhi/ordito/.claude/skills/ordito-move-block Skill

    0★ repo

    Reorder or re-parent an existing block within an Ordito IR document (write to the IR store). Use this when the user wants to change the ORDER of content on a page, or move a block into/out of a tab — without changing the block's content. Moves exactly one existing block by id to a new position (at/after/before a sibling, or inside a tab), validates the result, and bumps meta.updated_at. Does NOT regenerate HTML (ordito-generate is separate) and does NOT ask for confirmation; the calling agent owns that.

  • Ordito remove block

    karuhi/ordito/.claude/skills/ordito-remove-block Skill

    0★ repo

    Delete one block from an existing Ordito IR document (write to the IR store). Use this when the user has agreed to remove a specific piece of content from a page — a now-obsolete note, paragraph, code sample, etc. Removes exactly one block by id (including blocks nested inside tabs), validates the remaining document, and bumps meta.updated_at. Does NOT regenerate HTML (ordito-generate is the separate step) and does NOT ask for confirmation itself; the calling agent owns that decision.

  • Ordito update block

    karuhi/ordito/.claude/skills/ordito-update-block Skill

    0★ repo

    Apply a block-level diff update to an Ordito IR document (write to the IR store). Use this AFTER the user has agreed that a specific piece of knowledge/content should be recorded into the docs — e.g. "記載しておきますか?" → yes. Updates exactly one block (by block id, including blocks nested inside tabs) and bumps meta.updated_at. It does NOT regenerate any HTML (generation is a separate, explicit step — see ordito-generate) and it does NOT ask for confirmation itself; the calling agent owns that decision. Idempotent: re-applying an identical patch is a no-op.

  • E2e scenario author

    SkillMedev/qa-test-automation/skills/e2e-scenario-author Skill

    0★ repo

    Converts an acceptance criterion or user story into one maintainable Playwright or Cypress end-to-end test that reads like the journey it covers. Use when turning a Given/When/Then acceptance criterion or user story into a browser test, when asked to "write an E2E test for this AC", or when a feature's critical journey (login, checkout, signup) needs a single automated scenario. Do NOT use when writing general Playwright tests, configuring the runner, or fixing existing test flakiness - use playwright-testing or flaky-test-detangler instead.

    The same file is in 1 other repository

  • Playwright testing

    SkillMedev/qa-test-automation/skills/playwright-testing Skill

    0★ repo

    Writes and reviews end-to-end Playwright tests that survive UI refactors and never fail on timing - resilient locators, web-first assertions, isolated state, and a flake policy with quarantine rules. Use when someone asks "write a Playwright test for this flow", "why is this e2e test flaky", "how do I wait for this element", "what selector should I use", or is setting up a Playwright suite and CI config. Do NOT use for consumer/provider contract tests of API boundaries - use contract-test-writer instead; for turning product requirements into an e2e scenario inventory before any code - use e2e-scenario-author instead; for systematically diagnosing an already-flaky suite - use flaky-test-detangler instead; for designing reusable test fixtures and factories - use test-data-builder instead.

    The same file is in 1 other repository

  • Tdd expert

    SkillMedev/qa-test-automation/skills/tdd-expert Skill

    0★ repo

    Drive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.

    The same file is in 3 other repositories

  • A12 dmtool bug report

    mbackschat/a12-dmtool-releases/skills/a12-dmtool-bug-report Skill

    0★ repo

    Produce a well-isolated bug-and-findings report for the dmtool CLI (a12-dmkits / A12 kernel) and save it to a folder the user picks. Use when a user hits an error, crash, internal error, or unexpected behaviour in dmtool, when they want to capture findings / DX friction / improvement notes, or when they ask to write or file a bug report against dmtool. Covers reading the result envelope (telling an internal tool error apart from a rejected input), shrinking to a minimal repro, an affected-vs-unaffected table, classifying genuine defects vs. your own input mistakes, a verbatim replay log, and a self-audit — then writing the report to a folder the user can upload or send however they like.

  • Escalation summary

    SkillMedev/customer-support-copilot/skills/escalation-summary Skill

    0★ repo

    Writes a tight escalation summary to engineering or management with a one-line headline, quantified customer impact, repro steps, prior attempts, and a single clear ask. Use when someone says "I need to escalate this ticket", "write this up for engineering", "this bug needs eng eyes", or a support issue must leave the queue for specialist action. Do NOT use for replying to the customer - use support-ticket-reply instead; do NOT use for assigning incident severity and coordinating an active outage - use sev-triage instead; do NOT use for the after-the-fact incident writeup - use postmortem-writer instead.

    The same file is in 1 other repository

  • Kb article writer

    SkillMedev/customer-support-copilot/skills/kb-article-writer Skill

    0★ repo

    Turns a resolved support ticket into a clear, searchable knowledge-base or help center article. Use when someone asks "write a KB article from this resolved ticket", "turn these resolved tickets into help center articles", or "write an internal knowledge base article for our support agents" - converting ticket resolutions into self-service documentation that deflects future tickets. Do NOT use for writing user-facing how-to guides from scratch - use help-documentation instead.

    The same file is in 1 other repository

  • Eval writer

    cody-hutson/pmo-platform/core/skills/eval-writer Skill

    no license0★ repo

    Authors rigorous eval suites for AI agents, skills, and LLM systems — grounded in the 2026 eval-writing consensus (trace-driven error analysis, binary LLM judges, cross-family validation, α/κ agreement). Produces characterization, failure taxonomies, judge prompts, rubrics, and calibration protocols that harnesses (pmo-skill-refiner, CI) then execute. Two modes — Author (write from scratch) and Review (audit against the framework). First-class playbooks for per-skill evals and for pipeline stage-gate judgment content; generic fallback for arbitrary AI systems. Use whenever the user asks to write evals, audit evals, add eval coverage, calibrate a judge, build a rubric, write a judge prompt, or diagnose why a judge keeps passing broken outputs.

  • Prompt builder

    cody-hutson/pmo-platform/core/skills/prompt-builder Skill

    no license0★ repo

    Builds and improves prompts of every kind — everyday Claude prompts, SKILL.md instruction bodies, skill descriptions, and agent/system prompts. Detects mode from input: critique-and-rewrite when the user pastes a draft, interview-and-build when the user describes a goal without a draft. Always does live web research on current Anthropic prompting guidance before producing output. Returns a short critique plus a copy/paste-ready prompt block. Use whenever the user asks for help writing, improving, rewriting, critiquing, sharpening, or scoping a prompt — including phrases like "help me write a prompt for…", "improve this prompt", "make this better", "what's wrong with this prompt", "rewrite this", "I need a system prompt for…", "draft a SKILL.md description for…", "write a prompt for", "sharpen this prompt", or whenever the user shares a block of text that is clearly an LLM prompt and asks for any kind of feedback or revision.

  • Skill compliance auditor

    cody-hutson/pmo-platform/core/skills/skill-compliance-auditor Skill

    no license0★ repo

    Measures skill trigger-compliance — whether the RIGHT skill actually fires for the requests it should serve — across the pmo-platform skill catalog, closing the coverage gap upstream of output-quality and structural audits. It runs template-seeded scenarios at three strictness levels (explicit / neutral / competing), classifies each tool-call trace deterministic-first, and reports a per-strictness compliance rate. Single Measure mode, plus a read-only re-render variant. A mandatory cost governor makes every run operator-gated, scenario-capped, and --dry-run-first. Distinct from eval-writer (which authors eval suites), pmo-qa-auditor (which grades output quality), and gate-evaluation-spec (which measures gate-decision judgment). Triggers: "measure skill trigger-rate", "audit skill compliance", "does the right skill fire", "is this skill's description drifting", "run the trigger-compliance pass", "check skill firing rate", "skill compliance report".

  • Comms writer

    cody-hutson/pmo-platform/operations/skills/comms-writer Skill

    no license0★ repo

    The voice of the PMO — produces audience-calibrated, ready-to-send communications. Covers email, Teams, Confluence, exec briefs, meeting agendas, escalation drafts, recaps, and status updates. Use when drafting any stakeholder communication. Triggers: "draft an update for [audience]", "write the exec brief", "prepare the agenda", "send the escalation email", "write the recap", "put together a message", "write a Teams post."

  • Pmo business analyst

    cody-hutson/pmo-platform/operations/skills/pmo-business-analyst Skill

    no license0★ repo

    Business Analyst Specialist — owns the HOW-it-works of delivery: requirements elicitation, process/workflow documentation, traceability, and gap analysis. Operates at the requirements tier: eliciting what the business needs, documenting how work flows, and proving the requirement traces from source to evidence. Composes pmo-process-designer (requirements definition, INVEST, Given-When-Then, process docs, traceability, gap analysis) + delivery-engine (backlog substrate, DoR readiness) — invokes them, never re-implements them. Modes: Requirements Elicitation · Workflow & Process Documentation · Traceability & Coverage · Gap Analysis. Use when the question is what the business needs elicited, how a process is documented, whether a requirement traces end-to-end, or where the coverage gap is. Triggers: "elicit the requirements", "document this process/workflow", "build the traceability matrix", "trace this requirement to Jira", "what's the gap", "map the as-is/to-be", "is this requirement complete".

  • Pmo process designer

    cody-hutson/pmo-platform/operations/skills/pmo-process-designer Skill

    no license0★ repo

    Converts business context into structured, traceable requirements and process documentation. Modes: Requirements definition · Workflow documentation · Gap analysis · Traceability matrix · Compliance mapping. Use when uploading business requirements, FDDs, or Jira exports. Triggers: "document this process", "build the requirements", "build the traceability matrix", "write the FRD", "trace from requirement to Jira", "what's the gap."

  • Obsidian documentation

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-documentation Skill

    0★ repo

    Orchestrator and ONLY entrypoint for all Obsidian documentation work. Use this skill whenever the user wants to document anything in their Obsidian vault — features, architecture, decisions (ADRs), diagrams, tags, links/MOCs, or vault cleanup — or says things like "document this", "write this up in Obsidian", "add this to the vault", "create an ADR", "update the docs". Even if the request seems to match a specialist skill directly, route through this skill. It analyzes intent, gathers context (git diff, repo, vault, conversation), delegates to specialist skills, and assembles one coherent documentation package.

  • Obsidian feature

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-feature Skill

    0★ repo

    Specialist skill for documenting features (backend + frontend) in an Obsidian vault. Normally invoked by the obsidian-documentation orchestrator, but also use it directly when the user asks to document a feature, a new capability, an endpoint, a UI flow, or "what I just built" — including from a git diff or PR. Produces feature notes under Features/ with backend/frontend sub-notes, ready for the tagging and linking pass.

  • Obsidian maintenance

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-maintenance Skill

    0★ repo

    Specialist skill for keeping an Obsidian vault healthy over time — deduplicating overlapping notes, merging, refactoring outdated documentation, fixing structural mess, and updating docs after code changes. Normally invoked by the obsidian-documentation orchestrator. Use for "clean up the vault", "these notes overlap", "the docs are outdated", "refactor the documentation", or when any skill notices duplication or rot.

  • Obsidian query

    rubber-ducks-syndicate/obsidian-documentation-skill/skills/obsidian-query Skill

    0★ repo

    Specialist skill for answering questions FROM the Obsidian vault — "how does X work", "why did we choose Y", "what do we know about Z", "find the docs about…". It owns the hidden per-project index (a catalog of every note with one-line summaries, in <vault>/.claude-docs/) and run log, reads the index first to locate relevant notes, then synthesizes a cited answer. Valuable answers can be filed back into the vault. Use whenever the user asks a question whose answer should live in the documentation, or asks to find/locate notes.