Browse Skills
16146 skills found
testdrivendevelopment.md
14
1
export
testdrivendevelopment
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Disciplined TDD workflow enforcing red-green-refactor cycle and the "iron law" of no production code without failing tests first. USE WHEN user wants to write tests first OR implement new feature with TDD OR fix bugs with test coverage OR explicitly requests TDD approach. Enforces systematic test-first development with verification at each step.
2026-01-05
github.md
14
1
export
github
2
from
"vdemeester/home"
from
"vdemeester/home"
3
GitHub repository and pull request management. USE WHEN working with GitHub PRs, checking CI/CD status, reviewing pull requests, managing issues, or using gh CLI commands.
2026-01-05
maestro-workflow.md
14
1
export
maestro-workflow
2
from
"sionic-ai/sionic-maestro-skills"
from
"sionic-ai/sionic-maestro-skills"
3
Multi-LLM orchestration implementing the 5-stage coding workflow: Example Analysis → Hypothesis → Implementation → Debug Loop → Recursive Improvement.
Based on "Towards a Science of Scaling Agent Systems" (Kim et al., 2025): - Centralized Consult architecture (Claude orchestrates, others advise) - Measured coordination (avoid MAS overhead in tool-heavy stages) - Tests-first selection (Poetiq pattern, not voting)
Use when: Debugging complex issues, analyzing unfamiliar code, refactoring, or any task that benefits from diverse LLM perspectives with verification.
2026-01-14
fabric-cli.md
14
1
export
fabric-cli
2
from
"data-goblin/fabric-cli-plugin"
from
"data-goblin/fabric-cli-plugin"
3
Use Microsoft Fabric CLI (fab) to manage workspaces, semantic models, reports, notebooks, lakehouses, and other Fabric resources via file-system metaphor and commands. Use when deploying Fabric items, running jobs, querying data, managing OneLake files, or automating Fabric operations. Invoke this skill automatically whenever a user mentions the Fabric CLI, fab, or Fabric.
2026-01-15
core.md
14
1
export
core
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Personal AI Infrastructure core principles and operating system. AUTO-LOADS at session start. USE WHEN any session begins OR user asks about identity, response patterns, workflow preferences, or core principles.
2026-01-05
ai4curation-configuration.md
14
1
export
ai4curation-configuration
2
from
"ai4curation/curation-skills"
from
"ai4curation/curation-skills"
3
Skill to assist with how a GitHub repository is configured with GitHub integrations, including instructions for agents in markdown (AGENTS and CLAUDE), github actions for invoking agents, and specific localization procedures such as defining claude/codex skills, or claude subagents. The skill helps with both technical aspects, and with best practice for guiding agents.
2026-01-21
jira-work-starter.md
14
1
export
jira-work-starter
2
from
"juanibiapina/dotfiles"
from
"juanibiapina/dotfiles"
3
This skill should be used when the user wants to start working on a Jira ticket. Trigger when user says "Let's work on [JIRA_URL]" or similar phrases indicating intent to begin work on a specific Jira issue. The skill orchestrates environment preparation, information gathering, and branch creation for development work.
2026-01-21
api-proxy.md
14
1
export
api-proxy
2
from
"abra5umente/api-proxy"
from
"abra5umente/api-proxy"
3
Routes API requests through the user's residential proxy to bypass cloud IP blocks. TWO use cases - (1) Runtime fallback when direct curl/fetch fails with 403/blocked errors, use fetch.py for quick retry. (2) Template for building new skills that need proxy routing, copy proxy_helper.py into the new skill.
2026-01-11
analyze-wast.md
14
1
export
analyze-wast
2
from
"Milky2018/wasmoon"
from
"Milky2018/wasmoon"
3
Analyze WebAssembly test (WAST) files to debug compilation issues and create regression tests. Use when the user asks to debug or analyze WAST test failures, investigate compilation bugs in wasmoon, or when encountering test failures in spec/*.wast files. Triggers include "analyze wast", "debug wast", "wast bug", or references to specific .wast test files.
2026-01-21
codex.md
14
1
export
codex
2
from
"keboola/osiris"
from
"keboola/osiris"
3
Invoke OpenAI Codex CLI for second opinions, multi-model analysis, architectural validation, or structured JSON output. Use when you need external AI perspective from OpenAI models to validate your decisions or get comparative analysis.
2025-11-21
kubernetes.md
14
1
export
kubernetes
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Kubernetes development and operations best practices. USE WHEN working with kubectl commands, K8s manifests, deployments, debugging pods, managing resources, RBAC, or cluster operations.
2026-01-05
osiris-component-developer.md
14
1
export
osiris-component-developer
2
from
"keboola/osiris"
from
"keboola/osiris"
3
Create production-ready Osiris ETL components (extractors, writers, processors). Use when building new components, implementing capabilities (discover, streaming, bulkOperations), adding doctor/healthcheck methods, packaging for distribution, validating against 60-rule checklist, or ensuring E2B cloud compatibility. Supports third-party component development in isolated projects.
2025-11-21
commit.md
14
1
export
commit
2
from
"Milky2018/wasmoon"
from
"Milky2018/wasmoon"
3
Safe git commit workflow that prevents commits to main branch. Use when the user asks to "commit changes", "save changes", "git commit", or when completing a task that needs version control. Automatically creates feature branches when on main. NEVER creates pull requests unless explicitly requested by the user.
2026-01-21
systematicdebugging.md
14
1
export
systematicdebugging
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Evidence-based debugging methodology emphasizing observation over assumptions following the scientific method. USE WHEN user reports a bug OR system behavior is unexpected OR troubleshooting issues OR investigating errors OR debugging failures. Follows observe, hypothesize, test, verify cycle with disciplined evidence gathering.
2026-01-05
docker.md
14
1
export
docker
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Container management with Docker and Podman. USE WHEN building images, managing containers, working with compose files, debugging containers, managing networks/volumes, scanning for vulnerabilities, or optimizing images.
2026-01-05
home-assistant-diagnostics.md
14
1
export
home-assistant-diagnostics
2
from
"andrew-blake/melcloudhome"
from
"andrew-blake/melcloudhome"
3
Diagnose Home Assistant errors by connecting via SSH, checking Docker containers, reading logs, and identifying integration issues. Use when the user mentions Home Assistant errors, issues, problems, diagnostics, or when they want to troubleshoot their HA system.
2026-01-22
PAI.md
14
1
export
PAI
2
from
"danielmiessler/PAIPlugin"
from
"danielmiessler/PAIPlugin"
3
Personal AI Infrastructure (PAI) - PAI System Template
MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability.
=== CORE IDENTITY (Always Active) ===
Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas]
Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend]
Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.]
Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management
Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.]
=== ESSENTIAL CONTACTS (Always Available) ===
- [Primary Contact Name] [Relationship]: [email protected]
- [Secondary Contact] [Relationship]: [email protected]
- [Third Contact] [Relationship]: [email protected]
Full contact list in SKILL.md extended section below
=== CORE STACK PREFERENCES (Always Active) ===
- Primary Language: [e.g., TypeScript, Python, Rust]
- Package managers: [e.g., bun for JS/TS, uv for Python]
- Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked
- Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks
=== CRITICAL SECURITY (Always Active) ===
- NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit
- `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos
- CHECK THREE TIMES before git add/commit from any directory
- [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.]
=== RESPONSE FORMAT (Always Use) ===
Use this structured format for every response:
📋 SUMMARY: Brief overview of request and accomplishment
🔍 ANALYSIS: Key findings and context
⚡ ACTIONS: Steps taken with tools used
✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT
📊 STATUS: Current state after completion
➡️ NEXT: Recommended follow-up actions
🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"]
🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words]
=== PAI/KAI SYSTEM ARCHITECTURE ===
This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt).
Full context loaded from SKILL.md for comprehensive tasks, including:
- Complete contact list and social media accounts
- Voice IDs for agent routing (if using ElevenLabs)
- Extended security procedures and infrastructure caution
- Detailed scratchpad instructions
=== CONTEXT LOADING STRATEGY ===
- Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available
- Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details
=== WHEN TO LOAD FULL CONTEXT ===
Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests.
=== DATE AWARENESS ===
Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.
2026-01-11
python.md
14
1
export
python
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Python development best practices and modern tooling with uv. USE WHEN writing Python code, managing dependencies, testing, type checking, or working with Python projects.
2026-01-05
tekton.md
14
1
export
tekton
2
from
"vdemeester/home"
from
"vdemeester/home"
3
Tekton Pipelines CI/CD best practices for Kubernetes-native workflows. USE WHEN working with Tekton tasks, pipelines, triggers, building container images, GitOps integration, or cloud-native CI/CD.
2026-01-05
rust-webapp.md
14
1
export
rust-webapp
2
from
"arsenyinfo/rust-webapp-skill"
from
"arsenyinfo/rust-webapp-skill"
3
Build full-stack web applications using Rust (Axum + SQLx) with HTMX + Alpine.js frontend and Neon (serverless PostgreSQL). Use when asked to create web apps, CRUD apps, dashboards, forms, or any stateful web application. Triggers on requests like "build a todo app", "create a voting app", "make a dashboard", "build a blog", etc.
2026-01-06
brand-positioning.md
13
1
export
brand-positioning
2
from
"majesticlabs-dev/majestic-marketplace"
from
"majesticlabs-dev/majestic-marketplace"
3
Define your brand's core identity - purpose, values, personality, and positioning statement. Creates the strategic foundation that informs voice, design, and all brand decisions.
2026-01-22
polyglot-rust-c.md
13
1
export
polyglot-rust-c
2
from
"letta-ai/skills"
from
"letta-ai/skills"
3
Guidance for creating polyglot source files that compile and run correctly as both Rust and C or C++. This skill applies when tasks require writing code that is valid in multiple languages simultaneously, exploiting comment syntax differences or preprocessor directives to create dual-language source files. Use this skill for polyglot programming challenges, CTF tasks, or educational exercises involving multi-language source compatibility.
2026-01-21
compile-compcert.md
13
1
export
compile-compcert
2
from
"letta-ai/skills"
from
"letta-ai/skills"
3
Guidance for building CompCert, a formally verified C compiler. This skill applies when tasks involve compiling CompCert from source, setting up Coq/OCaml environments with opam, or building software with strict proof assistant dependencies. Use for CompCert compilation, Coq-dependent project builds, or formal verification toolchain setup.
2026-01-21
ln-360-codebase-auditor.md
13
1
export
ln-360-codebase-auditor
2
from
"levnikolaevich/claude-code-skills"
from
"levnikolaevich/claude-code-skills"
3
Coordinates 9 specialized audit workers (security, build, architecture, code quality, dependencies, dead code, observability, concurrency, lifecycle). Researches best practices, delegates parallel audits, aggregates results into single Linear task in Epic 0.
2026-01-21