Search Results for "document"
c4-modeling
C4 architectural modeling for documenting software architecture. Use when creating architecture diagrams, planning new systems, communicating with stakeholders, or conducting architecture reviews.
post-impl-docs
Update repository documentation after code implementation. Maintains README, CHANGELOG, docs/ folder, and inline docstrings based on changes made. Triggered by lane-executor after task completion.
docs-navigation
Navigate hierarchical ai-docs indexes to find documentation. Check local docs FIRST for speed and curated context before web searching. Covers Claude Code, BAML, MCP, and other tracked libraries.
docs-retrieval
Retrieve documentation context from local ai-docs. Check here first when implementing features, debugging errors, or needing library information. Fall back to web search if topic not found locally.
browser-discovery
Browser automation for documentation discovery. Use when curl fails on JS-rendered sites, when detecting available browser tools, or when configuring browser-based documentation collection.
investigation-creation
Create investigations from security events, detections, or LCQL queries. Performs HOLISTIC investigations - not just process trees, but initial access hunting, org-wide scope assessment, lateral movement detection, and full host context. Builds Investigation Hive records documenting findings with events, detections, entities, and analyst notes. Use for incident investigation, threat hunting, alert triage, or building SOC working reports.
reporting
Generate comprehensive multi-tenant security and operational reports from LimaCharlie. Provides billing summaries, usage roll-ups, detection trends, sensor health monitoring, and configuration audits across multiple organizations. Supports both per-tenant detailed breakdowns and cross-tenant aggregated roll-ups. Built with strict data accuracy guardrails to prevent fabricated metrics. Supports partial report generation when some organizations fail, with transparent error documentation. Time windows always displayed, detection limits clearly flagged, zero cost calculations.
smart-docs-updater
Intelligently updates CHANGELOG.md and documentation by tracking work sessions.Accumulates multiple related changes into ONE coherent entry instead of fragmented updates.Use this when:- User says "start working on X" or "fixing Y" (session start)- User says "done", "ship it", "finished with X" (session end - trigger docs update)- User asks to update changelog after multiple commitsDO NOT update docs after every small change. Wait for session completion.
architecture-adr
When making significant architectural decisions that need to be documented. Used by ARCHITECT-AGENT.
prd-structure
When creating or reviewing Product Requirements Documents. Used by PM-AGENT.
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.
technical-research
Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Preliminary phase before discussion-specification-plan-implement-review workflow. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in docs/workflow/research/ that may seed the technical-discussion phase.
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.
storybook-patterns
Component documentation, visual testing, interaction testing
council-verify
Verify code, documents, or implementation against requirements using LLM Council multi-model deliberation.Use when you need multi-model consensus on correctness, completeness, or quality.Keywords: verify, check, validate, review, approve, pass/fail, consensus, multi-model
research-opportunity-investigator
Conduct systematic research and opportunity investigation for ACP protocol integration, collaboration, and enhancement opportunities. Use when the user wants to research external projects, protocols, or tools for potential collaboration; investigate gap-filling opportunities for IDE integrations; assess compatibility between ACP and external protocols; or identify opportunities for ACP adoption. Guides through discovery, analysis, validation, and RFC generation with mandatory gates and source grounding. Outputs include comprehensive summary documents, gap analyses, and formal RFC proposals.
feature-implementation
Comprehensive checklist for implementing new features in Ishkul. Ensures all aspects are covered including frontend, backend, tests, E2E tests, infrastructure, and documentation. Use when starting work on a new feature or enhancement.
project-docs
Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USER_GUIDE, DEVELOPER_GUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files, or wants to set up docs for a new repository. Adapts to Python/Go projects and OpenSource/internal contexts.
Frequently Asked Questions
What is a Claude Skill?
It is a modular, protocol-based instruction set that enables Claude to perform specific tasks autonomously and efficiently.
How is this different from regular prompts?
Skills use the official Anthropic protocol for better token efficiency and automatic triggering compared to static prompts.
Does it support the new Claude Code CLI?
Yes, we provide specialized one-click installation commands designed specifically for Claude Code and OpenCode.
Can I use these skills in Cursor?
Absolutely, our library is fully compatible with popular IDEs and extensions including Cursor, Codex, and AntiGravity.
Are the skills on the website free to use?
Most skills in our 90,000+ database are free and open-source for the community to download and deploy.
How can I contribute my own skills?
Developers can easily share their work by submitting their own skill repositories through our community portal.