Documentation skills for markdown, PDFs, knowledge bases, and content operations.
This directory brings installable AI Agent skills into one place so you can filter by search, category, topic, and official source, then install them directly into Claude Code, Cursor, Windsurf, and other supported environments.
This skill should be used when the user asks to look up Effect API, check the Effect docs, find Effect function signature, what does Effect.X do, how to use Effect.X, Effect API reference, fetch Effect documentation, or needs to look up specific function signatures, parameters, or usage examples from the official Effect-TS API documentation.
This skill should be used when the user asks about plugin settings, store plugin configuration, user-configurable plugin, .local.md files, plugin state files, read YAML frontmatter, per-project plugin settings, or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Run Agent Workbench (awb) interactive UI components from Codex or the CLI. Use when the user needs a confirmation, checklist, input, table, code or markdown view, or a visual playground. Always follow interactive runs with awb wait and the returned ID. Use tmux for long-running commands (see awb --help).
Format blog content into properly structured markdown files for Next.js portfolio blog. Use when user wants to: (1) Format raw blog content into markdown with frontmatter, (2) Create new blog posts from topics or titles, (3) Generate blog post files with proper metadata (title, excerpt, date, author) and save to _posts/ directory. Automatically generates excerpts, converts titles to kebab-case filenames, and ensures proper frontmatter format.
Suggests one appropriate branch name and a PR description in the project template (title, Description, Test plan, Documentation update) for Calimero core. Use when creating a PR for core, or when the user asks for a branch name and PR description.
프로젝트 문서 작성 템플릿을 제공합니다. README, API 문서, 컴포넌트 문서 작성 시 사용합니다. documentation-writer 에이전트와 함께 사용하세요.
Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.
Create or update a feature spec under `docs/Features/` using `docs/templates/Feature-Template.md`: business rules, user flows, system behaviour, Mermaid diagram(s), verification plan, and Definition of Done. Use before implementing a non-trivial feature or when behaviour changes; keep the spec executable (test flows + traceability to tests).
Implement a new TAPD API endpoint in the go-tapd SDK when a user provides an API documentation URL or asks to add/implement an endpoint (Story/Bug/Task/Iteration/etc.), including request/response structs, service methods, tests, test data, and features.md updates.
Create DevTrail documentation. Analyzes context to suggest document type or accepts explicit type parameter. Always confirms before creating.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for shadcn init, create an app with --preset, or switch to --preset.
PDF manipulation toolkit. Extract text/tables, create PDFs, merge/split, fill forms, for programmatic document processing and analysis.