Back to tags
Tag

Agent Skills with tag: documentation

127 skills match this tag. Use tags to discover related Agent Skills and explore similar workflows.

write-docs

Write AI-scannable technical documentation.

technical-writingdocumentationstandardizationai-scannable
michalvavra
michalvavra
1

version-release

版本發布整合工具,處理 worklog 檢查、文件更新、合併推送等完整流程。三步驟流程:Pre-flight 檢查 → Document Updates → Git Operations。支援 check / update-docs / release 子命令,包含 --dry-run 預覽模式。

workflow-automationgitreleasedocumentation
tarrragon
tarrragon
1

red-team-reporting

Professional security report generation, executive summaries, finding documentation, and remediation tracking

red-teamreportingexecutive-summariesremediation-tracking
pluginagentmarketplace
pluginagentmarketplace
1

comprehensive-research

Multi-phase research orchestration for thorough codebase, documentation, and external knowledge investigation. Invoked by /ai-eng/research command. Use when conducting deep analysis, exploring codebases, investigating patterns, or synthesizing findings from multiple sources.

codebase-analysisdocumentationexternal-knowledgemulti-phase-research
v1truv1us
v1truv1us
11

technical-specification

Build validated specifications from discussion documents through collaborative refinement. Third phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) User asks to create/build a specification from discussions, (2) User wants to validate and refine discussion content before planning, (3) Converting discussion documents into standalone specifications, (4) User says 'specify this' or 'create a spec' after discussions, (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that technical-planning uses to build implementation plans.

specification-documentsworkflowvalidationplanning
leeovery
leeovery
1

technical-discussion

Document technical discussions as expert architect and meeting assistant. Capture context, decisions, edge cases, debates, and rationale without jumping to specification or implementation. Second phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) Users discuss/explore/debate architecture or design, (2) Working through edge cases before specification, (3) Need to document technical decisions and their rationale, (4) Capturing competing solutions and why choices were made. Creates documentation in docs/workflow/discussion/{topic}.md that technical-specification uses to build validated specifications.

architecturearchitectural-decisionsdecision-logstechnical-specifications
leeovery
leeovery
1

byterover-notion-sync

Advanced memory and knowledge management workflows for Byterover MCP Server. Use when creating implementation reports with timelines, documenting features as PRDs, or syncing project documentation folders with automatic conflict resolution. Extends basic retrieve/store operations with structured workflows for documentation, analysis, and knowledge synthesis.

knowledge-managementdocumentationconflict-resolutionworkflow-automation
RyanNg1403
RyanNg1403
4

Creating Agent Skills

Guide Claude through creating well-structured Agent Skills following best practices. Use when creating new Skills, authoring SKILL.md files, or when the user asks to build a Skill for Claude Code.

claudeskill-templateagent-frameworkbest-practices
camoneart
camoneart
4

youtube-to-knowledge-doc

Use when user provides YouTube URL and says "document this", "create notes", or "save this video". Automatically extracts transcript, determines folder placement, and generates Knowledge Framework documentation with MECE structure, Mermaid diagrams, and clickable timestamp citations.

youtubetranscriptiondocumentationmermaid
tekliner
tekliner
41

changelog-updater

Update CHANGELOG.md and TEST-CHANGELOG.md with new entries following Keep a Changelog format and token optimization principles. Use when adding changes to the changelog, documenting new features, fixes, or optimizations.

keep-a-changelogchangelogdocumentationtoken-optimization
phamhung075
phamhung075
31

repomix

Package entire code repositories into single AI-friendly files using Repomix. Capabilities include pack codebases with customizable include/exclude patterns, generate multiple output formats (XML, Markdown, plain text), preserve file structure and context, optimize for AI consumption with token counting, filter by file types and directories, add custom headers and summaries. Use when packaging codebases for AI analysis, creating repository snapshots for LLM context, analyzing third-party libraries, preparing for security audits, generating documentation context, or evaluating unfamiliar codebases.

repomixtoken-optimizationcodebase-analysisdocumentation
zircote
zircote
42

PRP Generator

Guides creation of Product Requirements Prompts (PRPs) - comprehensive requirement documents that serve as the foundation for AI-assisted development

prd-generationprompt-engineeringrequirements-analysistemplate
daffy0208
daffy0208
55

best-practices-extractor

Extract and generate coding best practices from PR review comments. Use when you want to analyze PR comments from a repository to create best practices documentation, or update existing standards with new feedback. Triggers include "extract best practices from repo X", "analyze PR comments", "update coding standards", or "generate best practices from PRs".

pull-requestscode-reviewcoding-standardsdocumentation
ItamarZand88
ItamarZand88
2

research

Use when needing to understand requirements before implementation. Gathers context from Jira, Confluence, codebase, and docs. Produces research document with confidence scoring.

jiraconfluencecodebasedocumentation
ferdiangunawan
ferdiangunawan
2

doc-coauthoring

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.

documentationcoauthoringcollaborationcontent-writing
Bbeierle12
Bbeierle12
3

documentation-standards

Apply documentation standards: comment why not what, minimal comments (prefer clear code), maintain README with quick start, update docs with breaking changes. Use when writing comments, creating docs, reviewing documentation, or discussing what to document.

documentationcommentsbest-practicesreadme
phrazzld
phrazzld
21

template-generator

Generate standardized document templates (DOCUMENT, TECHNICAL, PROPOSAL, RESEARCH, SECURITY-QA, INDEX) with YAML frontmatter, Quick Reference sections, and consistent structure for professional documentation.

document-templatesyaml-frontmatterquick-referencedocumentation
Tempuss
Tempuss
3

plugin-scaffolder

Scaffolds complete Claude Code plugin structures with all necessary directories, manifest, and documentation. Activates when user wants to create a new plugin, package features together, or prepare for marketplace distribution. Creates plugin.json, directory structure, and starter documentation. Use when user mentions "create plugin", "new plugin", "scaffold plugin", "plugin structure", or "share via marketplace".

claude-skillsplugin-developmentboilerplaterepository-structure
squirrelsoft-dev
squirrelsoft-dev
3

Page 4 of 8 · 127 results