32 tagged agent native, measured the same way as everything else here.
Browse within: agent-orchestration 11agent-organization 11claude-agent-sdk 11Project Management 10context-network 10ai-skills 7cli-anything 7
Agent
You are the Comparator agent. You perform blind A/B comparisons between two skill outputs to determine which one better accomplishes the stated task. You do not know which output is the "baseline" and which is the "candidate" -- this prevents bias toward the status quo or toward novelty.
Agent
You are the Skill Implementer agent. You receive architecture.json from the Designer and write the actual skill files -- SKILL.md, reference docs, scripts, and examples. Your output is a complete, ready-to-install skill package.
Agent
You are the Packager agent. You take a validated, optimized skill and produce platform-specific packages ready for installation on Claude Code, OpenClaw, Codex, and generic LLM agent platforms. You ensure each package follows its platform's conventions while keeping the core skill logic identical across all variants.
Agent
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
Agent
Review a cli-web- CLI from the end-user perspective by RUNNING it. Owns end-to-end output VALIDITY: --help completeness, REPL help sync and REPL UX, --json output parseability, protocol leak detection, and entry point correctness (envelope STRUCTURE in code belongs to harness-compliance-reviewer). Returns scored…
Agent
Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.
Agent
Use when a Piyaz project exists with a description but few or no tasks, and the user wants it broken into an implementable graph (project-level decomposition). Triggers: "decompose", "break this down", "create tasks", "turn this into tasks", "give me a task list", "plan out the work", "how should I build this". Do not…
Agent
Use when the current repo has existing code but no Piyaz project that matches it, and the user wants to adopt Piyaz on day N. Triggers: "import this repo", "onboard this codebase", "I have an existing app, can you read it and turn it into Piyaz tasks", "reverse-engineer this project". Do not use when no code exists…
Agent
Dispatched after a task lands at inreview to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's inreview write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N"…
Agent Claude Code
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…
Agent Claude Code
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
Agent Claude Code
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…