woodpecker-cli
Reference for the Woodpecker CI command-line tool. Use when working with Woodpecker CI pipelines, managing repositories, secrets, registries, organizations, or users via the CLI. Covers pipeline operations (sta...
Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
Reference for the Woodpecker CI command-line tool. Use when working with Woodpecker CI pipelines, managing repositories, secrets, registries, organizations, or users via the CLI. Covers pipeline operations (sta...
Operate agentpack safely (doctor/update/preview/diff/deploy/status/explain/evolve/rollback). Prefer --json.
Operate agentpack safely in Claude Code. Use /ap-* commands for execution; prefer --json.
Contribute to Agentpack itself (spec-driven changes, tests, releases).
Example Codex skill from Agentpack minimal repo template.
Gather and clarify requirements before autonomous pipeline execution. Interactive phase for user input.
Deep code/plan review for architecture, subtle bugs, and test quality. Use after sonnet review for thorough analysis.
Start the multi-AI pipeline with TDD-driven ralph loop. Plan → Review → Implement (loop until tests pass + reviews approve).
Implement code using sonnet model with full main context access
Fast code/plan review for quality, security, and tests. Use for quick reviews before deeper analysis.
Final code/plan review using Codex. Use as the last review step after sonnet and opus.
When reading or writing pyproject.toml or .toml config files in Python. When editing TOML while preserving comments and formatting. When designing configuration file format for a Python tool. When code uses tom...
Reference guide for Claude Code skills system (January 2026). Use when creating, modifying, or understanding skills, SKILL.md format, frontmatter fields, hooks, context fork, or skill best practices.
Global contract for all specialist subagents. Enforces role boundaries, scope discipline, and DONE/BLOCKED status signaling. Load this skill in any agent that should operate as a bounded specialist following su...
The model must use this skill when : 1. working within any python project. 2. Python CLI applications with Typer and Rich are mentioned by the user. 2. tasked with Python script writing or editing. 3. building...
The model must invoke this skill when any trigger occurs - (1) user mentions "clang-format" or ".clang-format", (2) user requests analyzing code style/formatting patterns/conventions, (3) user requests creating...
When setting up automated code quality checks on git commit. When project has .pre-commit-config.yaml. When implementing git hooks for formatting, linting, or validation. When creating prepare-commit-msg hooks...
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating br...
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT,...
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-plat...
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurr...
Complete reference for Claude Code hooks system (January 2026). Use when creating hooks, understanding hook events, matchers, exit codes, JSON output control, environment variables, plugin hooks, or implementin...
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product...
Reference guide for Claude Code plugins system (January 2026). Use when creating, distributing, or understanding plugins, plugin.json schema, marketplace configuration, bundling skills/commands/agents/hooks/MCP...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.