Docs & Writing

foscomputerservices Skill

Plan FOSMVVM implementation work with a design-first, DocC-first gate. Use BEFORE writing an implementation plan that adds or changes FOSMVVM types, protocols, ViewModels, requests, identities, or persistence — it applies FOSMVVM's design and documentation discipline up front, then hands task decomposition to your generic plan process.

dsifry Skill

Diagnostic status report — shows metaswarm installation state, project setup, and potential issues

imgly Bundle

Look up CE.SDK Vanilla JavaScript reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vanilla JavaScript — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Vanilla JavaScript doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vanilla JavaScript configuration user: "How do I configure the editor in Vanilla JavaScript?" assistant: "I'll use /cesdk:docs-js to look up configuration options." </example> <example> Context: User needs vanilla JS setup user: "How do I use CE.SDK without a framework?" assistant: "Let me use /cesdk:docs-js to find the relevant documentation." </example>

webdevtodayjason Skill

Technical writing best practices including documentation structure, clear writing principles, API documentation, tutorials, changelogs, and markdown formatting. Use when writing documentation, creating READMEs, documenting APIs, or writing tutorials.

mondaycom Skill

Analyze CRM activity data — rep performance, call and email volume, team activity breakdowns, and engagement stats. Use when someone says "how many calls did the team make", "show me rep activity", "who's the most active rep", "activity breakdown this week", "how is the team performing", "what's our outreach volume", "compare rep activity", "call stats", "email volume by rep", "activity report", or "team engagement stats".

a5c-ai Skill

help and documentation for babysitter command usage, processes, skills, agents, and methodologies. use this command to understand how to use babysitter effectively.

cyberelf Bundle

This skill provides a systematic approach for investigating and fixing bugs and issues in the codebase. Use this skill when users report bugs, unexpected behavior, test failures, or request fixes for specific issues. The skill guides through issue registration, root cause analysis, impact assessment, minimal code changes, quality validation, and E2E testing.

cyberelf Bundle

Build and expand an insight-ready raw-material layer by discovering page-level sources, deduplicating them with an internal pre-crawl link index, capturing raw Markdown, verifying metadata in place, and keeping ingest/register state aligned. Use for additive source harvesting, raw webpage capture, source registry maintenance, source/ingest tracking, source/raw downloads, and in-place verification rather than final synthesis.

lofcz Bundle

Generates complete Anthropic SKILL packages with proper structure, documentation, and automated download verification.

antoniocascais Bundle

Creates impressive LaTeX Beamer presentations with modern design. Generates .tex files with theme selection, font pairing, TikZ diagrams, overlays, and best practices. Use for LaTeX slides, Beamer presentations, scaffolding decks, slide design advice, or TikZ diagram generation.

imgly Bundle

Look up CE.SDK SvelteKit reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for SvelteKit — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing SvelteKit doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about SvelteKit configuration user: "How do I configure the editor in SvelteKit?" assistant: "I'll use /cesdk:docs-sveltekit to look up configuration options." </example> <example> Context: User asks about SvelteKit SSR user: "Does CE.SDK work with SvelteKit server-side rendering?" assistant: "Let me use /cesdk:docs-sveltekit to find the relevant documentation." </example>

imgly Bundle

Look up CE.SDK Node.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Node.js — configuration, headless rendering, export options, batch processing, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Node.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Node.js configuration user: "How do I configure the engine in Node.js?" assistant: "I'll use /cesdk:docs-node to look up configuration options." </example> <example> Context: User needs server-side generation user: "How do I use CE.SDK for server-side image generation?" assistant: "Let me use /cesdk:docs-node to find the relevant documentation." </example>

otrebu-agents Bundle

Scan ~/dev recursively for git repos and report today's work with commits, branches, stats, and detailed change analysis. Use when user asks "what did I work on", "show my work", "daily summary", "what repos did I touch".

karstenheld3 Bundle

Apply when converting, processing, or analyzing PDF files

msbart2 Skill

Add persona-grounded audience framing to a tech-talk. Selects 2–3 relevant personas, adds a "Who This Hits" box and up to 3 reaction lines to the README, and adds persona speaker notes to the slide deck. Triggers: "add personas", "who this hits", "persona reactions", "audience framing".

ddunnock Bundle

Stream long-form content to markdown files with resume capability. Writes content incrementally with section markers, enabling recovery if context limits are hit. Use when generating long documents (over 1000 lines), B-SPEC or specification writing, multi-section reports, any task where context compaction may occur mid-generation, or when user explicitly requests streaming output. Commands: init, write, status, resume, finalize, repair.

ddunnock Bundle

Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.

msbart2 Skill

Generates failing tests that reproduce reported bugs in FanHub. Use when a bug report comes in and you need to create a test that demonstrates the issue before fixing it. Follows FanHub's testing patterns and data integrity rules.

ddunnock Bundle

Conduct systematic trade study analyses using the DAU 9-Step Trade Study Process. Guides engineers through problem definition, root cause analysis (5 Whys, Fishbone), data collection from alternatives and datasheets, normalization calculations, weighted scoring, sensitivity analysis, and professional report generation with visualizations and decision matrices. Use when evaluating alternatives, comparing solutions, conducting trade-offs, or making engineering decisions.

ddunnock Bundle

