Docs & Writing

ihj04982 Skill

Analyze codebase structure and update architecture documentation (codemaps/). Use when documenting architecture, onboarding, or after major refactors.

ihj04982 Bundle

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.

musserlab Bundle

Use when creating a new project, setting up a project from scratch, or when the user invokes /new-project. Scaffolds directory structure, environments, git, and Claude Code configuration. Supports data science, documentation, and general project types.

musserlab Bundle

Quarto document conventions for data science analysis scripts (.qmd). Use when creating or rendering .qmd analysis scripts in data science projects with numbered scripts, status fields, git hash capture, and BUILD_INFO.txt. Do NOT load for Quarto books, websites, or documentation projects — those use standard Quarto conventions without numbered script prefixes or BUILD_INFO.txt.

musserlab Skill

File a suggestion, bug report, or new-skill idea about the lab-claude-skills plugin as a GitHub issue on MusserLab/lab-claude-skills. Use when the user hits a limitation in a lab skill, says a skill did something wrong or didn't activate, wants to suggest a skill improvement or a new skill, or says "file a plugin issue", "report this skill", "suggest a skill", or invokes /plugin-feedback. Also invoked when Claude offers to capture skill friction per the general-reminders standing instruction. Do NOT load for the student-feedback / feedback-walkthrough advisor-feedback workflow, or for filing issues on a user's own project repo (use gh directly for those).

musserlab Skill

Initialize a new Quarto book project with GitHub Pages. Use when creating a new documentation site, tutorial, or book.

musserlab Skill

Script organization for data science analysis projects with numbered scripts, data/outs/ directories, and reproducibility conventions. Use when creating new analysis scripts in projects that follow data science conventions (numbered XX_ prefix scripts, outs/ directories, BUILD_INFO.txt). Do NOT load for documentation projects (Quarto books), infrastructure repos, or projects without data/outs/ directory structure.

beshkenadze Skill

Format and structure content as clean, well-organized Markdown. Use when asked to create documentation, format text, or generate Markdown output.

lohasle Skill

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

benjaming Skill

This skill should be used after pr-feedback triage, when the user has picked which review items to act on and wants them applied and answered — apply the agreed code change per item, then post the reply, reaction, and (for inline threads) thread resolution in one confirmed batch. Triggers on "apply the PR feedback", "respond to the reviewers", "resolve the threads", "post my replies", or selecting items after a pr-feedback report.

benjaming Bundle

Mine human review comments from merged PRs into recurring themes and propose where each rule should live (lefthook/Danger, CLAUDE.md, gate-wf reviewer). Report only, no edits.

benjaming Skill

This skill should be used when the user wants to write their end-of-day / evening "build-in-public" update for a given Linear project — 2-3 impact-focused bullets plus a Next line synthesized from the project's Linear activity and the repo's git/PR shipping evidence, ready to paste into the pod thread. Invoke as /build-in-public with a Linear project ID. Triggers on "build-in-public post", "evening update", "what did I ship today", "end-of-day update", or any variant of "what did I do today" for a work update — even without the word "skill". Default to drafting; never post anywhere automatically.

cognyai Skill

Auto-generate the weekly or monthly email performance report in three formats — Slack update, CEO email, board-deck section — from real ESP data

yeachan-heo-oh-my-codex Skill

Persistent markdown project wiki stored under repository omx_wiki with keyword search and lifecycle capture

yeachan-heo-oh-my-codex Skill

Adversarial dynamic e2e QA workflow - generate hostile scenarios, test, verify, fix, report, and clean up

texarkanine-cursor-rules Skill

How to write project architecture documentation as portable principles — genre framing, inclusion bars, orientation diagrams, invariants, and change-surface routing. Use when writing or improving architecture docs, systems atlases, or design-surface explanations (not product how-tos).

cygnusfear Bundle

Apply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.

artsmc-claude-dev-agents Bundle

Read and summarize the current state of the documentation hub (cline-docs/). Provides a quick overview of system architecture, module responsibilities, technology stack, and glossary terms. Use this skill whenever the user asks about the project's documentation, wants to understand the architecture, asks "what does this project do", "show me the docs", or needs a quick onboarding summary. Also use before starting work to understand project context.

artsmc-claude-dev-agents Bundle

Review and update Memory Bank files. Full mode reads all 6 files and proposes targeted updates; --quick mode (formerly memory-bank-sync) updates only activeContext.md + progress.md. Full mode for "update the memory bank", "refresh documentation", "sync all memory bank files", architecture changes, or major milestones. Quick for "quick save", "save my progress", "mark this as done", "update where I left off", or recording a finished task without a full review.

