Back to categories
Category

Agent Skills in category: Uncategorized

83262 skills match this category. Browse curated collections and explore related Agent Skills.

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches reviewing-code subagent to review implementation against plan or requirements before proceeding

samjhecht
samjhecht
41

researching-web-sources

Systematically researches topics using web search with source verification. Use when investigating unfamiliar technologies, gathering current information, or verifying technical claims.

samjhecht
samjhecht
41

reviewing-code

Conducts systematic code review with quality checks, architectural verification, and actionable feedback. Use when reviewing pull requests, code changes, or ensuring code quality standards.

samjhecht
samjhecht
41

running-tests

Executes test suites with proper error reporting and failure analysis. Use when verifying implementations, debugging test failures, or confirming test coverage.

samjhecht
samjhecht
41

running-workflows

Launches workflow engine runs in the background, monitors progress via session files, and reports status. Use when running spec-implementation workflows or any workflow engine invocation.

samjhecht
samjhecht
41

setting-up-git-hooks

Configures git hooks for automated testing, linting, and quality enforcement. Use when initializing projects, establishing quality gates, or preventing commit/push errors.

samjhecht
samjhecht
41

sharing-skills

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

samjhecht
samjhecht
41

testing-skills-with-subagents

DEPRECATED - Use writing-skills instead. This functionality has been consolidated into writing-skills which now contains both skill creation and testing methodology.

samjhecht
samjhecht
41

tracing-root-causes

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

samjhecht
samjhecht
41

updating-wrangler

Update the wrangler plugin to the latest version by clearing all caching layers. Use when user says "update yourself", "update wrangler", or after pushing changes to the wrangler repo.

samjhecht
samjhecht
41

updating-git-hooks

Updates existing git hook configurations for new requirements or tool changes. Use when hook requirements change, adding new quality checks, or modifying test commands.

samjhecht
samjhecht
41

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

samjhecht
samjhecht
41

validating-roadmaps

Validates roadmap completeness, phase coherence, and alignment with constitution. Use when creating roadmaps, reviewing planning documents, or ensuring strategic consistency.

samjhecht
samjhecht
41

verifying-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

samjhecht
samjhecht
41

verifying-governance

Validates governance file completeness, format compliance, and metric accuracy. Use when auditing governance health, after bulk changes, or ensuring documentation integrity.

samjhecht
samjhecht
41

writing-plans

Use when design is complete and you need detailed implementation tasks - creates tracked MCP issues with exact file paths, complete code examples, and verification steps. Optional reference plan file for architecture overview.

samjhecht
samjhecht
41

writing-skills

Creates and refines agent skills using TDD methodology with pressure testing and rationalization detection. Use when creating new skills, editing existing skills, testing skills with pressure scenarios, or verifying skills work before deployment.

samjhecht
samjhecht
41

writing-specifications

Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wrangler MCP issue management system with proper structure and completeness checks.

samjhecht
samjhecht
41

docusaurus-style

Provides comprehensive guidelines for writing and formatting MDX content, frontmatter, and Docusaurus-specific components for the Physical AI & Humanoid Robotics textbook.

uneezaismail
uneezaismail
2

exercise-patterns

Structure for creating hands-on exercises in the Physical AI textbook.

uneezaismail
uneezaismail
2

frontend-architect

Build production-grade UI/UX with React (Next.js, Docusaurus), CSS architecture (Tailwind, Modules, Global), animations, theming, performance optimization, state management, and testing. Use when creating React components, building layouts, refactoring CSS, implementing animations, auditing accessibility, optimizing performance, setting up state management, or writing component tests.

uneezaismail
uneezaismail
2

isaac-patterns

NVIDIA Isaac Sim and Isaac ROS integration patterns for Physical AI applications.

uneezaismail
uneezaismail
2

ros2-code-example-writer

Generate working Python/rclpy code examples for Physical AI & Humanoid Robotics textbook with tier-specific variants (Simulation/Jetson/Robot).

uneezaismail
uneezaismail
2

ros2-standards

Authoritative guidelines for writing production-grade ROS 2 (Humble) Python 3.11+ code (leveraging 3.12+ features where compatible) for Physical AI applications.

uneezaismail
uneezaismail
2

sim-to-real

Provides guidelines and principles for bridging the gap between simulated robotics environments and real-world hardware deployment in Physical AI.

uneezaismail
uneezaismail
2

vla-patterns

Vision-Language-Action model integration patterns for cognitive robotics with ROS 2.

uneezaismail
uneezaismail
2

building-apple-platform-products

Builds, tests, archives, and deploys Swift packages and Xcode projects for Apple platforms. Use when running xcodebuild, swift build, swift test, xcrun simctl, xcrun devicectl, or any xcrun developer tool. Covers project discovery, simulator management, physical device deployment, code signing, profiling, distribution, and binary inspection.

kylehughes
kylehughes
582

training-hub

Fine-tune LLMs using Red Hat training-hub library with SFT, LoRA, and OSFT algorithms. Use when preparing JSONL datasets, running training jobs, configuring hardware, scaling to clusters, evaluating models, or deploying with vLLM.

RobbieJ
RobbieJ
2

ailang-debug

Debug AILANG code errors. Use when you encounter type errors, parse errors, or runtime failures in AILANG programs.

sunholo-data
sunholo-data
3

ailang-inbox

Cross-agent communication system with semantic search and GitHub sync. Check messages, find similar content, deduplicate, and sync with GitHub Issues for AI workflows across sessions.