Conduct Kepner-Tregoe (KT) Problem Solving and Decision Making (PSDM) analysis using the four rational processes - Situation Appraisal, Problem Analysis, Decision Analysis, and Potential Problem Analysis. Use when performing structured root cause analysis, making complex decisions, evaluating alternatives with weighted criteria, conducting IS/IS NOT specification analysis, anticipating implementation risks, troubleshooting complex issues, or when user mentions "Kepner-Tregoe", "KT method", "IS/IS NOT", "situation appraisal", "decision analysis", "MUSTS and WANTS", "potential problem analysis", or needs systematic problem-solving methodology. Includes specification matrices, decision scoring, quality rubrics, and professional report generation.

langadventurellc Bundle

Bumps version files (package.json, plugin.json, pyproject.toml, Cargo.toml, VERSION, etc.) based on a diff. Project-type aware — Claude Code plugin markdown under agents/, skills/, commands/, hooks/, and .claude-plugin/ is treated as runtime configuration, not prose docs. Use when the user invokes /planning:versioning or when an orchestrator calls this skill at the end of an implementation run. Requires an explicit bump level or --infer — empty input is an error.

langadventurellc Bundle

Reviews completed work and updates or creates project documentation (README, CLAUDE.md, AGENTS.md, .claude/rules/, docs/) to prevent stale docs. Invoked at the end of an implementation workflow with a base ref; diffs the working tree against that base to capture every change on the branch — committed and uncommitted.

langadventurellc Skill

Creates a Jira issue in the project's configured Jira instance from a free-form description. Use when the user says "create a Jira ticket", "file a Jira issue", "open a Jira ticket", "log a bug in Jira", "make a new Jira ticket", or "report this in Jira". Drafts an outcome-focused summary and a structured description, humanizes the prose sections, shows the draft, and waits for explicit user confirmation before submitting.

peabody124 Skill

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

christopheryeo Skill

Manages markdown journal files in a Journals/ folder — creating new journal files, adding date-stamped entries, and deleting entries. A journal is a markdown file named with reverse-month and purpose (e.g., "2026-03 Activities.md") containing chronological entries grouped under reverse-date headers. Three operations: CREATE-JOURNAL, CREATE-ENTRY, DELETE-ENTRY. Use whenever the user says "create a journal", "new journal", "journal entry", "add to journal", "delete journal entry", "remove entry", "show journals", or mentions logging thoughts, activities, notes, or reflections into a dated journal format.

christopheryeo Bundle

Create powerful presentations using Steve Jobs's 3-Second Rule methodology. Applies the Billboard Test principles for minimal cognitive load, maximum visual impact, and elegant slide design. Use when creating product launches, pitches, explanations, or any live presentation that requires high audience retention and visual clarity. Automatically integrates with Claude's PPTX skill to generate professional PowerPoint files and always applies the Sentient Brand Guidelines skill to ensure consistent branding.

peabody124 Skill

Use when the user asks for a periodic review of their GitHub activity, wants a summary of what they've been working on, asks "what have I done recently", "review my commits", "summarize my GitHub activity", or wants a cross-repository progress report. Also use when asked to review team activity, lab progress, or multi-repo development summaries. Defaults to 2-week window. Creates thematic report in scratch/.

mckinsey Skill

Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.

porteden Skill

Secure Google Slides Management. Use when the user wants to read presentation content, list slides, create a new deck, or manage sharing, permissions, renames, and deletes on Google Slides.

porteden Skill

Secure Calendar, Email, and Google Drive management - Gmail, Outlook & Exchange, Google Docs, Sheets & Slides. Use when the user wants to list, search, create, update, or delete calendar events, emails, or Drive/Docs/Sheets/Slides files across multiple accounts (gog-cli secure alternative).

get-convex Skill

Send THIS Codex session's transcript to the Convex quickstart backend for an AI post-mortem that improves the whole system (runbook, bootstrap, skills). TRIGGER when the user runs $improve-convex-plugin, or after a quickstart build says 'send feedback', 'report how that went', or 'help improve the quickstart'.

cellinlab Bundle

Book-to-writing-material skill for Chinese content creation. Use when Codex needs to break down a book, chapter, excerpt, reading note, or book link into reusable writing materials instead of a normal book report:观点、故事、金句化表达、概念对比、可直接调用的素材块，以及一篇适合交给 $deep-writer 继续深化的素材文章。

clickhouse-clickhouse Bundle

Show a report of open ClickHouse PRs whose only non-green CI check is "CH Inc sync" (or that are fully green) — i.e. effectively ready to merge. Groups by your authored PRs, PRs assigned to you (authored by others), and PRs by tracked authors (default groeneai). Shows the CH Inc sync state and whether each PR was ever approved; excludes already-merged PRs. Use when asked for "good PRs", merge-ready PRs, or PRs blocked only on the sync job.

christophe1997 Skill

Dry-run a tool call against the active yapermission policy and report which rule matched and why. Trigger when the user asks to test/debug/trace a yapermission rule, check whether a command would be auto-approved or blocked, or understand why a yapermission decision happened.

clickhouse-clickhouse Skill

Analyze CI performance comparison reports for a ClickHouse PR. Lists all regressions and improvements, cross-references with master history to distinguish real changes from flaky tests.

clickhouse-clickhouse Bundle

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches the failed tests and their output, classifies each as flaky vs a real regression using play.clickhouse.com master history, and for every failure searches for both an existing tracking GitHub issue and an existing fix (open/merged PR) — reporting, per failure, whether an issue still needs to be created and whether a fix exists with its status (WIP, merged, already in this branch or not). Downloads and reads the harness artifacts only for failures that history does not explain, and reports a root-cause hypothesis. Read-only first pass — never commits, pushes, or edits.