Browse Skills
1068 skills found
obsidian-mermaid.md
0
1
export
obsidian-mermaid
2
from
"AlejandroIglesiasCalvo/Coddex-Obsidian-Skills"
from
"AlejandroIglesiasCalvo/Coddex-Obsidian-Skills"
3
Crear diagramas Mermaid compatibles con Obsidian (flowchart, sequence, gantt). Evita errores comunes y produce diagramas simples y mantenibles.
2026-01-05
rust-dependency-analysis.md
0
1
export
rust-dependency-analysis
2
from
"danballance/claude"
from
"danballance/claude"
3
Use this skill when the user asks about Rust module dependencies, dependency graphs,architecture visualization, cycle detection, DAG analysis, or module structure. Activatewhen you see phrases like "show module structure", "dependency graph", "visualizearchitecture", "check for circular dependencies", or "Mermaid diagram of modules".
2026-01-05
go-uber-style.md
0
1
export
go-uber-style
2
from
"nhlongnguyen/dotfiles"
from
"nhlongnguyen/dotfiles"
3
Use this skill when writing Go code following the Uber Go Style Guide. Provides comprehensive guidance on idiomatic Go patterns, error handling, concurrency safety, performance optimization, and test-driven development. Covers all critical Uber Go rules including channel sizing, goroutine management, interface design, and proper error handling. Appropriate for any task involving .go files, Go code reviews, refactoring, or implementing Go best practices.
2026-01-05
entity-relation-based-documentation.md
0
1
export
entity-relation-based-documentation
2
from
"customer-cloud-club/meeting-visualizer"
from
"customer-cloud-club/meeting-visualizer"
3
Generate documentation for CCAGI system components, architecture, and workflows. Use when documenting features, updating architecture docs, or explaining how components work.
2026-01-05
docs-keeper.md
0
1
export
docs-keeper
2
from
"weppa-cloud/bukeer-flutter"
from
"weppa-cloud/bukeer-flutter"
3
Documentation organization, maintenance, and cleanup.USE WHEN: organizing docs, cleaning project root, updating documentation,checking for redundancy, maintaining docs structure.NOT FOR: technical implementation (use relevant technical skill).Examples:<example>Context: User added documentation to wrong location.user: "I added a new API doc file to the root directory"assistant: "I'll use docs-keeper to organize it in the proper docs/ location."<commentary>File organization is docs-keeper responsibility.</commentary></example><example>Context: User needs to update docs after code changes.user: "I modified the auth system and need to update the docs"assistant: "I'll use docs-keeper to update the authentication documentation."<commentary>Documentation updates are docs-keeper responsibility.</commentary></example>
2026-01-05
doc-serve.md
0
1
export
doc-serve
2
from
"SpillwaveSolutions/doc-serve-skill"
from
"SpillwaveSolutions/doc-serve-skill"
3
Advanced document search with BM25 keyword matching, semantic vector search, and hybrid retrieval.Enables precise technical queries, conceptual understanding, and intelligent result fusion.Supports local document indexing and provides comprehensive search capabilities for knowledge bases.
2026-01-05
brand-writing.md
0
1
export
brand-writing
2
from
"mattppal/shipping-szn"
from
"mattppal/shipping-szn"
3
Write content following Replit's brand voice and style guidelines. Use when creating or reviewing any user-facing content including changelogs, documentation, or marketing materials. Ensures consistent professional yet approachable tone.
2026-01-05
tech-report.md
0
1
export
tech-report
2
from
"michaeldubu/Nexus-Code-CLI"
from
"michaeldubu/Nexus-Code-CLI"
3
Generates professional technical reports from performance analysis data. Creates investor and client-ready documents with executive summaries, visualizations, and actionable recommendations.
2026-01-05
testing.md
0
1
export
testing
2
from
"nathanielcrowell12-spec/photo-vault"
from
"nathanielcrowell12-spec/photo-vault"
3
Implement testing patterns for PhotoVault using Playwright and Vitest. Use when writing E2E tests, unit tests, API route tests, or debugging flaky tests. Includes PhotoVault test fixtures, page objects, and Stripe webhook testing patterns.
2026-01-05
github-security-alert-fixer.md
0
1
export
github-security-alert-fixer
2
from
"bigandslow/cproj"
from
"bigandslow/cproj"
3
Systematically analyzes and fixes GitHub CodeQL security alerts with proper documentation and testing
2026-01-05
steering-workflow.md
0
1
export
steering-workflow
2
from
"anujkumar001111/xsky-agent"
from
"anujkumar001111/xsky-agent"
3
This skill should be used when the user asks about "steering documents", "project steering", "workflow setup", "CLAUDE.md configuration", "AGENTS.md", "AI agent project setup", or needs to understand how to configure steering documentation for AI-driven development workflows.
2026-01-05
develop-agent-skill.md
0
1
export
develop-agent-skill
2
from
"mikekelly/develop-agent-skill"
from
"mikekelly/develop-agent-skill"
3
Use PROACTIVELY when creating, reviewing, or updating Claude Code Skills. MUST be invoked before writing any new SKILL.md file. Provides structure, workflows, and validation for skill development.
2026-01-05
init-repo.md
0
1
export
init-repo
2
from
"SidU/GoodDocs"
from
"SidU/GoodDocs"
3
Initialize a fork of GoodDocs with fork-specific defaults and a customized doc type.
2026-01-05
summary-generator.md
0
1
export
summary-generator
2
from
"92Bilal26/TaskPilotAI"
from
"92Bilal26/TaskPilotAI"
3
This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.
2026-01-05
project-setup.md
0
1
export
project-setup
2
from
"score-ra/network-tools"
from
"score-ra/network-tools"
3
Automates new project setup from the software-dev-project-template including customization, documentation generation, and initial sprint planning
2026-01-05
holistic-seo.md
0
1
export
holistic-seo
2
from
"ogabasseyy/Baci"
from
"ogabasseyy/Baci"
3
Comprehensive SEO audit and optimization framework based on Koray Tuğberk GÜBÜR's Holistic SEO methodology. Use when performing SEO audits, creating content strategies, building topical authority, implementing semantic SEO, optimizing for E-E-A-T, or improving technical SEO. Covers topical maps, entity optimization, internal linking, structured data, Core Web Vitals, and content optimization for any website type including e-commerce, SaaS, blogs, and local businesses.
2026-01-05
codex-mcps.md
0
1
export
codex-mcps
2
from
"GantisStorm/claude-code-repoprompt-codex-plugins"
from
"GantisStorm/claude-code-repoprompt-codex-plugins"
3
Codex MCP tool reference. Supplemental parameter docs for codex tool (tuannvm/codex-mcp-server).
2026-01-05
sync-openapi.md
0
1
export
sync-openapi
2
from
"semicolon-devteam/sax-backend"
from
"semicolon-devteam/sax-backend"
3
core-interface OpenAPI 스펙 조회 및 동기화. Use when:(1) API 구현 전 스펙 확인, (2) Controller 작성 시 DTO 확인,(3) Response 형식 확인, (4) v0.4.x CODE 단계.
2026-01-05
ios26-research-assistant.md
0
1
export
ios26-research-assistant
2
from
"keiranhaax/fonic-hifi"
from
"keiranhaax/fonic-hifi"
3
Compensates for Claude's January 2025 knowledge cutoff by actively searching Apple's official iOS 26 documentation before making claims about iOS 26 APIs, frameworks, or features. This skill should be used when about to make statements about iOS 26 features, suggesting iOS 26-specific APIs, implementing iOS 26 functionality, or answering questions about iOS 26 capabilities. The skill provides multi-tier search workflows using Apple RAG, Sosumi, and web search tools with proper verification tagging.
2026-01-05
writing-use-cases.md
0
1
export
writing-use-cases
2
from
"mixomat/claude-plugins"
from
"mixomat/claude-plugins"
3
Create structured use case documentation with sequence diagrams for backend systems. Use when documenting API endpoints, service interactions, event flows, or system behaviors. Triggers on requests like "document this use case", "create use case for X endpoint", "write flow documentation", or "explain how X feature works".
2026-01-05
cto-audit.md
0
1
export
cto-audit
2
from
"jjeremycai/claude-toolkit"
from
"jjeremycai/claude-toolkit"
3
Perform deep, expert-level codebase and architecture audits to identify technical strengths, weaknesses, risks, and opportunities. Use when a user asks for an assessment of a codebase's structure, quality, or readiness for scale. Deliver detailed, actionable, and prioritized recommendations grounded in engineering best practices.
2026-01-05
miso.md
0
1
export
miso
2
from
"asnar00/miso"
from
"asnar00/miso"
3
Implement feature changes by updating pseudocode, platform code, and product code from modified feature markdown files. Use when user asks to "implement features", "run miso", "update implementations", or "sync code with features".
2026-01-05
markdown.md
0
1
export
markdown
2
from
"46ki75/skills"
from
"46ki75/skills"
3
Markdown linting and automated fixing using markdownlint-cli2. Use when Claude needs to: (1) Check markdown files for style issues, (2) Fix markdown formatting problems, (3) Ensure markdown follows best practices, (4) Validate markdown documents, or (5) Apply consistent markdown styling
2026-01-05
global-tech-stack.md
0
1
export
global-tech-stack
2
from
"overtimepog/AgentTheo"
from
"overtimepog/AgentTheo"
3
Reference and maintain the project's technology stack including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across the codebase. Use this skill when making technology decisions, adding new dependencies, choosing appropriate tools or libraries, configuring build systems, setting up testing frameworks, or documenting the tech stack. Apply this skill when selecting which framework, library, or tool to use for a given task, when ensuring code follows the conventions of the chosen stack (React patterns, Python idioms, Rails conventions), when integrating third-party services, or when documenting technology choices in README or architecture documentation. This skill ensures all team members use consistent technologies, new additions align with existing stack decisions, technology choices are documented with rationale, and the project maintains coherent patterns rather than mixing conflicting approaches or frameworks.
2026-01-05