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

  • Copywriting

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/copywriting Skill

    no license1★ 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 email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.

    The same file is in 5 other repositories

  • Create pr

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/create-pr Skill

    no license1★ repo

    Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.

  • Daily news report

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/daily-news-report Skill

    no license1★ repo

    Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.

    The same file is in 11 other repositories

  • Data storytelling

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/data-storytelling Skill

    no license1★ repo

    Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

    The same file is in 1 other repository

  • Doc coauthoring

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/doc-coauthoring Skill

    no license1★ repo

    Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

    The same file is in 39 other repositories

  • Docs architect

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/docs-architect Skill

    no license1★ repo

    Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks.

    The same file is in 2 other repositories

  • Documentation generation doc generate

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/documentation-generation-doc-generate Skill

    no license1★ repo

    You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI...

    The same file is in 1 other repository

  • Documentation templates

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/documentation-templates Skill

    no license1★ repo

    Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

    The same file is in 2 other repositories

  • Docx

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/docx Skill

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

  • I18n localization

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/i18n-localization Skill

    no license1★ repo

    Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

    The same file is in 2 other repositories

  • Incident runbook templates

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/incident-runbook-templates Skill

    no license1★ repo

    Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident resp...

    The same file is in 1 other repository

  • N8n code python

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/n8n-code-python Skill

    no license1★ repo

    Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.

  • Openapi spec generation

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/openapi-spec-generation Skill

    no license1★ repo

    Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

  • Plan writing

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/plan-writing Skill

    no license1★ repo

    Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

    The same file is in 5 other repositories

  • Postgresql

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/postgresql Skill

    no license1★ repo

    PostgreSQL database documentation - SQL queries, database design, administration, performance tuning, and advanced features. Use when working with PostgreSQL databases, writing SQL, or managing database systems.

    The same file is in 3 other repositories

  • Postmortem writing

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/postmortem-writing Skill

    no license1★ repo

    Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...

    The same file is in 1 other repository

  • Readme

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/readme Skill

    no license1★ repo

    When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.

    The same file is in 1 other repository

  • Seo content writer

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/seo-content-writer Skill

    no license1★ repo

    This skill should be used when the user asks to "write SEO content", "create a blog post", "write an article", "content writing for SEO", "draft optimized content", "write a how-to guide", "create a product description", "write a landing page", "SEO copywriting", "draft content targeting [keyword]", or "write 2000-word article about [topic]". Creates keyword-optimized content using a 12-step workflow: CORE-EEAT pre-write checklist, keyword integration, title optimization (5 formula options), meta description, H1/H2/H3 hierarchy, featured snippet targeting, internal/external linking, and readability enhancement. Produces full drafts with embedded SEO elements, title variants, meta description, FAQ section with schema, and a self-scored CORE-EEAT checklist. For AI-citation optimization, see geo-content-optimizer. For updating existing content, see content-refresher.

  • Tutorial engineer

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/tutorial-engineer Skill

    no license1★ repo

    Creates step-by-step tutorials and educational content from code. Transforms complex concepts into progressive learning experiences with hands-on examples.

  • Writing plans

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/writing-plans Skill

    no license1★ repo

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

  • Writing skills

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/writing-skills Skill

    no license1★ repo

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

    The same file is in 7 other repositories

  • Xlsx

    ulpi-io/plugin-marketplace/plugins/sickn33/skills/xlsx Skill

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

  • C4 architecture

    ulpi-io/plugin-marketplace/plugins/softaworks/skills/c4-architecture Skill

    no license1★ repo

    Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture".

    The same file is in 7 other repositories

  • Writing clearly and concisely

    ulpi-io/plugin-marketplace/plugins/softaworks/skills/writing-clearly-and-concisely Skill

    no license1★ repo

    Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

    The same file is in 6 other repositories

  • Markdown converter

    ulpi-io/plugin-marketplace/plugins/steipete/skills/markdown-converter Skill

    no license1★ repo

    Convert documents and files to Markdown using markitdown. Use when converting PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx, .xls), HTML, CSV, JSON, XML, images (with EXIF/OCR), audio (with transcription), ZIP archives, YouTube URLs, or EPubs to Markdown format for LLM processing or text analysis.

  • Api documentation

    ulpi-io/plugin-marketplace/plugins/supercent-io/skills/api-documentation Skill

    no license1★ repo

    Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.

    The same file is in 4 other repositories

  • Crawl

    ulpi-io/plugin-marketplace/plugins/tavily-ai/skills/crawl Skill

    no license1★ repo

    Crawl any website and save pages as local markdown files. Use when you need to download documentation, knowledge bases, or web content for offline access or analysis. No code required - just provide a URL.

  • Extract

    ulpi-io/plugin-marketplace/plugins/tavily-ai/skills/extract Skill

    no license1★ repo

    Extract content from specific URLs using Tavily's extraction API. Returns clean markdown/text from web pages. Use when you have specific URLs and need their content without writing code.

    The same file is in 3 other repositories

  • Harness writing

    ulpi-io/plugin-marketplace/plugins/trailofbits/skills/harness-writing Skill

    no license1★ repo

    Techniques for writing effective fuzzing harnesses across languages. Use when creating new fuzz targets or improving existing harness code.

    The same file is in 4 other repositories

  • Building components

    ulpi-io/plugin-marketplace/plugins/vercel/skills/building-components Skill

    no license1★ repo

    Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.

    The same file is in 1 other repository

  • Update docs

    ulpi-io/plugin-marketplace/plugins/vercel/skills/update-docs Skill

    no license1★ repo

    This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

  • Changelog automation

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/changelog-automation Skill

    no license1★ repo

    Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

    The same file is in 1 other repository

  • Data storytelling

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/data-storytelling Skill

    no license1★ repo

    Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

    The same file is in 1 other repository

  • Openapi spec generation

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/openapi-spec-generation Skill

    no license1★ repo

    Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.

  • Python code style

    ulpi-io/plugin-marketplace/plugins/wshobson/skills/python-code-style Skill

    no license1★ repo

    Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

    The same file is in 4 other repositories

  • Rust skill creator

    ulpi-io/plugin-marketplace/plugins/zhanghandong/skills/rust-skill-creator Skill

    no license1★ repo

    Use when creating skills for Rust crates or std library documentation. Keywords: create rust skill, create crate skill, create std skill, 创建 rust skill, 创建 crate skill, 创建 std skill, 动态 rust skill, 动态 crate skill, skill for tokio, skill for serde, skill for axum, generate rust skill, rust 技能, crate 技能, 从文档创建skill, from docs create skill

  • Testing patterns

    mike-diff/ai-coding-configs/.claude/skills/testing-patterns Skill

    no license1★ repo

    Testing patterns for running and writing tests across project types. Use when running lint, typecheck, or tests, writing new tests, setting up test infrastructure, or diagnosing test failures. Covers auto-detection of test frameworks, error categorization, and structured reporting.

  • Testing patterns

    mike-diff/ai-coding-configs/plugins/agent-team/skills/testing-patterns Skill

    no license1★ repo

    Testing patterns for running and writing tests across project types. Use when running lint, typecheck, or tests, writing new tests, setting up test infrastructure, or diagnosing test failures. Covers auto-detection of test frameworks, error categorization, and structured reporting.

  • Github changelog

    tsubakimoto/skills/github-changelog Skill

    1★ repo

    Use this skill when the user wants to know what GitHub announced or released on a specific date, wants to review GitHub Changelog entries, needs a summary of recent GitHub features or changes, wants to build action plans based on GitHub product updates, or mentions "GitHub Changelog," "GitHub release notes," "what did GitHub ship," or "GitHubの更新." Trigger whenever the user asks about GitHub feature announcements, product updates, or wants to understand what changed in GitHub on a particular day. This skill fetches all posts from the GitHub Changelog RSS feed for a specified date and organizes them into summaries, action plans, and references (URLs).

  • Marp deck

    tsubakimoto/skills/marp-deck Skill

    1★ repo

    Use this skill whenever the user wants to create, outline, rewrite, or organize a presentation in Marp or Marpit Markdown. Trigger on requests to turn notes, docs, READMEs, specs, or outlines into slide Markdown; set up `marp: true` frontmatter; choose slide structure, directives, backgrounds, speaker flow, asset folders, or export commands; or build a new Markdown slide deck from scratch. Use it even when the user says 'presentation', 'deck', or 'slides' without naming Marp explicitly but the desired output is a Marp Markdown deck. If the task is mainly theme CSS or visual restyling, also consult `marp-css`.

  • Isolate

    ph3on1x/wisci/skills/isolate Skill

    1★ repo

    Delegates research and exploration to subagents with isolated context windows, then synthesizes findings inline and persists durable results to .wisci/context/ via the write skill. Use for investigating a codebase area, researching external docs or best practices, or comparing approaches without polluting the main context.

  • Write

    ph3on1x/wisci/skills/write Skill

    1★ repo

    Externalizes knowledge from the conversation into persistent, staleness-tracked markdown files under .wisci/context/. Use when research results, decisions, or findings are worth keeping beyond this session, or when the user wants context saved to disk.

  • Mdq

    akhy/agent-skills/mdq Skill

    no license1★ repo

    Query and filter Markdown documents using jq-like selector syntax — extract headings, list items, tasks, links, images, tables, code blocks, blockquotes, and paragraphs from markdown files. Useful for parsing README files, docs, changelogs, and any structured markdown.

  • Link rot detection

    jacob-balslev/skill-graph/examples/projects/markdown-static-site/skills/link-rot-detection Skill

    no license1★ repo

    Use when authoring or reviewing a periodic-scan job that walks every external link in a markdown content set and flags 404s, redirects to unrelated content, and connection failures. Activate this skill whenever the task says 'check our links' or mentions a link-rot scan, broken-link audit, or link-health report. Do NOT use for live runtime link checking inside the rendered page (use a frontend a11y / UX skill) or for chasing a specific broken-link incident from a user report (use debugging).

  • Markdown post frontmatter validation

    jacob-balslev/skill-graph/examples/projects/markdown-static-site/skills/markdown-post-frontmatter-validation Skill

    no license1★ repo

    Use when authoring or reviewing the frontmatter of a markdown post — checking required fields (title, date, slug, tags), validating against the content schema in `lib/content/schema.ts`, catching ambiguous date formats or tags not in the controlled vocabulary, and ensuring the slug matches the file path. Activate this skill whenever the task touches files under `content/posts/**/*.md`, the `parsePostFrontmatter()` helper, or any code path that reads YAML frontmatter from a content file. Do NOT use for general YAML schema design (use a generic schema-design skill) or for chasing a specific build-time validation failure (use debugging).

  • A11y

    jacob-balslev/skill-graph/marketplace/skills/a11y Skill

    no license1★ 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. Do NOT use for rewrite this error message at a 6th-grade reading level. Do NOT use for clean up this accessibility code without changing how it behaves.

  • Architecture decision records

    jacob-balslev/skill-graph/marketplace/skills/architecture-decision-records Skill

    no license1★ 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`). Do NOT use for write a general README section explaining how this module works. Do NOT use for choose which framework we should use for this project. Do NOT use for review this PR for bugs and regressions. Do NOT use for design the interface contract between these two services.

  • Autonomous loop patterns

    jacob-balslev/skill-graph/marketplace/skills/autonomous-loop-patterns Skill

    no license1★ repo

    Use when designing, reviewing, or debugging an autonomous AI agent loop: repeated agent execution, completion signals, checkpoints, supervisor respawn, stall detection, safety caps, and human handoff rules. Covers the core loop patterns from simple bounded runs through sentinel-based continuation, checkpoint-resume, and external supervisor loops. Do NOT use for choosing a specific agent product command (use agent-engineering or the product's docs), writing ordinary task instructions (use prompt-craft), or optimizing individual tool calls (use tool-call-strategy).

  • Claude code

    jacob-balslev/skill-graph/marketplace/skills/claude-code Skill

    no license1★ repo

    Use when deciding whether to run a task in the Claude Code agent harness, when scoping work to its native capabilities (skills, hooks, subagents, MCP, plan mode, 1M-context Opus, background tasks, slash commands), or when choosing Claude Code versus a different harness (Codex, OpenCode, Copilot) for a given piece of work. Covers what the harness is good at, the extensibility stack and when each layer earns its keep, and the decision boundaries against rival harnesses. Do NOT use for writing Anthropic SDK / API code (use `claude-api`), for choosing which Claude MODEL to route a task to versus GPT (use `gpt-5-5`), or for designing a generic autonomous agent loop (use `autonomous-loop-patterns`). Do NOT use for write a Python script that calls the Anthropic Messages API. Do NOT use for is GPT-5.5 or Opus better for this code review? Do NOT use for design a resumable autonomous loop with a supervisor.

  • Cognitive load theory

    jacob-balslev/skill-graph/marketplace/skills/cognitive-load-theory Skill

    no license1★ repo

    Sweller's Cognitive Load Theory (CLT) for agents reviewing skill bodies, prompts, docs, dashboards, and agent outputs for avoidable cognitive burden. Working memory holds ~4 chunks; CLT splits load into intrinsic (irreducible difficulty), extraneous (avoidable load from poor presentation — ELIMINATE), and germane (the schema-building work applied to intrinsic load — PROTECT). Use when writing a SKILL.md body, designing prompts (am I asking the model to hold too much at once?), building dashboards (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. Do NOT use for retrieval/session working-set design (use context-management), token budget and compaction timing (use context-window), prompt engineering tactics (use prompt-craft), or token-efficient representation (use compression).

  • Doc updater

    jacob-balslev/skill-graph/marketplace/skills/doc-updater Skill

    no license1★ 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`).

  • Error tracking

    jacob-balslev/skill-graph/marketplace/skills/error-tracking Skill

    no license1★ repo

    Use when designing or extending an application exception-reporting pipeline: error boundary placement, tracker SDK wrappers, sanitized reporting calls, environment gating, user context without PII leaks, breadcrumbs, and verification that each layer reports correctly. Covers component, route, global, and manual capture surfaces plus central `reportError`/`reportMessage` patterns. Do NOT use for the visual error UX shown to users (use `a11y` and interaction skills), chasing one captured error (use `debugging`), or broad privacy and retention policy (use `owasp-security`). Do NOT use for design accessible error-message copy and recovery UI for the 404 page. Do NOT use for the boundary fired but the tracker shows no event — root-cause it. Do NOT use for explain our error-tracking architecture in the contributor docs. Do NOT use for review this AI-generated error handler for correctness. Do NOT use for decide if the new error path needs an integration regression test.

  • Keywords

    jacob-balslev/skill-graph/marketplace/skills/keywords Skill

    no license1★ 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`). Do NOT use for build the SEO landing page, JSON-LD schema, and internal-linking plan from these keywords.

  • Linguistics

    jacob-balslev/skill-graph/marketplace/skills/linguistics Skill

    no license1★ 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`). Do NOT use for decide kebab-case vs snake_case vs camelCase for new database columns. Do NOT use for restructure this doc into a tutorial format with progressive disclosure. Do NOT use for implement Intl.NumberFormat for DKK vs USD currency formatting.

  • Microcopy

    jacob-balslev/skill-graph/marketplace/skills/microcopy Skill

    no license1★ 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. Do NOT use for write the marketing headline for the pricing page. Do NOT use for review this WCAG 2.2 contrast violation on the dashboard. Do NOT use for explain the morphology rule behind verb-first function names. Do NOT use for restructure this help-center article into a tutorial. Do NOT use for decide the kebab-case format for this new CSS class. Do NOT use for rename this React component across all call-sites.

  • Naming conventions

    jacob-balslev/skill-graph/marketplace/skills/naming-conventions Skill

    no license1★ 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). Do NOT use for refactor this 200-line function into smaller pieces. Do NOT use for write a doc explaining our naming conventions. Do NOT use for review this PR's naming choices. Do NOT use for the variable named `userIsActive` is logging the wrong value. Do NOT use for scaffold a new skill that teaches naming conventions.

  • No cutting corners

    jacob-balslev/skill-graph/marketplace/skills/no-cutting-corners Skill

    no license1★ repo

    Enforce five non-negotiable quality pillars as a pre-output gate: 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 verified with evidence; docs ship with the change), enrichment ('improve' adds capability, never trims), and anti-shortcut (exhaust deterministic lookup before guessing; findings demand action, not filing). Use when reviewing enumerated output for completeness, when an agent claims something works without evidence, when marking a task done, or when asked to 'improve' anything.

  • Owasp security

    jacob-balslev/skill-graph/marketplace/skills/owasp-security Skill

    no license1★ 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`).

  • Principled negotiation

    jacob-balslev/skill-graph/marketplace/skills/principled-negotiation Skill

    no license1★ repo

    Use when preparing, structuring, or pressure-testing a negotiation with principled negotiation / BATNA: separate people from the problem, focus on interests rather than positions, invent options for mutual gain, use objective criteria, define BATNA / reservation value / ZOPA, and decide whether to accept, improve, or walk away. Do NOT use for generic persuasion copy (use microcopy or writing-humanizer), unilateral conflict diagnosis without a deal table, competitive strategy analysis (use playing-to-win, porters-five-forces, or seven-powers), or broad decision scoring without counterparties (use expected-value or prioritization). Do NOT use for Write persuasive landing-page copy for this offer. Do NOT use for Analyze rivalry, supplier power, buyer power, entrants, and substitutes. Do NOT use for Choose our winning aspiration, where to play, and how to win. Do NOT use for Rank these initiatives by expected value and downside risk. Do NOT use for Give legal advice on whether this contract clause is enforceable.

  • Refactor

    jacob-balslev/skill-graph/marketplace/skills/refactor Skill

    no license1★ 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). Do NOT use for the test is failing after my edit — what did I break? Do NOT use for write an architecture note explaining this pattern for new team members. Do NOT use for reproduce why this function retries three times on transient network errors.