artsmc-claude-dev-agents Bundle

Comprehensive review and update of the documentation hub (cline-docs/). Analyzes recent code changes, detects drift, validates structure, and proposes specific updates to keep documentation synchronized with the codebase. Use this skill whenever the user says "update the docs", "sync documentation with code", "docs are outdated", or after significant code changes. For read-only analysis without changes, use document-hub-analyze instead.

artsmc-claude-dev-agents Bundle

Bootstrap a new project's Memory Bank by creating the six core files with templates and gathering initial project information from the user. Also the entry point to initialize/set up project documentation in a new or freshly cloned repo — including bootstrapping BOTH Brain systems (Memory Bank + Document Hub) at once.

artsmc-claude-dev-agents Bundle

Bootstrap a new project's documentation hub by creating the four core documentation files (systemArchitecture.md, keyPairResponsibility.md, glossary.md, techStack.md) with initial content based on codebase analysis.

navraj007in Skill

Generate OpenAPI 3.0 specification from blueprint API documentation. Creates interactive API docs that can be imported into Postman, Swagger UI, and other API testing tools.

adonis0123 Bundle

Generate structured weekly reports from Git commit history across one or multiple repositories. Use when you need concise, project-grouped progress summaries for status reporting.

artsmc-claude-dev-agents Bundle

Fast synchronization of activeContext.md and progress.md only. Lightweight alternative to full update for quick post-task documentation. Use this skill whenever the user says things like "quick save", "save my progress", "update where I left off", "just update progress", "mark this as done", or finishes a task and wants to record it without a full memory bank review. If the user only wants to update 1-2 files (not all 6), use this instead of memory-bank-update.

artsmc-claude-dev-agents Skill

Initialize Memory Bank and Document Hub if not already set up

artsmc-claude-dev-agents Bundle

Assess and score codebase architecture health — layer separation, SOLID compliance, module coupling (FAN-IN/FAN-OUT), circular dependencies, drift from documented patterns. Use whenever the user asks to assess/review/grade architecture quality, wants an architecture score, or asks how healthy the codebase's architecture is. Analysis-only report + refactoring tasks; for docs-vs-code drift use document-hub-analyze.

navraj007in Skill

Setup steps, credentials, free tiers, and documentation links for 70+ commonly used services. Use when listing required accounts or recommending third-party services.

navraj007in Skill

Extract and render all Mermaid diagrams from architecture blueprints to PNG images. Creates a diagrams/ folder with high-quality images ready for presentations and documentation.

helderberto Skill

Structurally edit and improve article drafts — reorder sections, tighten arguments, improve clarity. Use when user asks to "revise", "improve my article", "edit my draft", or "/revise". Don't use for typo fixes or formatting (use prose-fix), code documentation, or non-article content.

maroffo Skill

Run the local quality gates (`make check` + `make test-e2e`) and report commit/PR/excellence readiness per `rules/quality-gates.md`. Use when user says /score, is this ready to commit, is this ready for a PR, or score my changes.

amattas Skill

How user-facing and internal documentation should be written and maintained.

neuromechanist Bundle

Use this skill for "search for papers", "find citations", "look up a DOI", "get BibTeX", "download PDF", "convert PDF to markdown", "find canonical papers", "convert identifiers", "batch download papers", "configure opencite", "literature review", "find related papers", "what papers cite this", "export references", "read this paper", or mentions of opencite, Semantic Scholar, OpenAlex, PubMed, academic literature search, citation management, or paper retrieval.

helderberto Skill

Fix prose formatting, typos, and clarity issues in markdown or text files. Use when user asks to "fix dashes", "fix typos", "clean up text", "improve sentences", or "/prose-fix". Don't use for code style, linting, or full rewrites.

neuromechanist Bundle

This skill should be used when the user asks to "review a grant", "review my proposal", "score this grant", "evaluate my specific aims", "critique my research strategy", "review as an NIH reviewer", "review as an NSF panelist", "give me reviewer feedback", "check my grant proposal", "review my R01", "review my K99", "review my SBIR", "review my STTR", "review my Phase I application", "review my Phase II application", "review my commercialization plan", "evaluate my CAREER proposal", "run a mock study section", "review my resubmission", "review this PDF", "check my proposal PDF", "analyze my grant layout", or mentions grant review, proposal critique, NIH scoring, NSF panel review, small business grant review, study section feedback, or proposal PDF review.

kurokeita Bundle

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.