agentsclimarketplace

Docs & writing

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

  • Stakeholder alignment

    viktorbezdek/skillstack/communication/skills/stakeholder-alignment Skill

    15★ repo

    Align stakeholders in writing using RFCs, design docs, proposals, pre-reads, and decision docs with explicit role assignments (DACI, RAPID). Use when the user asks to write an RFC, design doc, proposal, pre-read, or decision doc, wants to align async stakeholders on a decision, needs to assign deciders vs consulted vs informed, wants to structure a cross-team proposal, or is preparing a pre-read for a decision meeting. NOT for structuring a generic memo (use structured-writing). NOT for stakeholder power maps (use persona-mapping). NOT for storytelling pitches or investor decks (use storytelling-for-stakeholders).

  • Structured writing

    viktorbezdek/skillstack/communication/skills/structured-writing Skill

    15★ repo

    Structure a written piece using BLUF (Bottom Line Up Front), the Minto Pyramid Principle, inverted pyramid, or SPQR (Situation-Problem-Question- Resolution). Use when the user asks to write BLUF-style, apply the Pyramid Principle, structure a memo/email/doc, lead with the conclusion, outline a long message so it is skim-readable, or reorganize buried-lede writing. NOT for line-level clarity and concision editing (use clarity-editing). NOT for UI microcopy (use ux-writing). NOT for narrative or story arcs (use storytelling). NOT for slide decks (use frontend-slides).

  • Deslop ui

    viktorbezdek/skillstack/deslop/skills/deslop-ui Skill

    15★ repo

    Audit and rewrite UI copy to remove AI slop — overlong button labels, hedging error messages, corporate filler, and passive voice in interface text. Use when asked to clean up UI text, deslop interface copy, fix AI-sounding buttons or error messages, audit microcopy for AI patterns, or humanize product UI. Trigger phrases: "deslop", "anti-slop", "remove AI slop from UI", "clean up button labels", "fix error messages", "humanize interface text", "UI copy review". NOT for writing new UI copy from scratch (use ux-writing). NOT for marketing or editorial prose (use deslop-copy). NOT for code quality cleanup (use ai-slop-cleaner).

  • Documentation generator

    viktorbezdek/skillstack/documentation-generator/skills/documentation-generator Skill

    15★ repo

    Generate comprehensive documentation for a codebase by reading the repository and producing READMEs, API docs, architecture docs, and technical references. Use when the user asks to "document this repo", "generate docs", "write a README", "create API documentation", "document this codebase", "write architecture docs", or "produce technical references" for an existing project. NOT for UX copy, button labels, or interface microcopy (use ux-writing). NOT for pedagogical code examples or tutorials (use example-design). NOT for inline code comments. NOT for navigation or sitemap design (use navigation-design).

  • Edge case coverage

    viktorbezdek/skillstack/edge-case-coverage/skills/edge-case-coverage Skill

    15★ repo

    Identify and document boundary conditions, corner cases, error scenarios, and validation requirements that implementations must handle. Use when the user asks to find edge cases, identify corner cases, specify validation rules, enumerate error scenarios, harden a function against bad inputs, or think through what can go wrong at the boundaries of a system. NOT for writing the actual tests (use testing-framework or test-driven-development). NOT for structured risk registers around project-level risks (use risk-management). NOT for security vulnerability scanning (use code-review).

  • Example design

    viktorbezdek/skillstack/example-design/skills/example-design Skill

    15★ repo

    Design pedagogically effective code examples, tutorials, and runnable samples using progressive complexity and deliberate scaffolding. Use when the user asks to write a code example that teaches a concept, design a quickstart tutorial, create sample code for a library or API, build a runnable demo, or structure examples from simple to advanced. NOT for generating full repo documentation or READMEs (use documentation-generator). NOT for writing examples inside a skill file (use skill-foundry). NOT for API endpoint design (use api-design).

  • Navigation design

    viktorbezdek/skillstack/navigation-design/skills/navigation-design Skill

    15★ repo

    Design information architecture, wayfinding systems, and navigation structures for documentation sites and applications. Use when the user asks to design navigation, plan a sitemap, structure a sidebar or menu, define content hierarchy, design breadcrumbs, or organize how users move through content. NOT for user journey maps or touchpoint flows across time (use user-journey-design). NOT for microcopy, labels, or button text in navigation (use ux-writing). NOT for Next.js routing, layouts, or parallel routes (use nextjs-development).

  • Plugin documenter

    viktorbezdek/skillstack/plugin-dev/skills/plugin-documenter Skill

    15★ repo

    Generates comprehensive documentation for any Claude Code plugin by fetching and analyzing all source files. Use when you need to document a Claude plugin, write a plugin README, explain how a plugin works, generate plugin usage guides, create plugin tutorials, analyze a plugin architecture for documentation, or produce installation and setup instructions. Takes a GitHub URL or local path, fetches all plugin files, maps the component architecture, identifies real use-case scenarios from skill descriptions and reference content, and produces a complete documentation package with problem statement, architecture overview, component-by-component guide, realistic usage scenarios, installation instructions, and cross-reference map. NOT for building plugins (use plugin-architecture), NOT for validating plugin structure (use plugin-validation), NOT for evaluating plugin activation (use plugin-evaluation).

  • Plugin evaluation

    viktorbezdek/skillstack/plugin-dev/skills/plugin-evaluation Skill

    15★ repo

    Measures whether a Claude Code plugin actually works by running triggering evals (does the model pick the skill?) and output evals (does it produce correct results?). Use when you need to evaluate a plugin, run skill activation testing, set up an eval harness, measure plugin quality, write trigger rate tests, check output quality, compare plugin iterations, or iterate on a SKILL description based on eval results. Covers the two eval file formats (trigger-evals.json and evals.json), the grader/analyzer/comparator pattern from Anthropic's skill-creator, quality criteria for eval queries (realistic, varied, near-miss negatives), and the iteration methodology for fixing a skill that fails activation. NOT for writing the plugin's code itself — use plugin-architecture, plugin-hooks, or plugin-validation.

  • Plugin research

    viktorbezdek/skillstack/plugin-dev/skills/plugin-research Skill

    15★ repo

    Validates a plugin idea by surveying the marketplace, reading authoritative Anthropic sources, and deciding build-vs-fork-vs-skip before writing any code. Use when you want to research existing Claude Code plugins, check whether there is already a plugin for X, decide whether to build a new plugin or fork an existing one, run a marketplace survey before starting work, find authoritative documentation on a Claude Code feature, or gather primary sources for a plugin design. Covers the marketplace survey methodology, the canonical list of authoritative Anthropic URLs (code.claude.com, docs.claude.com, platform.claude.com, github.com/anthropics/claude-code, github.com/anthropics/skills, the Complete Guide PDF), community pattern discovery, and the build-vs-fork-vs-skip decision gate. NOT for deciding whether an idea is worth pursuing (use plugin-ideation) or for designing component layout (use plugin-architecture).

  • Value proposition design

    viktorbezdek/skillstack/product-thinking/skills/value-proposition-design Skill

    15★ repo

    Design a product value proposition using the Value Proposition Canvas (jobs, pains, gains, pain relievers, gain creators) and the Kano model. Use when the user asks to write a value proposition, map pains and gains to product features, apply VPC, distinguish basic/performance/delighter features (Kano), or articulate why a product matters to a specific customer. NOT for marketing copy or microcopy (use ux-writing). NOT for pitching the value prop to stakeholders (use storytelling-for-stakeholders). NOT for generic slogans.

  • Skill foundry

    viktorbezdek/skillstack/skill-foundry/skills/skill-foundry Skill

    15★ repo

    Author high-quality Claude Code SKILL.md files using philosophy-first design, evidence-based prompting, progressive disclosure, and anti-pattern prevention. Use when the user asks to write a skill file, create a new Claude Code skill, design a SKILL.md, review whether a skill's description will trigger correctly, or convert a workflow into a reusable skill. NOT for optimizing standalone prompts or system prompts (use prompt-engineering). NOT for full plugin development with hooks and MCP (use plugin-architecture). NOT for generating code documentation (use documentation-generator).

  • Build a plugin

    viktorbezdek/skillstack/skillstack-workflows/skills/build-a-plugin Skill

    15★ repo

    End-to-end workflow for authoring a Claude Code plugin from idea to validated, evaluated artifact. Composes six phases — ideation with a 7-criteria kill gate (plugin-ideation), marketplace survey and build-vs-fork decision (plugin-research), skill/hook/MCP/subagent/command decomposition (plugin-architecture), component implementation (plugin-hooks + plugin-composition + skill-creator), structural validation (plugin-validation), and trigger plus output evaluation with iteration loop (plugin-evaluation). Use when building a full Claude Code plugin with multiple components, hooks, MCP servers, or composed skills. Use when converting a working prototype into a shippable plugin. NOT for writing a single SKILL.md file — use the write-your-own-skill workflow for that. NOT for one-off prompt engineering — use prompt-engineering directly.

  • Content platform build

    viktorbezdek/skillstack/skillstack-workflows/skills/content-platform-build Skill

    15★ repo

    Layering workflow for building a knowledge base, CMS, documentation site, or structured content platform from scratch. Builds the data model first (content-modelling), adds a formal knowledge-graph layer if needed (ontology-design), establishes naming and taxonomy conventions (consistency-standards), designs information architecture (navigation-design), fine-tunes voice and microcopy (ux-writing), fills the structure with examples (example-design), and adds tooling for scale (documentation-generator). Use when starting a content or docs system from scratch, migrating one to a structured model, or rescuing one that has drifted into inconsistency. NOT for small single-page docs — use documentation-generator alone.

  • Storytelling for stakeholders

    viktorbezdek/skillstack/skillstack-workflows/skills/storytelling-for-stakeholders Skill

    15★ repo

    Narrative-build workflow for turning data, technical results, or project outcomes into a compelling story for leadership, investors, or customers. Structures the narrative using proven story frameworks — 3-act, SparkLines, situation-complication-resolution (storytelling), finds the surprising angle through lateral thinking and reframing (creative-problem-solving), anchors every claim to measurable business impact using OKRs and outcome vs output framing (outcome-orientation), then iterates through craft and polish. Use when presenting quarterly results to leadership, pitching a technical initiative to non-technical stakeholders, writing a case study, summarizing a project for board review, or defending a budget request with narrative. NOT for fiction writing — use storytelling directly. NOT for investor pitches with full research — use the pitch-sprint workflow instead.

  • Write your own skill

    viktorbezdek/skillstack/skillstack-workflows/skills/write-your-own-skill Skill

    15★ repo

    Meta-workflow for creating your own Claude Code skill that actually activates when needed and delivers genuine value. Starts with skill-creator as the canonical starting point, adds elicitation frameworks when the skill is for a human/domain area (interviewing, research, therapy-adjacent), designs the examples that will illustrate the skill (example-design), aligns with repo conventions (consistency-standards), writes structural validation tests before the content (test-driven-development), audits the draft against anti-patterns (critical-intuition), and generates the README with scenario tables (documentation-generator). Use when creating any new Claude Code skill that you want to be activation-reliable, well-scoped, and maintainable. NOT for quick-and-dirty prompts — use prompt-engineering directly.

  • Storytelling

    viktorbezdek/skillstack/storytelling/skills/storytelling Skill

    15★ repo

    Expert guidance for writing, editing, and teaching stories across fiction, business, data, speech, UX, and interactive narrative. Covers canonical story structures (3-act, Hero's Journey, Story Circle, Save the Cat, Kishōtenketsu, Freytag, Fichtean), business narrative frameworks (StoryBrand, Pixar Spine, Before-After-Bridge), data storytelling (Knaflic, situation-complication-resolution), speech writing (Duarte SparkLines, TED, Monroe's Motivated Sequence), narrative craft (character, scene, dialogue, POV), interactive narrative, and anti-pattern diagnostics. Use when writing or editing stories, designing pitches or presentations, structuring case studies, drafting speeches, planning interactive narratives, critiquing narrative work, or teaching storytelling. NOT for technical documentation (use documentation-generator). NOT for UX microcopy like button labels and error messages (use ux-writing). NOT for persona creation (use persona-definition).

  • Distribution craft

    viktorbezdek/skillstack/technical-copywriting/skills/distribution-craft Skill

    15★ repo

    Engineer the distribution layer of a long-form technical article — title, dek (subtitle), meta description, social pull-quotes, and channel-specific framing. Most technical articles die at the title; this skill covers the craft of titles that earn the click without clickbait, deks that confirm the promise, social pull-quotes for X / LinkedIn / Hacker News / Reddit, open-graph metadata, and the practice of reframing the same article differently per channel. Use when the user asks to write a title for an article, suggest titles, write a dek or subtitle, write a meta description, pull social quotes, prepare a launch, write a tweet thread for an article, reframe for LinkedIn / HN / Reddit, or audit existing distribution copy. NOT for the article body itself (use long-form-structure / engaging-craft / long-form-polish). NOT for SEO keyword research and on-page optimization beyond titles and meta (general SEO is out of scope). NOT for content marketing strategy. NOT for short-form business writing like email subject lines for work (use communication/structured-writing).

  • Engaging craft

    viktorbezdek/skillstack/technical-copywriting/skills/engaging-craft Skill

    15★ repo

    Apply proven copywriting techniques to long-form technical content so it holds attention from sentence to sentence — and humanize prose that reads AI-generated. Covers AIDA, PAS, Before-After-Bridge, Bencivenga's pyramid, Sugarman's slippery slide, Schwartz's awareness levels, hook engineering, voice and tonality calibration, the concrete-over-abstract discipline, and the AI-prose-tell catalog (banned high-frequency AI words like delve / underscore / pivotal / leverage; AI transitions like "that being said" / "at its core"; reflex hedges; academic filler verbs; buzzwords like revolutionize / cutting-edge / seamless integration; the six structural fingerprints; the sniff test). Use when the user asks to make an article more engaging, write a hook, calibrate voice, humanize AI-generated prose, remove AI tells, fix robotic or generic copy, replace abstract claims with concrete examples, or apply a copywriting formula. NOT for outlining or section structure (use long-form-structure). NOT for line-level clarity editing of short-form work writing (use communication/clarity-editing). NOT for research or sourcing (use technical-research). NOT for narrative storytelling craft (use storytelling).

  • Test driven development

    viktorbezdek/skillstack/test-driven-development/skills/test-driven-development Skill

    15★ repo

    Guides the Test-Driven Development methodology: the Red-Green-Refactor cycle of writing failing tests before implementation code, then making them pass with minimal code, then refactoring. Use when the user asks to do TDD, practice test-driven development, follow red-green-refactor, write tests first, apply test-first methodology, or implement a feature using TDD workflow with pytest, Vitest, ERT, or Zod. NOT for choosing or setting up test frameworks (use testing-framework), NOT for finding and fixing bugs or analyzing stack traces (use debugging), NOT for reviewing existing code or PRs (use code-review).

  • User journey design

    viktorbezdek/skillstack/user-journey-design/skills/user-journey-design Skill

    15★ repo

    Map user journeys with touchpoints, emotional states, pain points, and opportunities across the full arc of a user's experience over time. Use when the user asks to map a user journey, create a customer journey map, design a service blueprint, document touchpoints and friction points, or visualize the end-to-end experience of a user across multiple interactions. NOT for static navigation structure or sitemaps (use navigation-design). NOT for creating user personas or archetypes (use persona-definition). NOT for designing research interview flows (use elicitation). NOT for writing microcopy at specific touchpoints (use ux-writing).

  • Ux writing

    viktorbezdek/skillstack/ux-writing/skills/ux-writing Skill

    15★ repo

    Write effective microcopy, error messages, button labels, and interface text using UX writing principles. Use when crafting microcopy, UX copy, interface text, error messages, button labels, empty states, or conversational UI text. NOT for generating documentation (use documentation-generator). NOT for writing marketing copy or brand voice guidelines (use storytelling for narrative, not UI microcopy). NOT for designing the UI itself (use frontend-design or navigation-design). NOT for content strategy or information architecture (use content-modelling).

  • Human merge

    allemaar/open-skills/skills/human-merge Skill

    15★ repo

    Takes several separate reports — from several agents, several sources, or several documents — and returns one surface a person can decide from. Each report may be individually fine; the pile is what defeats the reader, and the relations between reports are invisible to every author who wrote one. Collapses reports that share an upstream source into the single source they are, names what is now superseded and whether a live decision rests on the dead figure, classifies conflicts instead of averaging them away, and pools coverage so a gap no single report had becomes visible. Works on any subject: research, legal, finance, operations, conservation, code. Trigger phrases: "/human-merge", "merge these reports", "combine what the agents found", "what do all of these add up to", "the sub-agents all came back", "did anything here contradict anything else". Not /human-output (the writing contract, which this skill links to rather than restates) or /human-rewrite (repairs one existing text and explicitly refuses several) — human-merge governs the pass across many.

  • Human output

    allemaar/open-skills/skills/human-output Skill

    15★ repo

    The contract for writing anything a person will read and decide from — a report, a finding, an answer, a request for a decision. Works on any subject: research, legal, finance, operations, planning, code. Referenced by other skills and invocable directly before a long piece of work. Trigger phrases: "/human-output", "remember I am a person not a machine", "write this for a human", "keep the reader in mind". Not /human-rewrite (repairs text that already exists) or /human-draw (builds a picture) — human-output governs writing as it happens.

  • Human rewrite

    allemaar/open-skills/skills/human-rewrite Skill

    15★ repo

    The repair pass on text that already exists — an agent's own last output, a subagent's report, a supplied document, a research summary, a legal or medical paragraph — rewritten so a person can read it fast and act on it, without changing what it claims. Meaning-preserving by contract: uncertainty, scope conditions, numbers, sample sizes, attribution, absent results, and reversing caveats all survive. Works on any subject, not just software. Trigger phrases: "/human-rewrite", "translate that into human", "that was a wall of text", "I can't follow this", "say that again but readable", "shorten this without losing anything". Not /human-output (the writing contract, which this skill links to rather than restates) or /human-draw (builds a picture) — human-rewrite governs the transformation of text that already exists.

  • Insight retro

    allemaar/open-skills/skills/insight-retro Skill

    15★ repo

    Post-implementation retrospective — map blast radius, audit documentation, extract skills, update KIs, document lessons learned. Trigger when the user runs /retro or asks for a "retrospective", "post-mortem", "lessons learned", or "what changed" after completing significant implementation work. Use insight-skill-gap when the goal is specifically to identify new or updated skills.

  • Obsidian markdown

    allemaar/open-skills/skills/obsidian-markdown Skill

    15★ repo

    Write valid Obsidian-Flavored Markdown — wikilinks, embeds, callouts, frontmatter properties, tags, comments. Trigger when the user creates or edits a .md file inside an Obsidian vault, or says "write this as an Obsidian note", "add a callout", "use wikilinks", "set frontmatter properties", "embed this image/note". Use obsidian-cli instead when the action needs a running Obsidian (search, open, plugin reload).

  • Yon write

    allemaar/open-skills/skills/yon-write Skill

    15★ repo

    YON Writing & Compilation Mode. Use when creating, generating, converting, or writing YON content. Triggers on: "write YON", "convert to YON", "create a .yon file", "encode this as YON", "YON format", or any request where the expected output is YON records. Also triggers when unstructured content should be structured into YON even without explicit keyword — e.g., working in a YON project. Use yon-read instead when reading, interpreting, explaining, or summarizing existing YON.

  • Bug reporting

    zivtech/accessibility-skills/.agents/skills/bug-reporting Skill

    15★ repo

    Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, or AI agent scans. The purpose of this skill is to make accessibility errors easier to report accurately, so that developers can reproduce, understand, and fix them without additional back-and-forth. Absolutely always include the required fields (URL, XPath, HTML snippet, WCAG SC, rule ID, severity, frequency) in every report. Under no circumstances file a vague report that omits the failing element, the WCAG criterion, or the steps to reproduce.

  • Doc coauthoring

    adryanmoldokkr32-pixel/anthropics-skills/skills/doc-coauthoring Skill

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

  • Docx

    adryanmoldokkr32-pixel/anthropics-skills/skills/docx Skill

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

    adryanmoldokkr32-pixel/anthropics-skills/skills/xlsx Skill

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

  • Write tests

    hellotern/Sextant/skills/write-tests Skill

    15★ repo

    You MUST use this skill before writing any test cases or adding test coverage. Use when the goal is to verify code behavior through tests — new tests, missing coverage, or a reproduction test after a bug fix. Stronger signals: "write tests", "add tests", "unit test", "integration test", "test coverage", "TDD", "test this function", "add a regression test". Also apply automatically after completing sextant:fix-bug, before marking the bug as resolved.

  • Project documentation pack

    charmonye/landkit/skills/project-documentation-pack Skill

    no license15★ repo

    Use after client approval to prepare, audit, or assemble the landscape project documentation set according to the studio's agreed scope for this client.

  • Gh issue report

    jackchuka/skills/gh-issue-report Skill

    15★ repo

    Investigate and file bug reports on GitHub repositories. Searches existing issues to avoid duplicates, checks contributing guides and issue templates, optionally confirms the bug in source code, and files a well-structured issue. Works on both local and remote repos. Triggers: "file a bug", "report issue", "is there a bug for", "check if reported", "investigate and file", "bug report on", "/gh-issue-report"

  • P blog post mining

    jackchuka/skills/p-blog-post-mining Skill

    15★ repo

    Mine development activities for blog-worthy topics and create outlines. Analyzes Claude session history, GitHub commits/PRs, Slack discussions, and Fireflies meeting recordings to find interesting stories. Use when the user wants blog ideas, content inspiration, or asks "what can I write about", "find blog material", "blog ideas from my work", "/blog-post-mining".

  • P blog writer

    jackchuka/skills/p-blog-writer Skill

    15★ repo

    Write blog posts in {user_name}'s voice with theoretical depth and persuasive arguments. Iterative workflow: intake → outline → section-by-section expansion → polish. Adapts to tool announcements, opinion pieces, deep-dives, and tutorials. Use when the user says "/blog-writer", "write a blog post", "draft an article about", "help me write about", or wants to create blog content.

  • P daily report

    jackchuka/skills/p-daily-report Skill

    15★ repo

    Use when reviewing what you worked on, creating standups, writing status updates, tracking daily/weekly progress, or asking "what did I do today"

  • P md to slides

    jackchuka/skills/p-md-to-slides Skill

    15★ repo

    Convert a structured Markdown deck source into a styled Google Slides presentation. Use this skill when the user has a slide.md file (or wants to write one) and wants Google Slides output — talks, LT decks, lecture slides, conference presentations, internal explainers. Trigger phrases include "md からスライド作って", "slide.md を Google Slides にして", "発表資料を Google Slides で", "convert this markdown to slides", "build a Google Slides deck from this markdown", "make slides from md", "/md-to-slides", and similar. Also use when the user references a presentation/<date>/slide.md file structure with `## Slide N — title`, `**話すこと:**`, and `**スライド要素:**` sections.

  • Iblai api org

    iblai/api/skills/iblai-api-org Skill

    15★ repo

    Read and write an ibl.ai organization's org-wide settings via the platform API — the org metadata object holding Default Agent, Help Center URL, Chat Area Width, and feature toggles (Help/Accessibility menus, Community Agents, Report Inappropriate Content). Use when configuring org-wide behavior.

  • Smalltalk developer

    mumez/smalltalk-dev-plugin/skills/smalltalk-developer Skill

    15★ repo

    Comprehensive Smalltalk (Pharo/Squeak) development workflow guide with AI-driven Tonel editing. Provides expertise in Tonel file format syntax (class definitions with name, superclass, instVars, category, method categories, class comment placement), package structure (package.st placement, directory organization, BaselineOf dependencies), development workflow (Edit → Import → Test cycle with absolute paths, re-import timing, test execution), and Smalltalk best practices (CRC format documentation, method categorization conventions). Use when working with Pharo or Squeak Smalltalk projects, creating or editing Tonel .st files, organizing packages and dependencies, resolving import order issues, writing class comments, implementing standard Smalltalk development patterns (Singleton, Settings, etc.), or troubleshooting Tonel syntax.

  • Docgen

    cofin/flow/plugins/flow/skills/docgen Skill

    15★ repo

    Use when generating documentation, writing API docs, documenting modules or components, creating README content, building reference guides, or documenting many files with explicit coverage tracking.

    The same file is in 1 other repository

  • Flow sync status

    cofin/flow/plugins/flow/skills/flow-sync-status Skill

    15★ repo

    Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.

    The same file is in 1 other repository

  • Docgen

    cofin/flow/skills/docgen Skill

    15★ repo

    Use when generating documentation, writing API docs, documenting modules or components, creating README content, building reference guides, or documenting many files with explicit coverage tracking.

    The same file is in 1 other repository

  • Flow sync status

    cofin/flow/skills/flow-sync-status Skill

    15★ repo

    Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.

    The same file is in 1 other repository

  • Image compress and docs

    EntityProcess/agentv/plugins/agentv-self/skills/image-compress-and-docs Skill

    15★ repo

    Capture, optimize, and publish screenshots to Astro docs. Use when asked to take screenshots for docs, update doc images, compress PNG assets, or add visual documentation to the agentv.dev docs site. Triggers on "add screenshots to docs", "update docs images", "compress screenshots", "optimize PNG", "document with screenshots".

  • Agentv bench

    EntityProcess/agentv/skills-data/agentv-bench Skill

    15★ repo

    Run AgentV evaluations and optimize agents through eval-driven iteration. Triggers: run evals, benchmark agents, optimize prompts/skills against evals, compare agent outputs across providers, analyze eval results, offline evaluation of recorded sessions, run autoresearch, optimize unattended, run overnight optimization loop. Not for: writing/editing eval YAML without running (use agentv-eval-writer), analyzing existing traces/JSONL without re-running (use agentv-trace-analyst).

  • Agentv eval review

    EntityProcess/agentv/skills-data/agentv-eval-review Skill

    15★ repo

    Use when reviewing eval YAML files for quality issues, linting eval files before committing, checking eval schema compliance, or when asked to "review these evals", "check eval quality", "lint eval files", or "validate eval structure". Do NOT use for writing evals (use agentv-eval-writer) or running evals (use agentv-bench).

  • Agentv eval writer

    EntityProcess/agentv/skills-data/agentv-eval-writer Skill

    15★ repo

    Write, edit, review, and validate AgentV EVAL.yaml / .eval.yaml evaluation files. Use when asked to create new eval files, update or fix existing ones, add or remove test cases, configure graders (`llm-rubric`, `script`), review whether an eval is correct or complete, convert between EVAL.yaml and evals.json using `agentv convert`, or generate eval test cases from chat transcripts (markdown conversation or JSON messages). Do NOT use for creating SKILL.md files, writing skill definitions, or running evals — running and benchmarking belongs to agentv-bench.

  • Go code organization

    v0lka/skills/development/idiomatic-go/go-code-organization Skill

    15★ repo

    Guides the agent to write well-organized Go code and projects. Use when writing or reviewing Go code involving variable scoping, nested control flow, init functions, getters/setters, interfaces, generics, type embedding, functional options, package structure, utility packages, package naming, code documentation, or linter configuration. Covers the 16 most common code and project organization mistakes in Go.

  • Go optimizations

    v0lka/skills/development/idiomatic-go/go-optimizations Skill

    15★ repo

    Guides the agent to write and review performance-sensitive Go code by applying CPU cache awareness, false sharing prevention, instruction-level parallelism, data alignment, escape analysis, allocation reduction, inlining, profiling, GC tuning, and Docker/Kubernetes GOMAXPROCS configuration. Use when writing hot-path Go code, reviewing performance-critical sections, reducing allocations, profiling applications, tuning GC behavior, or deploying Go services in containers.

  • Go strings

    v0lka/skills/development/idiomatic-go/go-strings Skill

    15★ repo

    Guides the agent to write correct and efficient Go string code. Use when writing or reviewing Go code that iterates over strings, concatenates strings, trims strings, converts between string and []byte, or extracts substrings. Covers rune semantics, string iteration pitfalls, trim vs. suffix/prefix functions, Builder-based concatenation, avoiding useless string/byte conversions, and preventing memory leaks from substrings.

  • Vibespec init

    v0lka/skills/development/sdd/vibespec-init Skill

    15★ repo

    Initialize a specification system for a project from scratch. Analyzes the codebase to identify architectural layers, domains, boundaries, and key decisions, then generates the initial set of specs (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR template). Use when bootstrapping specs for a new project, setting up documentation governance, or creating a spec system for an existing codebase that has none.

  • Secure go

    v0lka/skills/development/secure-go Skill

    15★ repo

    Write secure Go applications through everyday development practices — no AppSec expertise required. Covers the 12 OWASP Top 10 categories (2021 & 2025) with idiomatic Go patterns, standard library defaults, recommended libraries, and a security-focused linter setup. Use when writing or reviewing Go backend code, designing Go APIs, configuring production deployments, setting up CI/CD security checks, or hardening existing Go services.

  • Research synthesis

    v0lka/skills/engineering/research-synthesis Skill

    15★ repo

    Execute the synthesis phase of an research project. Analyzes the hypothesis graph, determines report verbosity (simple vs. complex path), generates the final report, creates a prototype inventory, and finalizes the implementation plan in the brief. Use when concluding a research project, writing the final report, or when the research question has been answered or the budget is exhausted.

  • Svelte code writer

    spences10/skills/svelte-code-writer Skill

    no license15★ repo

    Svelte code writing and validation workflow. Use when creating, editing, reviewing, or debugging .svelte, .svelte.ts, or .svelte.js files.

  • De postmortem

    ivanshamaev/de-agent-skills/skills/de_postmortem Skill

    no license15★ repo

    DE blameless postmortem — incident timeline reconstruction, impact quantification, root cause chain (5 Whys), corrective actions (CAPA), postmortem document template, severity classification, SLA breach reporting, communication templates, lessons-learned facilitation, postmortem review checklist

  • Code writing

    byronxlg/skillfold/library/skills/code-writing Skill

    15★ repo

    Write clean, correct, production-quality code.

  • Writing

    byronxlg/skillfold/library/skills/writing Skill

    15★ repo

    Produce clear, structured prose and documentation.

  • Blog post

    byronxlg/skillfold/skills/blog-post Skill

    15★ repo

    Write and publish a new blog post for the skillfold site (site/blog/). Use whenever asked to write a blog post, cover a news story about the agent tooling ecosystem, announce a feature rollout, publish the next post from the queue, or when the weekly blog automation runs. Covers the full pipeline - finding the story, verifying it against primary sources, writing the markdown post, regenerating the site, and shipping the PR.