sunholo-data
sunholo-data
3

ailang

Write AILANG code. ALWAYS run 'ailang prompt' first - it contains the current syntax rules and templates.

sunholo-data
sunholo-data
3

design-doc-creator

Create AILANG design documents in the correct format and location. Use when user asks to create a design doc, plan a feature, or document a design. Handles both planned/ and implemented/ docs with proper structure.

sunholo-data
sunholo-data
3

sprint-executor

Execute approved sprint plans with test-driven development, continuous linting, progress tracking, and pause points. Supports parallel milestone execution via Task sub-agents. Use when user says "execute sprint", "start sprint", or wants to implement an approved sprint plan.

sunholo-data
sunholo-data
3

sprint-planner

Analyze design docs, calculate velocity from recent work, and create realistic sprint plans with day-by-day breakdowns. Use when user asks to "plan sprint", "create sprint plan", or wants to estimate development timeline.

sunholo-data
sunholo-data
3

website-builder

Build and refine websites from user briefs received via ailang messages. Use when the website-builder inbox has unread messages, or when the user asks to build/update a website.

sunholo-data
sunholo-data
3

architecture-case-study

Use when studying the architecture of an open-source codebase for the case-study series — "case study", "architecture study", "study how X is built", adding a subject under ~/devel/case-studies. Not for reviewing our own projects' code.

snits
snits
12

commit-decomposition

Use when breaking one or more oversized git commits into a series of logical commits — "decompose this commit", "break up this history", "atomic commits for this range". Lead-orchestrated - fresh subagent per patch, diff-parity gate, state file as cursor.

snits
snits
12

consulting-agents

Use when you need information you don't have, expertise outside your comfort zone, or a single fresh perspective on code — even if you think you already know the answer. Also triggered by "I'm not sure about", "what's the best approach", "second opinion", "research how X works", or any need for discovery, expertise, or review. For multi-perspective reviews where agents discuss and converge, use design-meeting instead. NOT for implementation delegation (see subagent-driven-development).

snits
snits
12

evidence-and-claims

Use when performing investigative work that produces reports or analysis for others to verify — root cause analysis, bug investigation, crash analysis, sosreport analysis, or any task making factual claims about system behavior. Also triggered by "investigate", "root cause", "analyze", "RCA", "figure out why", "what's causing", "track down", "write a report", "write up findings", "document what you found". Do NOT activate for quick lookups, code reviews, implementation tasks, or design work.

snits
snits
12

git-anchoring

Use before any git surgery — history rewriting, commit decomposition, rebase-heavy work, or any task that moves refs around. Establishes anchor refs, on-disk state, and worktree isolation so work cannot be orphaned and any fresh context can re-orient. Also use when recovering seemingly lost commits.

snits
snits
12

grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

snits
snits
12

interactive-rebase

Use when you need to amend a non-HEAD commit in git history without an interactive editor — automates rebase via fixup, autosquash, and GIT_SEQUENCE_EDITOR=true

snits
snits
12

project-insights

Generate a Claude Code usage-insights report for a single project by analyzing its session transcripts. Use when the user wants per-project insights, a session-history retrospective, "what have I been doing in this repo", or a homegrown/markdown version of the built-in /insights. Mirrors the built-in /insights pipeline (per-session facet extraction -> aggregate facets -> at-a-glance) but scoped to one project and emitting markdown.

snits
snits
12

retro

Use when Jerry asks for a retrospective, a weekly review, a summary of the past week's work, or "what kept getting in our way"; also when /wakey reports a retro is due.

snits
snits
12

sandbox-research

Run a research task in an isolated sandbox container with deterministic + semantic validation, retry-on-block (max 2 retries), and auto-archival to the research-vault. Use when the user asks to "research X with the sandbox", invokes /sandbox-research, or wants a structured research artifact rather than ad-hoc browsing.

snits
snits
12

stgit-stack-editing

Use when amending, reordering, or splitting commits in an in-progress patch series — especially fixing reviewer findings inside the offending commit instead of stacking fixup commits. Stacked Git (stg) alternative to interactive-rebase.

snits
snits
12

sync-devcontainer

Sync a project's .devcontainer/ files with the canonical template at ~/.claude/scratchpad/devcontainer-template/, or scaffold a new .devcontainer/ from the template. Triggers on /sync-devcontainer with optional arguments — no args (current project), <path> (specific project), or 'all' (sweep ~/devel/*).

snits
snits
12

using-claude-design

Use when creating or iterating on a design in a claude.ai/design project via the claude-design MCP server, before calling any mcp__claude-design__ tools.

snits
snits
12

writing-rubrics

Use when creating an evaluator or judge prompt for agent outputs — a rubric, scoring scheme, quality score, acceptance criteria for a generate-critique-revise loop, or a Workflow verify stage. Also use when an existing loop shows scores rising without real improvement, a judge growing lenient across iterations, or a request for "one overall score" or "give the judge the full conversation".

snits
snits
12

antiquities-extractor

Extract and structure data from documents about the illegal antiquities trade, including dealers, collectors, artifacts, locations, and relationships. Use when processing news reports, academic articles, legal documents, encyclopedia entries, or research materials pertaining to looted artifacts, antiquities trafficking, provenance research, or cultural heritage crimes. Returns structured JSON with entities (persons, organizations, artifacts, locations) and their relationships.

shawngraham
shawngraham
1

Page 1315 of 1666 · 83262 results