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

  • Elevenlabs dubbing

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main/skills-main/tools/audio/elevenlabs-dubbing Skill

    no license2★ repo

    ElevenLabs automatic dubbing - translate and dub audio/video into 29 languages while preserving speaker voice via inference.sh CLI. Capabilities: auto speaker detection, voice-preserving translation, video dubbing, audio localization. Use for: content localization, video translation, multilingual content, international distribution. Triggers: dubbing, dub video, translate audio, video translation, audio translation, localize content, elevenlabs dubbing, eleven labs dub, multilingual dub, voice translation, auto dub, language dub, content localization

  • Neversight skills feed writing best practices 1.0.1

    VRIL-LABS/skill-jam/skills/best-practices/neversight-skills_feed-writing-best-practices-1.0.1 Skill

    no license2★ repo

    Use when creating structured best practices guides, organizing technical documentation, or establishing reference materials for teams or agents

  • Api doc generator

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/api-integration/api-doc-generator Skill

    no license2★ repo

    Generate API documentation — Swagger, ReDoc, or API docs from code. Use when documenting APIs, creating developer portals, or generating specs.

  • Changelog generator

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/communication/changelog-generator Skill

    no license2★ repo

    Generate changelogs from commits — semantic versioning and release notes. Use when creating releases, documenting changes, or maintaining changelogs.

  • Release notes writer

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/communication/release-notes-writer Skill

    no license2★ repo

    Write release notes — feature summaries and change documentation. Use when documenting releases, communicating changes, or creating announcements.

  • Agent readiness

    VRIL-LABS/skill-jam/skills/core-collections/spellbook-master/spellbook-master/skills/agent-readiness Skill

    no license2★ repo

    Assess and improve codebase readiness for AI coding agents. Dispatches parallel subagents to evaluate style, testing, docs, architecture, CI, observability, security, and dev environment. Produces a scored report with prioritized remediation. Then executes the highest-impact fixes. Use when: "agent readiness", "is this codebase agent-ready", "readiness report", "make this codebase agent-friendly", "agent-ready assessment", "readiness audit", "prepare for agents". Trigger: /agent-readiness, /readiness.

  • Inline chat inline write changelog 1.0.2

    VRIL-LABS/skill-jam/skills/dev-tools/inline-chat-inline-write-changelog-1.0.2 Skill

    no license2★ repo

    Reads commits and changed files within a timeframe specified by user and compiles a changelog for both iOS and macOS.

  • Anthropics skills docx 1.0.2

    VRIL-LABS/skill-jam/skills/document-processing/anthropics-skills-docx-1.0.2 Skill

    no license2★ 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

  • Anthropics skills xlsx 1.0.2

    VRIL-LABS/skill-jam/skills/document-processing/anthropics-skills-xlsx-1.0.2 Skill

    no license2★ 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

  • Minimax ai skills minimax docx 1.0.1

    VRIL-LABS/skill-jam/skills/document-processing/minimax-ai-skills-minimax-docx-1.0.1 Skill

    no license2★ repo

    Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.

    The same file is in 7 other repositories

  • Minimax ai skills minimax pdf 1.0.1

    VRIL-LABS/skill-jam/skills/document-processing/minimax-ai-skills-minimax-pdf-1.0.1 Skill

    no license2★ repo

    Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): "make a PDF", "generate a report", "write a proposal", "create a resume", "beautiful PDF", "professional document", "cover page", "polished PDF", "client-ready document". FILL (complete form fields): "fill in the form", "fill out this PDF", "complete the form fields", "write values into PDF", "what fields does this PDF have". REFORMAT (apply design to an existing doc): "reformat this document", "apply our style", "convert this Markdown/text to PDF", "make this doc look good", "re-style this PDF". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.

    The same file is in 6 other repositories

  • Tobi qmd qmd 1.0.2

    VRIL-LABS/skill-jam/skills/document-processing/tobi-qmd-qmd-1.0.2 Skill

    no license2★ repo

    Search markdown knowledge bases, notes, and documentation using QMD. Use when users ask to search notes, find documents, or look up information.

  • Documentation writer

    VRIL-LABS/skill-jam/skills/documentation-writer Skill

    no license2★ repo

    Generates inline docstrings, README sections, and API reference docs from source code and function signatures. Invoke when asked to document code, write a README, add docstrings, create API docs, or explain what a function or module does.

  • Legal document reviewer

    VRIL-LABS/skill-jam/skills/legal-document-reviewer Skill

    no license2★ repo

    Scans contracts and legal documents for risky clauses, non-standard terms, missing provisions, and regulatory compliance issues. Invoke when asked to review a contract, analyze legal terms, flag risky clauses, check for missing provisions, or summarize legal documents in plain language.

  • Openapi generator

    VRIL-LABS/skill-jam/skills/openapi-generator Skill

    no license2★ repo

    Generates OpenAPI 3.x specifications from annotated code, existing routes, or natural-language descriptions, and vice versa. Invoke when asked to generate an OpenAPI spec, create API documentation, scaffold code from a spec, convert route definitions to OpenAPI, or produce a Swagger file.

  • Exa labs exa mcp server code search 1.0.3

    VRIL-LABS/skill-jam/skills/search-research/exa-labs-exa-mcp-server-code-search-1.0.3 Skill

    no license2★ repo

    Code context using Exa. Finds real snippets and docs from GitHub, StackOverflow, and technical docs. Use when searching for code examples, API syntax, library documentation, or debugging help.

  • Exa labs exa mcp server financial report search 1.0.2

    VRIL-LABS/skill-jam/skills/search-research/exa-labs-exa-mcp-server-financial-report-search-1.0.2 Skill

    no license2★ repo

    Search for financial reports using Exa advanced search. Near-full filter support for finding SEC filings, earnings reports, and financial documents. Use when searching for 10-K filings, quarterly earnings, or annual reports.

  • Firecrawl cli firecrawl download 1.0.2

    VRIL-LABS/skill-jam/skills/search-research/firecrawl-cli-firecrawl-download-1.0.2 Skill

    no license2★ repo

    Download an entire website as local files — markdown, screenshots, or multiple formats per page. Use this skill when the user wants to save a site locally, download documentation for offline use, bulk-save pages as files, or says "download the site", "save as local files", "offline copy", "download all the docs", or "save for reference". Combines site mapping and scraping into organized local directories.

    The same file is in 3 other repositories

  • Tavily ai skills tavily crawl 1.0.1

    VRIL-LABS/skill-jam/skills/search-research/tavily-ai-skills-tavily-crawl-1.0.1 Skill

    no license2★ repo

    Crawl websites and extract content from multiple pages via the Tavily CLI. Use this skill when the user wants to crawl a site, download documentation, extract an entire docs section, bulk-extract pages, save a site as local markdown files, or says "crawl", "get all the pages", "download the docs", "extract everything under /docs", "bulk extract", or needs content from many pages on the same domain. Supports depth/breadth control, path filtering, semantic instructions, and saving each page as a local markdown file.

  • Kabilan108 dotfiles librarian 1.0.3

    VRIL-LABS/skill-jam/skills/writing-content/kabilan108-dotfiles-librarian-1.0.3 Skill

    no license2★ repo

    Gather and create documentation files for libraries and frameworks using Exa's code search. Creates organized markdown docs in config/claude/docs/ for future reference.

  • Kepano obsidian skills obsidian markdown 1.0.3

    VRIL-LABS/skill-jam/skills/writing-content/kepano-obsidian-skills-obsidian-markdown-1.0.3 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.

    The same file is in 15 other repositories

  • Copywriting

    t4sh/dotfiles/agents/skills/copywriting Skill

    no license2★ repo

    When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.

    The same file is in 5 other repositories

  • Design system

    t4sh/dotfiles/agents/skills/design-system Skill

    no license2★ repo

    Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

    The same file is in 3 other repositories

  • Documentation

    t4sh/dotfiles/agents/skills/documentation Skill

    no license2★ repo

    Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.

    The same file is in 4 other repositories

  • Grill with docs

    t4sh/dotfiles/agents/skills/grill-with-docs Skill

    no license2★ repo

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    The same file is in 19 other repositories

  • Research

    t4sh/dotfiles/agents/skills/research Skill

    no license2★ repo

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

    The same file is in 11 other repositories

  • Ux copy

    t4sh/dotfiles/agents/skills/ux-copy Skill

    no license2★ repo

    Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

    The same file is in 3 other repositories

  • Writing beats

    t4sh/dotfiles/agents/skills/writing-beats Skill

    no license2★ repo

    Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.

    The same file is in 5 other repositories

  • Writing fragments

    t4sh/dotfiles/agents/skills/writing-fragments Skill

    no license2★ repo

    Writing, explore — mine raw fragments, no structure yet.

    The same file is in 5 other repositories

  • Writing great skills

    t4sh/dotfiles/agents/skills/writing-great-skills Skill

    no license2★ repo

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

    The same file is in 11 other repositories

  • Writing plans

    t4sh/dotfiles/agents/skills/writing-plans Skill

    no license2★ repo

    Use when you have a spec or requirements for a multi-step task, before touching code

    The same file is in 7 other repositories

  • Writing shape

    t4sh/dotfiles/agents/skills/writing-shape Skill

    no license2★ repo

    Writing, exploit — shape raw material into an article, paragraph by paragraph.

    The same file is in 5 other repositories

  • Writing skills

    t4sh/dotfiles/agents/skills/writing-skills Skill

    no license2★ repo

    Use when creating new skills, editing existing skills, or verifying skills work before deployment

    The same file is in 4 other repositories

  • Docs gen

    GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/docs-gen Skill

    2★ repo

    Génère la documentation du projet : API docs, README, architecture. Utilise les scripts Python et l'analyse du code réel.

  • Skill scaffold

    jacob-balslev/skills/skills/agent-ops/skill-scaffold Skill

    2★ repo

    Use when creating a new SKILL.md from scratch, restructuring a draft before it becomes a stable skill, or teaching another author the canonical Skill Metadata Protocol frontmatter, body, and audit-state.json sidecar structure. Covers flat schema-conformant frontmatter, the sidecar split, v8 classification, body layout by skill intent, semantic-layer discipline (description vs activation vs Coverage), teaching-layer mechanics (TEMPLATE NOTE blockquotes), native skill-creator handoff, public/private safety, and routing-eval honesty. Do NOT use when modifying an already-written skill (edit it directly), writing general technical documentation, routing an existing request across skills, or fixing malformed library health at scale (use `skill-infrastructure`).

  • Summarization

    jacob-balslev/skills/skills/ai-engineering/summarization Skill

    2★ repo

    Use when condensing prose while preserving meaning: session findings, wrap reports, research briefs, executive summaries, TLDRs, agent handoffs, progressive summaries, audit summaries, and long-document distillation. Covers extractive vs abstractive summarization, what to keep vs drop, evidence preservation, summary levels, handoff summaries, and audit-report condensation without hiding findings. Do NOT use for byte/data compression algorithms (use `compression`), context-window budget math or compaction triggers (use `context-window`), working-set selection (use `context-management`), prose tone repair (use `writing-humanizer`), or quality scoring (use `evaluation`).

  • Microcopy

    jacob-balslev/skills/skills/design/microcopy Skill

    2★ repo

    Use when writing or reviewing functional UI text: button labels, empty states, tooltips, dialogs, placeholders, loading/progress messages, toasts, inline validation, permission copy, or onboarding steps. Covers interface-copy patterns such as verb-first action labels, acknowledge-explain-guide empty states, one-sentence tooltips, consequence-first confirmations, progressive loading language, and blur/fix validation messages. Do NOT use for marketing persuasion, documentation prose/guide structure, feedback-state staging, or general linguistic rationale behind wording.

  • Writing humanizer

    jacob-balslev/skills/skills/design/writing-humanizer Skill

    2★ repo

    Use when writing or editing human-readable prose such as docs, PRs, issues, release notes, errors, UI copy, commits, tooltips, or support replies, especially when text sounds robotic, padded, monotonous, or overly formal. Covers AI-tell removal, active voice, hedging reduction, readability diagnosis, sentence rhythm, vocabulary variety, tone mapping, paragraph rhythm, bullets-vs-prose choice, and the 5-step humanization workflow. Do NOT use for documentation routing/type selection, code-identifier naming, or in-product UI-text pattern catalogs.

  • Keywords

    jacob-balslev/skills/skills/knowledge-organization/keywords Skill

    2★ repo

    Use when doing keyword research, evidence-quality triage of keyword sources, query normalization, mapping search intent, building topical clusters, choosing terms for product or marketplace listings, researching question/answer-intent and entity demand for AI search (AEO/GEO), detecting cannibalization, or translating query demand into page/listing targets. Covers seed expansion, intent classification, clustering, entity/topic research, platform field translation for Etsy, Amazon, Shopify, SaaS/content sites, long-tail marketplace strategy, marketplace semantic-intent (Amazon COSMO/Rufus) checks, cannibalization resolution, and rank/AI-citation tracking cadence. Do NOT use for building SEO pages, schema strategy, or AI-search content implementation (use `seo-strategy`), writing the finished prose (use `writing-humanizer`), or designing navigation/page hierarchy (use `information-architecture`).

  • Linguistics

    jacob-balslev/skills/skills/knowledge-organization/linguistics Skill

    2★ repo

    Use when choosing semantically precise names for files/functions/variables/types/columns, resolving overloaded terms, reviewing error messages or UI copy for blame/register clarity, or adapting language for end-user/agent/developer/global-audience contexts. Covers morphology, compound-word order, abbreviation policy, verb-noun naming, polysemy qualification, audience register, blame-free error structure, and cross-cultural language awareness. Do NOT use for casing convention policy (use `naming-conventions`), call-site-wide renames (use `refactor`), docs/navigation structure (use `information-architecture`), specialized UI text pattern catalogs (use `microcopy`), or final prose humanization (use `writing-humanizer`).

  • A11y

    jacob-balslev/skills/skills/quality-assurance/a11y Skill

    2★ repo

    Use when building or reviewing interactive UI, forms, navigation, or dynamic content. Covers semantic HTML, keyboard access, focus management, labeling, state-change announcement, and reduced-motion / high-contrast preferences. Do NOT use for color-palette creation, visual branding, feedback-state staging, or prose reading-level accessibility - those belong to `visual-design-foundations`, `interaction-feedback`, and documentation respectively.

  • Cognitive load theory

    jacob-balslev/skills/skills/quality-assurance/cognitive-load-theory Skill

    2★ repo

    Sweller's Cognitive Load Theory (CLT) for agents reviewing skill bodies, prompts, documentation, dashboards, and agent outputs for avoidable cognitive burden. Working memory holds roughly 4 chunks at a time; CLT classifies load into intrinsic (irreducible task difficulty), extraneous (unnecessary load from poor presentation, ELIMINATE), and germane (the schema-building processing applied to intrinsic load, PROTECT). Use when writing a SKILL.md body (does this section add extraneous load?), designing prompts (am I asking the model to hold too much at once?), building dashboards (what is the per-screen cognitive budget?), authoring docs (is intrinsic load segmented?), or checking whether modern features (long context, structured outputs, prompt caching, subagents) actually reduce load or just move it elsewhere. Do NOT use for retrieval and session working-set design (use context-management), token budget math and compaction timing (use context-window), prompt engineering tactics (use prompt-craft), token-efficient representation mechanics (use compression), or instructional design beyond the CLT mechanisms named here.

  • Graph audit

    jacob-balslev/skills/skills/quality-assurance/graph-audit Skill

    2★ repo

    Use when checking that SKILL.md files and audit-state.json sidecars conform to the live Skill Metadata Protocol schemas, that manifest entries match the joined source model, that relation targets point at real sibling skills, or that Skill Graph routing/audit claims are backed by the current deterministic gates. Covers schema conformance, sidecar consistency, manifest sync, protocol/schema parity, drift baselines, routing-eval honesty, relation metadata and target-existence ownership gaps, application-eval shape, eval-artifact coherence, corpus conformance-ledger signals, inline corpus-count hygiene, Markdown-link integrity, grounding presence, and name-directory parity. Do NOT use for general code review, runtime agent debugging, prose rewriting, body-section refactoring, new-skill scaffolding, or maintaining the health-tooling implementation itself.

  • Owasp security

    jacob-balslev/skills/skills/quality-assurance/owasp-security Skill

    2★ repo

    Use when reviewing code for security vulnerabilities, threat-modelling a new feature, implementing authentication or authorization, handling user input, hardening dependencies or CI/CD against software-supply-chain compromise, or auditing a codebase against the current OWASP Top 10 (2025, with the 2021 mapping retained). Covers broken access control (incl. SSRF), security misconfiguration, software supply chain failures, cryptographic failures, injection (SQL, NoSQL, command, LDAP, XSS), insecure design, authentication failures, software/data integrity failures, security logging and alerting failures, and mishandling of exceptional conditions (fail-open error paths, error leakage). Do NOT use for general code review (use `code-review` for the holistic per-PR pass), for chasing a known production bug (use `debugging`), for defending an LLM against prompt/RAG injection or agent-tool-authority abuse (use `prompt-injection-defense`), or for writing a security policy doc (use `documentation`).

  • Testing strategy

    jacob-balslev/skills/skills/quality-assurance/testing-strategy Skill

    2★ repo

    Use when planning tests for a bug fix, feature, or refactor — deciding what deserves a test, at which level, with what evidence. Covers test-scope decisions, test-level selection (unit / integration / contract / e2e), effort-to-risk matching, regression targeting, evidence quality, and failure-case coverage. Do NOT use for chasing a known failure (that is `debugging`), for pure doc writing (that is `documentation`), or for conceptual architecture discussion with no verification target (no dedicated skill — treat as strategy, not testing).

  • Architecture decision records

    jacob-balslev/skills/skills/software-architecture/architecture-decision-records Skill

    2★ repo

    Use when writing, reviewing, or updating Architecture Decision Records: context, decision, options rejected, consequences, status, supersession, and follow-up verification. Do NOT use for general documentation prose (use `documentation`), code review findings (use `code-review`), or choosing between frameworks before a decision exists (use `framework-fit-analysis`).

  • Doc updater

    jacob-balslev/skills/skills/software-engineering-method/doc-updater Skill

    2★ repo

    Enforces the documentation-sync discipline: every code or behavior change ships its documentation in the SAME commit, never after. Provides the five-step workflow — diff the change, route each changed file to the doc that OWNS that behavior (document by ownership, not convenience), update each owning doc, verify the update actually landed, and report what was changed — plus the doc-type-purity and stale-reference gates that keep a docs corpus from drifting as code moves. Use at the pre-commit step of any task that changes code, when a change touches several docs, when renaming or deleting something that is referenced elsewhere, or whenever you are unsure which doc owns a change. Do NOT use for how to WRITE good documentation prose or pick a doc's Diátaxis type (that is a documentation-authoring skill), for choosing clear names (use `naming-conventions`), or for the broad cross-domain quality catalog (use `best-practice`).

  • Naming conventions

    jacob-balslev/skills/skills/software-engineering-method/naming-conventions Skill

    2★ repo

    Use when naming a new file, function, variable, type, route, database column, environment variable, or any other code or system artifact. Covers identifier morphology (verb-noun choice, plural vs singular, prefix/suffix conventions), kebab-case vs camelCase vs snake_case vs PascalCase per artifact kind, abbreviation rules, name-vs-path semantics, the rename-coordination workflow, and detection of names that lie. Do NOT use for content writing (use `documentation`), for restructuring already-named code (use `refactor`), or for human-language copy in product UI (separate skill, not in this library).

  • No cutting corners

    jacob-balslev/skills/skills/software-engineering-method/no-cutting-corners Skill

    2★ repo

    Enforces five non-negotiable quality pillars that counter the shortcuts an agent takes under training pressure: complete reporting (show ALL items, never filter unilaterally), verification (no claim of works/done/exists without a tool-call receipt in the same turn), thoroughness (every acceptance criterion individually verified; docs ship with the change), enrichment ('improve' means add capability, never trim), and anti-shortcut (exhaust deterministic lookup before guessing; findings demand action, not just filing). Use when reviewing any enumerated output for completeness, when an agent claims something works without evidence, when marking a task done, when asked to 'improve' or 'clean up' anything, or when findings are filed without being acted on. Do NOT use for the deep explanatory model of WHY completeness fails or the step-level execution mechanics (use `methodical`), for the cross-domain quality-standards catalog like OWASP/WCAG/SOLID (use `best-practice`), for scoring whether a result is good enough (use `evaluation`), or for compression after a complete enumeration exists (use `summarization`).

  • Refactor

    jacob-balslev/skills/skills/software-engineering-method/refactor Skill

    2★ repo

    Use when reorganizing existing code without changing external behavior — extracting functions, reducing duplication, renaming for clarity, splitting modules, or tightening structure. Covers behavior preservation, duplication reduction, decomposition, naming improvements, structural reorganization, and before/after verification. Do NOT use for bug investigation, adding new product behavior, or writing documentation (even when the docs describe the refactored code).

  • Podcast shownote gqxj

    carpo9984/GQXJ/skills/podcast-shownote-gqxj Skill

    no license2★ repo

    Generate a unified Chinese podcast ShowNote document in the "搞钱学姐版" format from a podcast transcript, then publish it as a Feishu document when Feishu tools are available. Always use this skill whenever the user says 做 show note, 做 ShowNote, 做 SHOWNOTE, 做 shownote, show note, ShowNote, SHOWNOTE, shownote, show notes, 播客 ShowNote, 收听指北, 时间轴, 嘉宾信息整理, or explicitly mentions 搞钱学姐版 / 学姐版 ShowNote. The skill creates a Markdown source draft with the fixed images, intro style, timeline, guest section, production credits, and final formatting checks.

  • Wassenger customer support

    wassengerhq/whatsapp-skills/skills/wassenger-customer-support Skill

    2★ repo

    Run a WhatsApp customer support operation with Wassenger — multi-agent inbox, auto-replies, business-hours, SLA tracking (first-response, resolution), escalation rules, ticket lifecycle, FAQ deflection, and reporting on team performance. Use when the user runs (or is building) a customer support team that handles tickets over WhatsApp and needs to organize the inbox, hit SLAs, and report on CSAT and workload.

  • Wassenger labels

    wassengerhq/whatsapp-skills/skills/wassenger-labels Skill

    2★ repo

    Manage labels on Wassenger chats and contacts — create, edit, delete, color-code, apply in bulk, query chats by label, and report on label usage. Use when the user wants to tag conversations for organization, segmentation, or reporting — for example, mark VIP customers, flag bugs, classify lead stages, or group chats by topic. Includes the recommended naming convention (`namespace:value`) and anti-patterns to avoid label rot.

  • Pull requests

    latent-variable/agentscope/skills/pull-requests Skill

    2★ repo

    How to write pull requests and commits, terse style, structure, and attribution. Load when opening a PR, writing a commit, or summarizing a branch.

  • Linkedin ghostwriter cost

    liftli-ai/skills/skills/linkedin-ghostwriter-cost Skill

    2★ repo

    Use when the user is weighing how to get LinkedIn content produced — hiring a ghostwriter, writing it themselves, or using software — computes the real cost of each option with the user's own numbers, including the hidden cost of DIY time.

  • Obsidian markdown

    matvej-melikhov/karpathy-llm-wiki/.claude/skills/obsidian-markdown Skill

    2★ repo

    Корректный Obsidian Flavored Markdown: wikilinks, embeds, properties, теги, выделение, math, таблицы, mermaid. Ссылайся на этот скилл при создании или редактировании любой wiki-страницы. Триггеры: obsidian syntax, wikilink, embed, obsidian markdown, формат wikilink, обсидиан синтаксис.

  • Portfolio writing

    ryanbaumann/fieldwork/.agents/skills/portfolio-writing Skill

    2★ repo

    How Ryan writes. Use whenever drafting or editing prose or copy for this site, including work case studies, blog posts, social posts, article headlines, page copy, talk titles and abstracts, naming, social preview copy, and link summaries.

  • Executing plans

    supper-skills/develpment-skills/skills/executing-plans Skill

    2★ repo

    Use when there is a written implementation plan to execute in the session. Load the plan, review it, execute all tasks, and report upon completion. Activate when user mentions "execute plan", "implement plan", "run plan", "start execution", or when a plan document is ready for implementation.

  • Writing plan

    supper-skills/develpment-skills/skills/writing-plan Skill

    2★ repo

    Implementation plan creation skill for multi-step tasks. Use when there are specifications or requirements, before directly touching code. Create detailed, executable implementation plans. Activate when user mentions "create plan", "implementation plan", "write plan", "plan", "task breakdown", or starts complex multi-step development work with existing specifications.

  • Writing plan

    supper-skills/develpment-skills/skills_zh-CN/writing-plan Skill

    2★ repo

    实施计划创建技能,用于多步骤任务。在有规范或需求时,在直接接触代码前使用本技能。创建详细、可执行的实施计划。当用户提及"创建计划"、"实施计划"、"编写计划"、"规划"、"任务分解"或开始复杂的多步骤开发工作且有现有规范时触发本技能。