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

  • Capture screens

    mostafa-drz/claude-skills/code/capture-screens Skill

    2★ repo

    Automatically navigates a web app using Playwright MCP and captures context-aware named screenshots at each product feature state. Names each file semantically based on context (e.g., checkout-payment-form-filled.png). Outputs a manifest.json mapping filenames to descriptions and a summary report. Use when documenting product features, generating demo screenshots, building user guides, or creating visual test assets for any web application. Composable primitive — other skills (user-guide, demo-docs) consume its manifest.json output.

  • Clean copy

    mostafa-drz/claude-skills/code/clean-copy Skill

    2★ repo

    Cleans terminal-formatted text and copies it to the macOS clipboard via pbcopy, formatted for the target platform (Gmail, Slack, LinkedIn, plain, markdown). Strips uniform leading indentation, trailing whitespace, and soft-wrapped paragraphs that come from copying out of a terminal, then applies platform conventions (Slack `*bold*` vs Gmail plain prose, etc.). Use when the user wants to paste a draft from the chat into Gmail, Slack, LinkedIn, or any other tool without nightmare terminal formatting (extra whitespace, hard wraps, indented blocks) coming along.

  • Compliance audit

    mostafa-drz/claude-skills/code/compliance-audit Skill

    2★ repo

    Audits codebases against compliance frameworks (SOC2, HIPAA, PCI-DSS, GDPR, ISO27001, etc.) using parallel agents per subdirectory/sub-repo. Produces a detailed markdown report with line-level code references. Use when you need to check a directory or monorepo for compliance violations before an audit or review.

  • Docs doctor

    mostafa-drz/claude-skills/code/docs-doctor Skill

    2★ repo

    Audits a repository's documentation for unused docs, wrong details, missing coverage, inaccurate data, broken structure, and writing best-practices. Generates a markdown report (HTML optional) with severity ratings. Supports modes (main, comprehensive, focused, quick), per-profile templates (open-source, internal-docs, blog, nextjs-app), optional --fix for low-risk auto-fixes (broken links, frontmatter, stale dates), and a /feedback subcommand that promotes recurring signals into Learned defaults. Use when you want a "docs doctor" pass on a repo before a release, after a refactor, or as a recurring DX health check.

  • Emotional recap

    mostafa-drz/claude-skills/code/emotional-recap Skill

    2★ repo

    Reviews the user's past Claude Code conversations from a wellbeing perspective — sentiment, tone, emotional arc, recurring patterns — and generates a supportive, science-grounded report in both Markdown and HTML. Default lookback is 48 hours across all projects. Uses recognised emotion frameworks (Plutchik, Ekman, Russell's circumplex, Pennebaker linguistic markers) and cites the science behind every observation. Learns the user's baseline tone over time so future reports flag genuine shifts, not noise. Use when the user asks for an emotional/wellbeing recap, mood check, sentiment review, or wants to understand their own ups and downs across recent work sessions.

  • Release notes

    mostafa-drz/claude-skills/code/release-notes Skill

    2★ repo

    Generates brief, truth-based release notes for a release PR (typically main → prod) by listing each squash-merged PR, a one-paragraph summary drawn from each PR body, and the linked issue-tracker tickets (Linear, Jira, GitHub Issues, Asana, ClickUp, Shortcut, Plane, etc. — any tracker, configured via a URL template). Use when opening or updating a release PR.

  • Triage board

    mostafa-drz/claude-skills/code/triage-board Skill

    2★ repo

    Generates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown" action that produces a GitHub/Linear/Notion-ready ticket block. Stateless — triage state lives in the user's ticket system, not in the viewer. Use after a beginner-mind audit, QA exploration, code review, or any session where the user accumulated discrete findings worth handing off. Triggers: "generate test report", "create triage doc", "extract findings", "export this audit", "make a viewer", "save findings for review".

  • Fizzy write

    Rijul1204/rashedul-agentic-engineering/skills/fizzy-write Skill

    2★ repo

    Create cards, create boards, update cards, close/reopen cards, add comments, assign users, or move cards to a column in Fizzy. Use when user says "create card", "create board", "add task to fizzy", "close fizzy card", "comment on fizzy card", "assign fizzy card", "move card to column", or anything involving writing to the Fizzy task board.

  • Handoff

    Rijul1204/rashedul-agentic-engineering/skills/handoff Skill

    2★ repo

    Compact the current conversation into a structured handoff document (saved to the OS temp directory) so a fresh agent can continue the work without losing context. Use when the user invokes /handoff, says "create a handoff doc", "write a handoff document", "compact this for another agent", "pass off to another session", "what will the next session focus on", or generally wants to checkpoint the conversation state before a context-window break. Always references existing artifacts (design docs, plans, PRs, commits, memory entries) by path/URL — never duplicates their content. Includes a mandatory "suggested skills" section. Redacts API keys, passwords, PII.

  • Srs documentation

    Rijul1204/rashedul-agentic-engineering/skills/srs-documentation Skill

    2★ repo

    Software Requirements Specification documentation following IEEE 830 standard. Use when generating formal SRS documents or compiling gathered requirements into structured documentation.

    The same file is in 3 other repositories

  • Tri agent loop

    Rijul1204/rashedul-agentic-engineering/skills/tri-agent-loop Skill

    2★ repo

    Orchestrate a plan → review → implement delivery loop across three PLUGGABLE agent roles — planner, reviewer, implementer — where any agent can fill any role in any order. One agent drafts an artifact (SRS / design / per-task plan), a second adversarially reviews it through a shared markdown thread until convergence (Final ACK), and a third implements; the orchestrator (the agent running this skill) relays handoffs, monitors the review thread, and reviews the resulting PR. Use when the user asks to "run the planner / reviewer / implementer loop", "tri-agent loop", "plan-review-implement", "use X to plan, Y to review, Z to implement" (any permutation, e.g. Claude plans, Codex reviews, Cursor implements), or wants the docs-first / Codex-reviewed / Cursor-implemented workflow from feedback_planner_reviewer_codex_loop generalized to arbitrary agents.

  • Writing great skills

    d0hx4n2503/Agent-Skills/skills /productivity/writing-great-skills Skill

    2★ repo

    Collection of useful skills, prompts, tools and best practices for engineers when building and working with AI Agents

    The same file is in 6 other repositories

  • Writing skills

    slowdini/slow-powers/skills/writing-skills Skill

    2★ repo

    Use when creating new skills or editing existing skills. Drafting only; see slow-powers:evaluating-skills for measuring whether the draft works.

  • Api to openapi

    wunamesst/skills/skills/api-to-openapi Skill

    2★ repo

    将自然语言接口描述、接口文档、参数表格或支持的后端代码转换为标准 OpenAPI 3.0.3 JSON, 并在需要时生成 Postman Collection 等平台兼容产物,供 Postman / Apifox / ApiPost 导入后形成可调试接口。 Use when the user asks to generate, export, convert, or validate Swagger/OpenAPI/importable API documentation from existing API descriptions, docs, tables, or code. Do not use merely to implement, call, debug, or review API code. Directly writing/importing into external platforms is outside this skill and belongs to a separate MCP such as api-publish.

  • Sync rules

    wunamesst/skills/skills/sync-rules Skill

    2★ repo

    Iteration closeout knowledge routing for AI-assisted development. Use when the user asks to summarize changed function points into a knowledge base, update project docs or generated superpower docs after code changes, sync rules, distill lessons from an iteration, record durable decisions, or remember user preferences. Routes distilled knowledge to personal notes (K1), project docs (K2), agent memory suggestions (K3), or project instructions such as AGENTS.md and CLAUDE.md (K4), with preview and safety checks before writing.

  • Plan and verify

    zhengbingquant/frontier-skills/skills/plan-and-verify Skill

    2★ repo

    Disciplined-execution playbook for non-trivial engineering work. Consult BEFORE writing code whenever a task touches more than one file, an unfamiliar codebase, a bug whose cause is not yet proven by evidence, a refactor, a migration, or any state-changing operation — not only when the user asks for a plan. Applies even when the request sounds quick or trivial ('just', 'simple', 'quick fix'). Rule of thumb: if you cannot already name the exact command that will prove the change works, read this skill first. Covers ground-truthing the environment, scoping, planning, implementation discipline, evidence-first debugging, end-to-end verification, and faithful reporting.

  • Obsidian markdown

    arch3rPro/ark-space/plugins/ark-space/skills/obsidian-markdown Skill

    2★ repo

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

  • Defuddle

    arch3rPro/ark-space/skills/defuddle Skill

    2★ repo

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.

  • Obsidian markdown

    arch3rPro/ark-space/skills/obsidian-markdown Skill

    2★ repo

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

  • Press release writer

    hssh8917/cc-skills/skills/press-release-writer Skill

    2★ repo

    Write professional press releases for any occasion, media type, and country. Use when the user wants to write, draft, or improve a press release, communiqué de presse, media announcement, news release, or PR statement — including product launches, funding rounds, partnerships, crisis communications, earnings, executive hires, events, M&A, open source milestones, and media advisories. Covers all release types, media targets (print, digital/wire, broadcast, social/SMPR, trade press), and region-specific conventions (Western/Eastern Europe, Americas, Middle East, Africa, Asia, Oceania). Also trigger when the user says 'I need to announce something' or 'how do I tell the press about X.'

    The same file is in 1 other repository

  • Substack ghostwriting

    hssh8917/cc-skills/skills/substack-ghostwriting Skill

    2★ repo

    Write, optimize, and grow Substack content — both newsletter issues (email-first) and web posts (web-first articles/essays). Covers ghostwriting with voice matching, Substack algorithm optimization, Notes strategy, email formatting, SEO, growth tactics, and monetization planning. Use when the user mentions Substack, newsletters, write a newsletter issue, Substack post, Substack article, web post on Substack, evergreen content, SEO for Substack, newsletter growth, Notes strategy, ghostwrite for, match someone's voice, write in the style of, newsletter monetization, paid subscribers, or any task involving Substack as a platform. Also trigger for general article/newsletter writing even if Substack isn't named explicitly, or when the user wants to adapt existing content (blog post, talk, thread) into newsletter or web post format. Do NOT use for generic blog post writing without a newsletter/Substack context (-> See samber/cc-skills@technical-article-writer skill).

  • Technical article writer

    hssh8917/cc-skills/skills/technical-article-writer Skill

    2★ repo

    Write compelling technical articles and blog posts for developer audiences. Use this skill whenever the user asks to write a blog post, technical article, or any long-form technical content. Also trigger when the user says 'write about [technical topic]', 'help me draft an article', 'turn this into a blog post', 'write a post about', 'I want to publish something about', or mentions writing for a developer audience. Covers the full pipeline: idea sharpening, hook/title generation, article structure, body drafting, and editing. Even if the user just says 'I want to write about X' without specifying format, use this skill. Do NOT use for platform-specific optimization, newsletter strategy, or ghostwriting voice matching.

  • Training report

    hssh8917/cc-skills/skills/training-report Skill

    2★ repo

    Produce a professional training/workshop report as a .docx file. Use this skill whenever the user mentions "training report", "workshop report", "compte rendu", "compte rendu de formation", "formation report", "debriefing a workshop", "write up a training session", "résumé de formation", or any request to document a training session, workshop, or onboarding event with individual participant feedback and recommendations. Also trigger when the user says things like "I just ran a workshop and need to write it up", "help me summarize what happened in my training session", or "I need to report back to management about a session I ran". Always use this skill — for short or long sessions, across any discipline (technical, soft skills, creative, compliance, onboarding, etc.) — whenever a structured written deliverable about a training event is needed.

  • Writing meaningful tests

    yuchi-chang/no-cape/skills/writing-meaningful-tests Skill

    no license2★ repo

    Use when writing or modifying tests, adding mocks, or tempted to add test-only methods to production code

  • Writing solid plans

    yuchi-chang/no-cape/skills/writing-solid-plans Skill

    no license2★ repo

    Use when designing or planning a multi-step feature, refactor, or spec before implementation begins

  • Handoff

    stuartshields/claude-setup/skills/handoff Skill

    2★ repo

    Write or update a handoff document so the next agent with fresh context can continue this work.

  • Daily standup prep

    risadams/skills/daily-standup-prep Skill

    no license2★ repo

    Generate a per-team standup markdown report by gathering activity over the last N days from Jira, GitLab, Confluence, and a local Git repo. Maps activity to team members from a roster CSV, renders a Mermaid kanban + randomized talking order, captures a `daily`-tagged sprint snapshot, and runs a clarity-council (infographics-expert burndown chart + statistics-expert forecast + scrum-master suggestions) for sprint pulse. Writes one file per team into the Obsidian vault. Use when the user says "daily standup prep", "standup report", "generate standup", "scrum prep", or invokes /daily-standup-prep.

  • Defuddle

    risadams/skills/defuddle Skill

    no license2★ repo

    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page. Do NOT use for URLs ending in .md — those are already markdown, use WebFetch directly.

  • Grill with docs

    risadams/skills/grill-with-docs Skill

    no license2★ repo

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

  • Idea choice

    risadams/skills/idea-choice Skill

    no license2★ repo

    Weigh one or more ideas/concepts with a structured pros-and-cons analysis. Runs a clarity-council pass to surface arguments on both sides, optionally grills the user to expose hidden assumptions, scores each point on Impact × Confidence, and renders a markdown table per idea plus an overall recommendation (Go / Go with caveats / Don't / Needs more analysis). Use when the user wants to evaluate an idea before committing, compare two or more options on the merits, build a pros/cons list, score tradeoffs, justify a decision in writing, or asks "should I do X" / "is X worth it" / "weigh the tradeoffs" / "pros and cons of X". Differs from idea-decision-maker (which forces a fast binary pick) and idea-generate (which generates new options) — this skill deliberates on options the user already has.

  • Issue draft release notes

    risadams/skills/issue-draft-release-notes Skill

    no license2★ repo

    Draft a customer-facing release note for a Jira ticket by gathering the ticket context (summary, description, type, fix version, comments) and any linked GitLab merge requests / code changes, then synthesizing a clear, audience- appropriate release note. Runs a clarity-council quality pass over the draft. Read-only by default; the user may opt in at the end to publish the note as a Jira comment (or into a Release Notes field if one exists). Use when user says "draft release notes", "write a release note", "release note for [TICKET-KEY]", "what changed in this ticket", or invokes /issue-draft-release-notes with a ticket key.

  • Issue dup find

    risadams/skills/issue-dup-find Skill

    no license2★ repo

    Scan all open issues in a Jira project and identify likely duplicates using semantic comparison. Produces a markdown report listing each suspected duplicate pair with a probability score and reasoning. Read-only — never modifies, links, or transitions tickets. Default project key is read from memory (`reference_jira_default_project.md`); accepts an override project key. Use when user says "find duplicates", "duplicate check", "dedupe issues", "find duplicate tickets", or invokes /issue-dup-find with or without a project key.

  • Obsidian markdown

    risadams/skills/obsidian-markdown Skill

    no license2★ repo

    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

  • Sprint plan

    risadams/skills/sprint-plan Skill

    no license2★ repo

    Convert the start-of-sprint canvas into a planning markdown report — sprint goal summary, committed scope, capacity vs commitment (split into carry-over from previous sprint vs new commit), key observations, and risks. Assumes all unclosed items from the previous sprint's end snapshot are carried into this sprint and surfaces them as a dedicated section with WIP-saturation risk. Reuses sprint-snapshot's `_sprint.md`, `_team-rules.md`, current `start.canvas`, and previous sprint's `end.canvas`. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner) for the observations/risks block. Output is date-stamped (`sprint-plan-YYYY-MM-DD.md`) — same-day re-runs silently refresh today's file, prior days are preserved as historical record; a `sprint-plan-latest.md` pointer always wikilinks the newest. Use when user says "sprint plan", "sprint planning report", "convert sprint plan to markdown", or invokes /sprint-plan.

  • Sprint review

    risadams/skills/sprint-review Skill

    no license2★ repo

    End-of-sprint stakeholder report comparing the start.canvas (planning) to end.canvas (sprint close). Produces a markdown report fitting the standard SM template (Scrum Master, Sprint Accomplishments, Feature Demos, Customer Meetings, Status, Sprint Commitment, PI Confidence, Impediments). Applies team-specific overhead, wedge-balancing, and in-review overhead rules. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner) for accomplishments/status/impediments synthesis. Use when user says "sprint review", "end of sprint report", "sprint stakeholder report", "sprint close report", or invokes /sprint-review.

  • Sprint sos report

    risadams/skills/sprint-sos-report Skill

    no license2★ repo

    End-of-week scrum-of-scrums report comparing two sprint snapshots and surfacing key findings, observations, trouble areas, and trends. Auto-detects which two snapshots to compare (most-recent two by snapshot_at) with `--from`/`--to` overrides for re-planning churn comparisons (e.g. compare `week 1` vs a mid-week `week 1.5`). Applies team-specific overhead, wedge-balancing, and in-review overhead rules from `_team-rules.md`. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner). Use when user says "scrum of scrums", "sos report", "weekly sprint report", "sprint progress report", or invokes /sprint-sos-report.

  • Writing apology calibrator

    risadams/skills/writing-apology-calibrator Skill

    no license2★ repo

    Drafted apology in, calibrated apology out. Strips reflexive self-blame and over-apologizing that masking trains in, while keeping genuine accountability for things the user actually owes. Use when user says "calibrate this apology", "am I over-apologizing", "apology check", "did I say sorry too much", "is this too much", or invokes /writing-apology-calibrator.

  • Writing beats

    risadams/skills/writing-beats Skill

    no license2★ repo

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

  • Writing cold open

    risadams/skills/writing-cold-open Skill

    no license2★ repo

    Generates the first sentence of a message or email when you can't get past the blank cursor. Offers 2-3 openings matched to the relationship and goal, then steps out — you write the rest. Use when user says "cold open", "help me start this message", "how do I begin", "stuck on opening", "first sentence", or invokes /writing-cold-open.

  • Writing draft article

    risadams/skills/writing-draft-article Skill

    no license2★ repo

    Guide the user from raw idea, topic, or draft to a finished, polished article through relentless questioning and iterative writing. Supports blog posts, social media posts, and long-form prose. Delegates to sibling skills (writing-humanize, writing-shape, writing-beats, writing-fragments) when appropriate. Use when the user wants to write something from scratch and have it completed.

  • Writing fragments

    risadams/skills/writing-fragments Skill

    no license2★ repo

    Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

  • Writing humanize

    risadams/skills/writing-humanize Skill

    no license2★ repo

    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.

  • Writing shape

    risadams/skills/writing-shape Skill

    no license2★ repo

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

  • Writing social script

    risadams/skills/writing-social-script Skill

    no license2★ repo

    Generate a script for a specific social scenario you're dreading: declining a meeting, asking for a deadline extension, following up on silence, leaving a party early, asking for help, setting a boundary. Offers 2-3 phrasings from direct to softened. Use when user says "script for", "help me say", "how do I tell them", "I need to ask", "I need to decline", "social script", or invokes /writing-social-script.

  • Writing tone check

    risadams/skills/writing-tone-check Skill

    no license2★ repo

    Reverse decoder — paste a draft message and get a read on how it will land before you send. Flags blunt, cold, accidentally passive-aggressive, or over-apologetic patterns. Use when user says "tone check", "how does this sound", "before I send this", "will this land okay", "check this draft", or invokes /writing-tone-check.

  • Daily

    KKenny0/Tracework/plugins/tracework/skills/daily Skill

    no license2★ repo

    Generate or update workplace-facing daily reports from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes without mixing audiences. Use for "/tracework:daily", "更新日报", "写日报", "日报", "工作日志", "补日报", "daily note", or a dated daily work report. Do not use for agent handoff, meeting notes, generic prose reports, or git operations.

  • Weekly

    KKenny0/Tracework/plugins/tracework/skills/weekly Skill

    no license2★ repo

    Generate a workplace-facing weekly report from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes. Three modes: quick conversation review ("这周做了啥", "周报简版", "quick weekly", "本周概要"), default Markdown brief ("写周报", "周报", "/tracework:weekly", "weekly brief", "本周总结", "weekly report"), and PPT-ready Markdown Deck only when weekly PPT is explicit ("weekly PPT", "周报 PPT", "weekly slides", "演示大纲"). Do not use for daily notes, generic slide decks, or single-commit analysis.

  • Daily

    KKenny0/Tracework/skills/daily Skill

    no license2★ repo

    Generate or update workplace-facing daily reports from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes without mixing audiences. Use for "/tracework:daily", "更新日报", "写日报", "日报", "工作日志", "补日报", "daily note", or a dated daily work report. Do not use for agent handoff, meeting notes, generic prose reports, or git operations.

  • Weekly

    KKenny0/Tracework/skills/weekly Skill

    no license2★ repo

    Generate a workplace-facing weekly report from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes. Three modes: quick conversation review ("这周做了啥", "周报简版", "quick weekly", "本周概要"), default Markdown brief ("写周报", "周报", "/tracework:weekly", "weekly brief", "本周总结", "weekly report"), and PPT-ready Markdown Deck only when weekly PPT is explicit ("weekly PPT", "周报 PPT", "weekly slides", "演示大纲"). Do not use for daily notes, generic slide decks, or single-commit analysis.

  • Product requirements builder

    mouchegmouradian/claude-code-skills/skills/product-requirements-builder Skill

    2★ repo

    Build comprehensive product requirements documents (PRDs) and technical RFC specifications for software projects. Guides the user through structured discovery — from problem statement and user personas to technical architecture, data models, and implementation RFCs. Use this skill whenever the user wants to plan a new product, define requirements for a feature, create technical specs, write an RFC, break down a project into implementable pieces, or prepare documentation for AI-assisted coding (Claude Code, Cursor, etc.). Also use when the user says things like "help me spec this out", "let's plan this project", "write a PRD", "create an RFC", "break this into tasks", or "I need to define requirements for...".

  • Nestjs documentation

    FilippoDeSilva/skills/skills/nestjs/nestjs-documentation Skill

    no license2★ repo

    Automate Swagger/OpenAPI documentation and standardize API response schemas in NestJS. Use when generating OpenAPI specs, documenting paginated or generic responses, configuring the Nest CLI Swagger plugin, or publishing versioned API docs.

  • Nestjs testing

    FilippoDeSilva/skills/skills/nestjs/nestjs-testing Skill

    no license2★ repo

    Write Unit and E2E tests with Jest, mocking strategies, and database isolation in NestJS. Use when writing NestJS unit tests, E2E tests with supertest, or mock providers.

  • Nextjs i18n

    FilippoDeSilva/skills/skills/nextjs/nextjs-i18n Skill

    no license2★ repo

    Best practices for multi-language handling, locale routing, and detection strategies across App and Pages Router. Use when adding i18n, locale routing, or language detection in Next.js.

  • Rust

    FilippoDeSilva/skills/skills/rust-expert/rust Skill

    no license2★ repo

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use when writing new Rust code, reviewing or refactoring existing code, deciding between borrowing vs cloning or ownership patterns, implementing error handling with Result types, optimizing Rust code for performance, or writing tests or documentation for Rust projects.

  • Dsc scrape

    j-256/claude-code-skills/skills/dsc-scrape Skill

    2★ repo

    Scrape developer.salesforce.com (DSC) API reference pages and write structured JSON. Invoke whenever the user asks to scrape, extract, fetch, mirror, capture, discover, or get the contents of any DSC reference URL (anything under `/docs/.../references/` or the top-level `/docs/apis` catalog) -- including "get me the Shopper Products endpoints", "pull the SCAPI reference", "pull an OCAPI reference", "what APIs exist on DSC", "list Commerce Cloud references", "what's under Agentforce", or "scrape this whole API family." Handles the top-level product catalog, product-area reference listings, individual references (OAS 3 YAML, RAML/AMF JSON, Swagger 2 / OCAPI, ReDoc), and single operations in one fetch-based architecture. Not for guides, concept pages, atlas-format books, or release notes -- decline.

  • Stepped demo script

    j-256/claude-code-skills/skills/stepped-demo-script Skill

    2★ repo

    Author a self-contained bash script that walks a human through a multi-step demo – pausing between steps so they can read output before proceeding, and asserting expected vs. actual so pass/fail is visible at a glance. Use whenever the user wants a runnable repro, walkthrough, or demonstration with discrete steps: reproducing a bug on a sandbox, showing off correct behavior of an API, narrating a CLI flow, making a script an engineer or a stakeholder can paste into a terminal and run top-to-bottom. Phrases that should trigger: "repro script", "demo script", "case script", "walkthrough", "step-through", "show me the steps", "script I can run to demonstrate", "paste-and-run", "script I can share", "script they can run themselves", "reproduction for the team", "whip one up". This skill owns the *authoring* step even when the subject is a specific product/API (SCAPI, cQuotient/Einstein, GitHub, kubectl, git) – if the output is "a script" and the verb is "write/make/draft/build/generate", this is the right skill. For Salesforce-specific scenario *planning* without writing a script (e.g. "what do I need to call before createOrder", "prereqs for addItemToBasket"), use `dsc-scenario` instead. Not for: non-interactive pipelines (CI, one-shot batch jobs) – those shouldn't pause for human input. Not for: generating the domain-specific payloads themselves (API bodies, SQL, etc.) – that's the user's content; this skill authors the scaffolding around it.

  • Session handoff

    AdityaVasireddy/agent-skills/session-handoff Skill

    2★ repo

    Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or wants a structured end-of-session summary before clearing context. Also use proactively when the user says they are about to /clear and no handoff has been produced yet. Generates a handoff document saved as a file (in the project's docs/handoffs/ directory, or as a downloadable file in chat environments) with required sections (objective, status, decisions + rationale, key files, next action) plus situational sections included only when they apply, so a fresh agent can continue seamlessly without re-deriving lost context.

  • Nexus content multilingual

    Shuwanito/SkillsMP/.claude/skills/nexus-content-multilingual Skill

    no license2★ repo

    Multilingual and cultural bridge specialist for educational content. Use when you need educational translations, bilingual materials, or culturally-adapted content. Ensures translations preserve educational intent and cultural sensitivity rather than being literal word-for-word conversions.

  • Docx

    siddharthrath1999/Claude-Opus-4.7/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

  • Xlsx

    siddharthrath1999/Claude-Opus-4.7/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