Not in the top 1,000 by GitHub stars
tonone-ai/tonone
One session. Two commands. Full team. Zero meetings.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
bundle/engineering-team/skills/apex-plan/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/apex-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/apex-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/apex-status/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/apex-takeover/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-adr/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-changelog/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-map/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-onboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-present/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/atlas-report/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/cortex-eval/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/cortex-integrate/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/cortex-model/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/cortex-prompt/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/cortex-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-health/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-migrate/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-query/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/flux-schema/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-cost/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-diagnose/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-infra/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-network/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/forge-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/lens-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/lens-dashboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/lens-metrics/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/lens-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/lens-report/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/pave-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/pave-catalog/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/pave-env/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/pave-golden/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/pave-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/prism-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/prism-component/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/prism-dashboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/prism-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/prism-ui/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/proof-api/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/proof-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/proof-e2e/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/proof-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/proof-strategy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/relay-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/relay-deploy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/relay-docker/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/relay-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/relay-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-api/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-design/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-perf/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/spine-service/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/touch-app/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/touch-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/touch-feature/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/touch-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/touch-release/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/vigil-alert/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/vigil-check/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/vigil-incident/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/vigil-instrument/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/vigil-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/volt-driver/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/volt-firmware/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/volt-ota/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/volt-power/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/volt-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/warden-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/warden-harden/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/warden-iam/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/warden-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/engineering-team/skills/warden-threat/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/apex-plan/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/apex-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/apex-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/apex-status/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/apex-takeover/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-adr/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-changelog/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-map/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-onboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-present/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/atlas-report/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/buzz-community/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/buzz-launch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/buzz-pitch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/buzz-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/buzz-social/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/cortex-eval/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/cortex-integrate/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/cortex-model/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/cortex-prompt/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/cortex-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/crest-compete/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/crest-narrative/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/crest-okr/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/crest-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/crest-roadmap/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-close/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-playbook/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-pricing/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/deal-signals/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/draft-flow/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/draft-ia/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/draft-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/draft-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/draft-wireframe/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-feedback/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-interview/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-jobs/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-panel/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/echo-segment/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-health/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-migrate/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-query/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/flux-schema/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-cost/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-diagnose/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-infra/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-network/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/forge-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-brand/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-component/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-deck/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-email/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-logo/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-mobile/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-social/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-tokens/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/form-web/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/helm-arbiter/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/helm-brief/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/helm-handoff/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/helm-plan/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/helm-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/ink-calendar/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/ink-case/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/ink-post/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/ink-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/ink-seo/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/keep-expand/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/keep-health/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/keep-onboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/keep-playbook/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/keep-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lens-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lens-dashboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lens-metrics/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lens-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lens-report/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lumen-abtest/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lumen-funnel/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lumen-instrument/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lumen-metrics/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/lumen-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pave-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pave-catalog/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pave-env/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pave-golden/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pave-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pitch-copy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pitch-launch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pitch-message/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pitch-position/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/pitch-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/prism-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/prism-component/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/prism-dashboard/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/prism-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/prism-ui/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/proof-api/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/proof-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/proof-e2e/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/proof-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/proof-strategy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/relay-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/relay-deploy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/relay-docker/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/relay-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/relay-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-api/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-design/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-perf/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/spine-service/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/surge-activation/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/surge-experiment/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/surge-plg/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/surge-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/surge-retention/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/touch-app/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/touch-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/touch-feature/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/touch-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/touch-release/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/vigil-alert/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/vigil-check/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/vigil-incident/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/vigil-instrument/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/vigil-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/volt-driver/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/volt-firmware/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/volt-ota/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/volt-power/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/volt-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/warden-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/warden-harden/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/warden-iam/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/warden-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/full-team/skills/warden-threat/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-community/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-devrel/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-hn/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-launch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-outreach/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-pitch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/buzz-social/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-brief/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-calendar/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-case/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-cluster/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-distribute/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-links/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-local/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-post/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/ink-seo/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-copy/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-landing/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-launch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-message/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-position/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/marketing-team/skills/pitch-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/buzz-community/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/buzz-launch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/buzz-pitch/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/buzz-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/buzz-social/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/crest-compete/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/crest-narrative/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/crest-okr/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/crest-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/crest-roadmap/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-close/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-pipeline/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-playbook/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-pricing/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/deal-signals/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/draft-flow/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/draft-ia/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/draft-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/draft-review/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/draft-wireframe/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-feedback/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-interview/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-jobs/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-panel/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/echo-segment/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-audit/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-brand/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-component/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-deck/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-email/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-logo/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-mobile/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-social/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-tokens/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/form-web/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/helm-arbiter/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/helm-brief/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/helm-handoff/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/helm-plan/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/helm-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/ink-calendar/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/ink-case/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/ink-post/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/ink-recon/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/ink-seo/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/keep-expand/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
bundle/product-team/skills/keep-health/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 1ceec80367a4
No earlier version was observed for comparison.
Verified commit 1ceec80367a4e846e2f209cc87eea9d7544bd978
git clone --filter=blob:none --no-checkout https://github.com/tonone-ai/tonone.git .hotskills/tonone-ai-tonone && git -C .hotskills/tonone-ai-tonone checkout --detach 1ceec80367a4e846e2f209cc87eea9d7544bd978
# Copy each selected skill directory from .hotskills/tonone-ai-tonone into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/tonone-ai/tonone.git .hotskills/tonone-ai-tonone && git -C .hotskills/tonone-ai-tonone checkout --detach 1ceec80367a4e846e2f209cc87eea9d7544bd978
# Copy each selected skill directory from .hotskills/tonone-ai-tonone into .agents/skills/<skill-name>/Heat
1.2- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- apex-plan
bundle/engineering-team/skills/apex-plan - apex-recon
bundle/engineering-team/skills/apex-recon - apex-review
bundle/engineering-team/skills/apex-review - apex-status
bundle/engineering-team/skills/apex-status - apex-takeover
bundle/engineering-team/skills/apex-takeover - atlas-adr
bundle/engineering-team/skills/atlas-adr - atlas-changelog
bundle/engineering-team/skills/atlas-changelog - atlas-map
bundle/engineering-team/skills/atlas-map - atlas-onboard
bundle/engineering-team/skills/atlas-onboard - atlas-present
bundle/engineering-team/skills/atlas-present - atlas-recon
bundle/engineering-team/skills/atlas-recon - atlas-report
bundle/engineering-team/skills/atlas-report - cortex-eval
bundle/engineering-team/skills/cortex-eval - cortex-integrate
bundle/engineering-team/skills/cortex-integrate - cortex-model
bundle/engineering-team/skills/cortex-model - cortex-prompt
bundle/engineering-team/skills/cortex-prompt - cortex-recon
bundle/engineering-team/skills/cortex-recon - flux-health
bundle/engineering-team/skills/flux-health - flux-migrate
bundle/engineering-team/skills/flux-migrate - flux-pipeline
bundle/engineering-team/skills/flux-pipeline - flux-query
bundle/engineering-team/skills/flux-query - flux-recon
bundle/engineering-team/skills/flux-recon - flux-schema
bundle/engineering-team/skills/flux-schema - forge-audit
bundle/engineering-team/skills/forge-audit - forge-cost
bundle/engineering-team/skills/forge-cost - forge-diagnose
bundle/engineering-team/skills/forge-diagnose - forge-infra
bundle/engineering-team/skills/forge-infra - forge-network
bundle/engineering-team/skills/forge-network - forge-recon
bundle/engineering-team/skills/forge-recon - lens-audit
bundle/engineering-team/skills/lens-audit - lens-dashboard
bundle/engineering-team/skills/lens-dashboard - lens-metrics
bundle/engineering-team/skills/lens-metrics - lens-recon
bundle/engineering-team/skills/lens-recon - lens-report
bundle/engineering-team/skills/lens-report - pave-audit
bundle/engineering-team/skills/pave-audit - pave-catalog
bundle/engineering-team/skills/pave-catalog - pave-env
bundle/engineering-team/skills/pave-env - pave-golden
bundle/engineering-team/skills/pave-golden - pave-recon
bundle/engineering-team/skills/pave-recon - prism-audit
bundle/engineering-team/skills/prism-audit - prism-component
bundle/engineering-team/skills/prism-component - prism-dashboard
bundle/engineering-team/skills/prism-dashboard - prism-recon
bundle/engineering-team/skills/prism-recon - prism-ui
bundle/engineering-team/skills/prism-ui - proof-api
bundle/engineering-team/skills/proof-api - proof-audit
bundle/engineering-team/skills/proof-audit - proof-e2e
bundle/engineering-team/skills/proof-e2e - proof-recon
bundle/engineering-team/skills/proof-recon - proof-strategy
bundle/engineering-team/skills/proof-strategy - relay-audit
bundle/engineering-team/skills/relay-audit - relay-deploy
bundle/engineering-team/skills/relay-deploy - relay-docker
bundle/engineering-team/skills/relay-docker - relay-pipeline
bundle/engineering-team/skills/relay-pipeline - relay-recon
bundle/engineering-team/skills/relay-recon - spine-api
bundle/engineering-team/skills/spine-api - spine-design
bundle/engineering-team/skills/spine-design - spine-perf
bundle/engineering-team/skills/spine-perf - spine-recon
bundle/engineering-team/skills/spine-recon - spine-review
bundle/engineering-team/skills/spine-review - spine-service
bundle/engineering-team/skills/spine-service - touch-app
bundle/engineering-team/skills/touch-app - touch-audit
bundle/engineering-team/skills/touch-audit - touch-feature
bundle/engineering-team/skills/touch-feature - touch-recon
bundle/engineering-team/skills/touch-recon - touch-release
bundle/engineering-team/skills/touch-release - vigil-alert
bundle/engineering-team/skills/vigil-alert - vigil-check
bundle/engineering-team/skills/vigil-check - vigil-incident
bundle/engineering-team/skills/vigil-incident - vigil-instrument
bundle/engineering-team/skills/vigil-instrument - vigil-recon
bundle/engineering-team/skills/vigil-recon - volt-driver
bundle/engineering-team/skills/volt-driver - volt-firmware
bundle/engineering-team/skills/volt-firmware - volt-ota
bundle/engineering-team/skills/volt-ota - volt-power
bundle/engineering-team/skills/volt-power - volt-recon
bundle/engineering-team/skills/volt-recon - warden-audit
bundle/engineering-team/skills/warden-audit - warden-harden
bundle/engineering-team/skills/warden-harden - warden-iam
bundle/engineering-team/skills/warden-iam - warden-recon
bundle/engineering-team/skills/warden-recon - warden-threat
bundle/engineering-team/skills/warden-threat - apex-plan
bundle/full-team/skills/apex-plan - apex-recon
bundle/full-team/skills/apex-recon - apex-review
bundle/full-team/skills/apex-review - apex-status
bundle/full-team/skills/apex-status - apex-takeover
bundle/full-team/skills/apex-takeover - atlas-adr
bundle/full-team/skills/atlas-adr - atlas-changelog
bundle/full-team/skills/atlas-changelog - atlas-map
bundle/full-team/skills/atlas-map - atlas-onboard
bundle/full-team/skills/atlas-onboard - atlas-present
bundle/full-team/skills/atlas-present - atlas-recon
bundle/full-team/skills/atlas-recon - atlas-report
bundle/full-team/skills/atlas-report - buzz-community
bundle/full-team/skills/buzz-community - buzz-launch
bundle/full-team/skills/buzz-launch - buzz-pitch
bundle/full-team/skills/buzz-pitch - buzz-recon
bundle/full-team/skills/buzz-recon - buzz-social
bundle/full-team/skills/buzz-social - cortex-eval
bundle/full-team/skills/cortex-eval - cortex-integrate
bundle/full-team/skills/cortex-integrate - cortex-model
bundle/full-team/skills/cortex-model - cortex-prompt
bundle/full-team/skills/cortex-prompt - cortex-recon
bundle/full-team/skills/cortex-recon - crest-compete
bundle/full-team/skills/crest-compete - crest-narrative
bundle/full-team/skills/crest-narrative - crest-okr
bundle/full-team/skills/crest-okr - crest-recon
bundle/full-team/skills/crest-recon - crest-roadmap
bundle/full-team/skills/crest-roadmap - deal-close
bundle/full-team/skills/deal-close - deal-pipeline
bundle/full-team/skills/deal-pipeline - deal-playbook
bundle/full-team/skills/deal-playbook - deal-pricing
bundle/full-team/skills/deal-pricing - deal-recon
bundle/full-team/skills/deal-recon - deal-signals
bundle/full-team/skills/deal-signals - draft-flow
bundle/full-team/skills/draft-flow - draft-ia
bundle/full-team/skills/draft-ia - draft-recon
bundle/full-team/skills/draft-recon - draft-review
bundle/full-team/skills/draft-review - draft-wireframe
bundle/full-team/skills/draft-wireframe - echo-feedback
bundle/full-team/skills/echo-feedback - echo-interview
bundle/full-team/skills/echo-interview - echo-jobs
bundle/full-team/skills/echo-jobs - echo-panel
bundle/full-team/skills/echo-panel - echo-recon
bundle/full-team/skills/echo-recon - echo-segment
bundle/full-team/skills/echo-segment - flux-health
bundle/full-team/skills/flux-health - flux-migrate
bundle/full-team/skills/flux-migrate - flux-pipeline
bundle/full-team/skills/flux-pipeline - flux-query
bundle/full-team/skills/flux-query - flux-recon
bundle/full-team/skills/flux-recon - flux-schema
bundle/full-team/skills/flux-schema - forge-audit
bundle/full-team/skills/forge-audit - forge-cost
bundle/full-team/skills/forge-cost - forge-diagnose
bundle/full-team/skills/forge-diagnose - forge-infra
bundle/full-team/skills/forge-infra - forge-network
bundle/full-team/skills/forge-network - forge-recon
bundle/full-team/skills/forge-recon - form-audit
bundle/full-team/skills/form-audit - form-brand
bundle/full-team/skills/form-brand - form-component
bundle/full-team/skills/form-component - form-deck
bundle/full-team/skills/form-deck - form-email
bundle/full-team/skills/form-email - form-logo
bundle/full-team/skills/form-logo - form-mobile
bundle/full-team/skills/form-mobile - form-social
bundle/full-team/skills/form-social - form-tokens
bundle/full-team/skills/form-tokens - form-web
bundle/full-team/skills/form-web - helm-arbiter
bundle/full-team/skills/helm-arbiter - helm-brief
bundle/full-team/skills/helm-brief - helm-handoff
bundle/full-team/skills/helm-handoff - helm-plan
bundle/full-team/skills/helm-plan - helm-recon
bundle/full-team/skills/helm-recon - ink-calendar
bundle/full-team/skills/ink-calendar - ink-case
bundle/full-team/skills/ink-case - ink-post
bundle/full-team/skills/ink-post - ink-recon
bundle/full-team/skills/ink-recon - ink-seo
bundle/full-team/skills/ink-seo - keep-expand
bundle/full-team/skills/keep-expand - keep-health
bundle/full-team/skills/keep-health - keep-onboard
bundle/full-team/skills/keep-onboard - keep-playbook
bundle/full-team/skills/keep-playbook - keep-recon
bundle/full-team/skills/keep-recon - lens-audit
bundle/full-team/skills/lens-audit - lens-dashboard
bundle/full-team/skills/lens-dashboard - lens-metrics
bundle/full-team/skills/lens-metrics - lens-recon
bundle/full-team/skills/lens-recon - lens-report
bundle/full-team/skills/lens-report - lumen-abtest
bundle/full-team/skills/lumen-abtest - lumen-funnel
bundle/full-team/skills/lumen-funnel - lumen-instrument
bundle/full-team/skills/lumen-instrument - lumen-metrics
bundle/full-team/skills/lumen-metrics - lumen-recon
bundle/full-team/skills/lumen-recon - pave-audit
bundle/full-team/skills/pave-audit - pave-catalog
bundle/full-team/skills/pave-catalog - pave-env
bundle/full-team/skills/pave-env - pave-golden
bundle/full-team/skills/pave-golden - pave-recon
bundle/full-team/skills/pave-recon - pitch-copy
bundle/full-team/skills/pitch-copy - pitch-launch
bundle/full-team/skills/pitch-launch - pitch-message
bundle/full-team/skills/pitch-message - pitch-position
bundle/full-team/skills/pitch-position - pitch-recon
bundle/full-team/skills/pitch-recon - prism-audit
bundle/full-team/skills/prism-audit - prism-component
bundle/full-team/skills/prism-component - prism-dashboard
bundle/full-team/skills/prism-dashboard - prism-recon
bundle/full-team/skills/prism-recon - prism-ui
bundle/full-team/skills/prism-ui - proof-api
bundle/full-team/skills/proof-api - proof-audit
bundle/full-team/skills/proof-audit - proof-e2e
bundle/full-team/skills/proof-e2e - proof-recon
bundle/full-team/skills/proof-recon - proof-strategy
bundle/full-team/skills/proof-strategy - relay-audit
bundle/full-team/skills/relay-audit - relay-deploy
bundle/full-team/skills/relay-deploy - relay-docker
bundle/full-team/skills/relay-docker - relay-pipeline
bundle/full-team/skills/relay-pipeline - relay-recon
bundle/full-team/skills/relay-recon - spine-api
bundle/full-team/skills/spine-api - spine-design
bundle/full-team/skills/spine-design - spine-perf
bundle/full-team/skills/spine-perf - spine-recon
bundle/full-team/skills/spine-recon - spine-review
bundle/full-team/skills/spine-review - spine-service
bundle/full-team/skills/spine-service - surge-activation
bundle/full-team/skills/surge-activation - surge-experiment
bundle/full-team/skills/surge-experiment - surge-plg
bundle/full-team/skills/surge-plg - surge-recon
bundle/full-team/skills/surge-recon - surge-retention
bundle/full-team/skills/surge-retention - touch-app
bundle/full-team/skills/touch-app - touch-audit
bundle/full-team/skills/touch-audit - touch-feature
bundle/full-team/skills/touch-feature - touch-recon
bundle/full-team/skills/touch-recon - touch-release
bundle/full-team/skills/touch-release - vigil-alert
bundle/full-team/skills/vigil-alert - vigil-check
bundle/full-team/skills/vigil-check - vigil-incident
bundle/full-team/skills/vigil-incident - vigil-instrument
bundle/full-team/skills/vigil-instrument - vigil-recon
bundle/full-team/skills/vigil-recon - volt-driver
bundle/full-team/skills/volt-driver - volt-firmware
bundle/full-team/skills/volt-firmware - volt-ota
bundle/full-team/skills/volt-ota - volt-power
bundle/full-team/skills/volt-power - volt-recon
bundle/full-team/skills/volt-recon - warden-audit
bundle/full-team/skills/warden-audit - warden-harden
bundle/full-team/skills/warden-harden - warden-iam
bundle/full-team/skills/warden-iam - warden-recon
bundle/full-team/skills/warden-recon - warden-threat
bundle/full-team/skills/warden-threat - buzz-community
bundle/marketing-team/skills/buzz-community - buzz-devrel
bundle/marketing-team/skills/buzz-devrel - buzz-hn
bundle/marketing-team/skills/buzz-hn - buzz-launch
bundle/marketing-team/skills/buzz-launch - buzz-outreach
bundle/marketing-team/skills/buzz-outreach - buzz-pitch
bundle/marketing-team/skills/buzz-pitch - buzz-recon
bundle/marketing-team/skills/buzz-recon - buzz-social
bundle/marketing-team/skills/buzz-social - ink-brief
bundle/marketing-team/skills/ink-brief - ink-calendar
bundle/marketing-team/skills/ink-calendar - ink-case
bundle/marketing-team/skills/ink-case - ink-cluster
bundle/marketing-team/skills/ink-cluster - ink-distribute
bundle/marketing-team/skills/ink-distribute - ink-links
bundle/marketing-team/skills/ink-links - ink-local
bundle/marketing-team/skills/ink-local - ink-post
bundle/marketing-team/skills/ink-post - ink-recon
bundle/marketing-team/skills/ink-recon - ink-seo
bundle/marketing-team/skills/ink-seo - pitch-copy
bundle/marketing-team/skills/pitch-copy - pitch-landing
bundle/marketing-team/skills/pitch-landing - pitch-launch
bundle/marketing-team/skills/pitch-launch - pitch-message
bundle/marketing-team/skills/pitch-message - pitch-position
bundle/marketing-team/skills/pitch-position - pitch-recon
bundle/marketing-team/skills/pitch-recon - buzz-community
bundle/product-team/skills/buzz-community - buzz-launch
bundle/product-team/skills/buzz-launch - buzz-pitch
bundle/product-team/skills/buzz-pitch - buzz-recon
bundle/product-team/skills/buzz-recon - buzz-social
bundle/product-team/skills/buzz-social - crest-compete
bundle/product-team/skills/crest-compete - crest-narrative
bundle/product-team/skills/crest-narrative - crest-okr
bundle/product-team/skills/crest-okr - crest-recon
bundle/product-team/skills/crest-recon - crest-roadmap
bundle/product-team/skills/crest-roadmap - deal-close
bundle/product-team/skills/deal-close - deal-pipeline
bundle/product-team/skills/deal-pipeline - deal-playbook
bundle/product-team/skills/deal-playbook - deal-pricing
bundle/product-team/skills/deal-pricing - deal-recon
bundle/product-team/skills/deal-recon - deal-signals
bundle/product-team/skills/deal-signals - draft-flow
bundle/product-team/skills/draft-flow - draft-ia
bundle/product-team/skills/draft-ia - draft-recon
bundle/product-team/skills/draft-recon - draft-review
bundle/product-team/skills/draft-review - draft-wireframe
bundle/product-team/skills/draft-wireframe - echo-feedback
bundle/product-team/skills/echo-feedback - echo-interview
bundle/product-team/skills/echo-interview - echo-jobs
bundle/product-team/skills/echo-jobs - echo-panel
bundle/product-team/skills/echo-panel - echo-recon
bundle/product-team/skills/echo-recon - echo-segment
bundle/product-team/skills/echo-segment - form-audit
bundle/product-team/skills/form-audit - form-brand
bundle/product-team/skills/form-brand - form-component
bundle/product-team/skills/form-component - form-deck
bundle/product-team/skills/form-deck - form-email
bundle/product-team/skills/form-email - form-logo
bundle/product-team/skills/form-logo - form-mobile
bundle/product-team/skills/form-mobile - form-social
bundle/product-team/skills/form-social - form-tokens
bundle/product-team/skills/form-tokens - form-web
bundle/product-team/skills/form-web - helm-arbiter
bundle/product-team/skills/helm-arbiter - helm-brief
bundle/product-team/skills/helm-brief - helm-handoff
bundle/product-team/skills/helm-handoff - helm-plan
bundle/product-team/skills/helm-plan - helm-recon
bundle/product-team/skills/helm-recon - ink-calendar
bundle/product-team/skills/ink-calendar - ink-case
bundle/product-team/skills/ink-case - ink-post
bundle/product-team/skills/ink-post - ink-recon
bundle/product-team/skills/ink-recon - ink-seo
bundle/product-team/skills/ink-seo - keep-expand
bundle/product-team/skills/keep-expand - keep-health
bundle/product-team/skills/keep-health - keep-onboard
bundle/product-team/skills/keep-onboard - keep-playbook
bundle/product-team/skills/keep-playbook - keep-recon
bundle/product-team/skills/keep-recon - lumen-abtest
bundle/product-team/skills/lumen-abtest - lumen-funnel
bundle/product-team/skills/lumen-funnel - lumen-instrument
bundle/product-team/skills/lumen-instrument - lumen-metrics
bundle/product-team/skills/lumen-metrics - lumen-recon
bundle/product-team/skills/lumen-recon - pitch-copy
bundle/product-team/skills/pitch-copy - pitch-launch
bundle/product-team/skills/pitch-launch - pitch-message
bundle/product-team/skills/pitch-message - pitch-position
bundle/product-team/skills/pitch-position - pitch-recon
bundle/product-team/skills/pitch-recon - surge-activation
bundle/product-team/skills/surge-activation - surge-experiment
bundle/product-team/skills/surge-experiment - surge-plg
bundle/product-team/skills/surge-plg - surge-recon
bundle/product-team/skills/surge-recon - surge-retention
bundle/product-team/skills/surge-retention - deal-close
bundle/revenue-team/skills/deal-close - deal-outreach
bundle/revenue-team/skills/deal-outreach - deal-pipeline
bundle/revenue-team/skills/deal-pipeline - deal-playbook
bundle/revenue-team/skills/deal-playbook - deal-pricing
bundle/revenue-team/skills/deal-pricing - deal-proposal
bundle/revenue-team/skills/deal-proposal - deal-qualify
bundle/revenue-team/skills/deal-qualify - deal-recon
bundle/revenue-team/skills/deal-recon - deal-signals
bundle/revenue-team/skills/deal-signals - keep-churn
bundle/revenue-team/skills/keep-churn - keep-expand
bundle/revenue-team/skills/keep-expand - keep-health
bundle/revenue-team/skills/keep-health - keep-onboard
bundle/revenue-team/skills/keep-onboard - keep-playbook
bundle/revenue-team/skills/keep-playbook - keep-qbr
bundle/revenue-team/skills/keep-qbr - keep-recon
bundle/revenue-team/skills/keep-recon - keep-segment
bundle/revenue-team/skills/keep-segment - surge-activation
bundle/revenue-team/skills/surge-activation - surge-experiment
bundle/revenue-team/skills/surge-experiment - surge-landing
bundle/revenue-team/skills/surge-landing - surge-plg
bundle/revenue-team/skills/surge-plg - surge-recon
bundle/revenue-team/skills/surge-recon - surge-retention
bundle/revenue-team/skills/surge-retention - apex-plan
bundle/tonone-core/skills/apex-plan - apex-recon
bundle/tonone-core/skills/apex-recon - apex-review
bundle/tonone-core/skills/apex-review - apex-status
bundle/tonone-core/skills/apex-status - apex-takeover
bundle/tonone-core/skills/apex-takeover - atlas-adr
bundle/tonone-core/skills/atlas-adr - atlas-changelog
bundle/tonone-core/skills/atlas-changelog - atlas-map
bundle/tonone-core/skills/atlas-map - atlas-onboard
bundle/tonone-core/skills/atlas-onboard - atlas-present
bundle/tonone-core/skills/atlas-present - atlas-recon
bundle/tonone-core/skills/atlas-recon - atlas-report
bundle/tonone-core/skills/atlas-report - cortex-eval
bundle/tonone-core/skills/cortex-eval - cortex-integrate
bundle/tonone-core/skills/cortex-integrate - cortex-model
bundle/tonone-core/skills/cortex-model - cortex-prompt
bundle/tonone-core/skills/cortex-prompt - cortex-recon
bundle/tonone-core/skills/cortex-recon - flux-health
bundle/tonone-core/skills/flux-health - flux-migrate
bundle/tonone-core/skills/flux-migrate - flux-pipeline
bundle/tonone-core/skills/flux-pipeline - flux-query
bundle/tonone-core/skills/flux-query - flux-recon
bundle/tonone-core/skills/flux-recon - flux-schema
bundle/tonone-core/skills/flux-schema - forge-audit
bundle/tonone-core/skills/forge-audit - forge-cost
bundle/tonone-core/skills/forge-cost - forge-diagnose
bundle/tonone-core/skills/forge-diagnose - forge-infra
bundle/tonone-core/skills/forge-infra - forge-network
bundle/tonone-core/skills/forge-network - forge-recon
bundle/tonone-core/skills/forge-recon - lens-audit
bundle/tonone-core/skills/lens-audit - lens-dashboard
bundle/tonone-core/skills/lens-dashboard - lens-metrics
bundle/tonone-core/skills/lens-metrics - lens-recon
bundle/tonone-core/skills/lens-recon - lens-report
bundle/tonone-core/skills/lens-report - pave-audit
bundle/tonone-core/skills/pave-audit - pave-catalog
bundle/tonone-core/skills/pave-catalog - pave-env
bundle/tonone-core/skills/pave-env - pave-golden
bundle/tonone-core/skills/pave-golden - pave-recon
bundle/tonone-core/skills/pave-recon - prism-audit
bundle/tonone-core/skills/prism-audit - prism-component
bundle/tonone-core/skills/prism-component - prism-dashboard
bundle/tonone-core/skills/prism-dashboard - prism-recon
bundle/tonone-core/skills/prism-recon - prism-ui
bundle/tonone-core/skills/prism-ui - proof-api
bundle/tonone-core/skills/proof-api - proof-audit
bundle/tonone-core/skills/proof-audit - proof-e2e
bundle/tonone-core/skills/proof-e2e - proof-recon
bundle/tonone-core/skills/proof-recon - proof-strategy
bundle/tonone-core/skills/proof-strategy - relay-audit
bundle/tonone-core/skills/relay-audit - relay-deploy
bundle/tonone-core/skills/relay-deploy - relay-docker
bundle/tonone-core/skills/relay-docker - relay-pipeline
bundle/tonone-core/skills/relay-pipeline - relay-recon
bundle/tonone-core/skills/relay-recon - spine-api
bundle/tonone-core/skills/spine-api - spine-design
bundle/tonone-core/skills/spine-design - spine-perf
bundle/tonone-core/skills/spine-perf - spine-recon
bundle/tonone-core/skills/spine-recon - spine-review
bundle/tonone-core/skills/spine-review - spine-service
bundle/tonone-core/skills/spine-service - touch-app
bundle/tonone-core/skills/touch-app - touch-audit
bundle/tonone-core/skills/touch-audit - touch-feature
bundle/tonone-core/skills/touch-feature - touch-recon
bundle/tonone-core/skills/touch-recon - touch-release
bundle/tonone-core/skills/touch-release - vigil-alert
bundle/tonone-core/skills/vigil-alert - vigil-check
bundle/tonone-core/skills/vigil-check - vigil-incident
bundle/tonone-core/skills/vigil-incident - vigil-instrument
bundle/tonone-core/skills/vigil-instrument - vigil-recon
bundle/tonone-core/skills/vigil-recon - volt-driver
bundle/tonone-core/skills/volt-driver - volt-firmware
bundle/tonone-core/skills/volt-firmware - volt-ota
bundle/tonone-core/skills/volt-ota - volt-power
bundle/tonone-core/skills/volt-power - volt-recon
bundle/tonone-core/skills/volt-recon - warden-audit
bundle/tonone-core/skills/warden-audit - warden-harden
bundle/tonone-core/skills/warden-harden - warden-iam
bundle/tonone-core/skills/warden-iam - warden-recon
bundle/tonone-core/skills/warden-recon - warden-threat
bundle/tonone-core/skills/warden-threat - apex
skills/apex - apex-diagnose
skills/apex-diagnose - apex-gate
skills/apex-gate - apex-plan
skills/apex-plan - apex-profile
skills/apex-profile - apex-recon
skills/apex-recon - apex-review
skills/apex-review - apex-route
skills/apex-route - apex-stats
skills/apex-stats - apex-status
skills/apex-status - apex-takeover
skills/apex-takeover - atlas
skills/atlas - atlas-adr
skills/atlas-adr - atlas-changelog
skills/atlas-changelog - atlas-map
skills/atlas-map - atlas-onboard
skills/atlas-onboard - atlas-present
skills/atlas-present - atlas-recon
skills/atlas-recon - atlas-report
skills/atlas-report - audit-controls
skills/audit-controls - audit-legal
skills/audit-legal - audit-recon
skills/audit-recon - axe-audit
skills/axe-audit - axe-fix
skills/axe-fix - axe-recon
skills/axe-recon - bench-compare
skills/bench-compare - bench-profile
skills/bench-profile - bench-recon
skills/bench-recon - bind-gap
skills/bind-gap - bind-policy
skills/bind-policy - bind-recon
skills/bind-recon - blue-detect
skills/blue-detect - blue-harden
skills/blue-harden - blue-recon
skills/blue-recon - brace-escalate
skills/brace-escalate - brace-kb
skills/brace-kb - brace-metrics
skills/brace-metrics - brace-onboard
skills/brace-onboard - brace-playbook
skills/brace-playbook - brace-recon
skills/brace-recon - brace-sla
skills/brace-sla - brace-triage
skills/brace-triage - brief-draft
skills/brief-draft - brief-recon
skills/brief-recon - brief-review
skills/brief-review - budget-audit
skills/budget-audit - budget-optimize
skills/budget-optimize - budget-recon
skills/budget-recon - buzz
skills/buzz - buzz-community
skills/buzz-community - buzz-devrel
skills/buzz-devrel - buzz-hn
skills/buzz-hn - buzz-launch
skills/buzz-launch - buzz-outreach
skills/buzz-outreach - buzz-pitch
skills/buzz-pitch - buzz-recon
skills/buzz-recon - buzz-social
skills/buzz-social - cache-design
skills/cache-design - cache-evict
skills/cache-evict - cache-recon
skills/cache-recon - cast-forecast
skills/cast-forecast - cast-recon
skills/cast-recon - cast-validate
skills/cast-validate - chain-recon
skills/chain-recon - chain-sbom
skills/chain-sbom - chain-scan
skills/chain-scan - change-policy
skills/change-policy - change-recon
skills/change-recon - change-write
skills/change-write - chaos-design
skills/chaos-design - chaos-game
skills/chaos-game - chaos-recon
skills/chaos-recon - cite-compare
skills/cite-compare - cite-recon
skills/cite-recon - cite-research
skills/cite-research - clause-analyze
skills/clause-analyze - clause-playbook
skills/clause-playbook - clause-recon
skills/clause-recon - clean-recon
skills/clean-recon - clean-transform
skills/clean-transform - clean-validate
skills/clean-validate - compat-audit
skills/compat-audit - compat-policy
skills/compat-policy - compat-recon
skills/compat-recon - copy-audit
skills/copy-audit - copy-recon
skills/copy-recon - copy-write
skills/copy-write - cortex
skills/cortex - cortex-eval
skills/cortex-eval - cortex-integrate
skills/cortex-integrate - cortex-model
skills/cortex-model - cortex-prompt
skills/cortex-prompt - cortex-recon
skills/cortex-recon - crest
skills/crest - crest-compete
skills/crest-compete - crest-narrative
skills/crest-narrative - crest-okr
skills/crest-okr - crest-recon
skills/crest-recon - crest-roadmap
skills/crest-roadmap - cut-icon
skills/cut-icon - cut-illustrate
skills/cut-illustrate - cut-recon
skills/cut-recon - deal
skills/deal - deal-close
skills/deal-close - deal-outreach
skills/deal-outreach - deal-pipeline
skills/deal-pipeline - deal-playbook
skills/deal-playbook - deal-pricing
skills/deal-pricing - deal-proposal
skills/deal-proposal - deal-qualify
skills/deal-qualify - deal-recon
skills/deal-recon - deal-signals
skills/deal-signals - deploy-canary
skills/deploy-canary - deploy-recon
skills/deploy-recon - deploy-serve
skills/deploy-serve - draft
skills/draft - draft-flow
skills/draft-flow - draft-ia
skills/draft-ia - draft-landing
skills/draft-landing - draft-patterns
skills/draft-patterns - draft-proto
skills/draft-proto - draft-recon
skills/draft-recon - draft-review
skills/draft-review - draft-wireframe
skills/draft-wireframe - drift-alert
skills/drift-alert - drift-monitor
skills/drift-monitor - drift-recon
skills/drift-recon - echo
skills/echo - echo-feedback
skills/echo-feedback - echo-interview
skills/echo-interview - echo-jobs
skills/echo-jobs - echo-panel
skills/echo-panel - echo-recon
skills/echo-recon - echo-segment
skills/echo-segment - edge-cdn
skills/edge-cdn - edge-recon
skills/edge-recon - edge-route
skills/edge-route - embed-design
skills/embed-design - embed-recon
skills/embed-recon - embed-search
skills/embed-search - eval-analyze
skills/eval-analyze - eval-design
skills/eval-design - eval-recon
skills/eval-recon - evals-analyze
skills/evals-analyze - evals-design
skills/evals-design - evals-harness
skills/evals-harness - evals-recon
skills/evals-recon - evals-regress
skills/evals-regress - feat-engineer
skills/feat-engineer - feat-recon
skills/feat-recon - feat-store
skills/feat-store - finop-audit
skills/finop-audit - finop-recon
skills/finop-recon - finop-reserve
skills/finop-reserve - fit-recon
skills/fit-recon - fit-train
skills/fit-train - fit-tune
skills/fit-tune - flux
skills/flux - flux-health
skills/flux-health - flux-migrate
skills/flux-migrate - flux-pipeline
skills/flux-pipeline - flux-query
skills/flux-query - flux-recon
skills/flux-recon - flux-schema
skills/flux-schema - folk-comp
skills/folk-comp - folk-culture
skills/folk-culture - folk-hire
skills/folk-hire - folk-migrate
skills/folk-migrate - folk-onboard
skills/folk-onboard - folk-org
skills/folk-org - folk-perf
skills/folk-perf - folk-recon
skills/folk-recon - forge
skills/forge - forge-audit
skills/forge-audit - forge-cost
skills/forge-cost - forge-diagnose
skills/forge-diagnose - forge-infra
skills/forge-infra - forge-network
skills/forge-network - forge-recon
skills/forge-recon - form
skills/form - form-animate
skills/form-animate - form-audit
skills/form-audit - form-brand
skills/form-brand - form-brief
skills/form-brief - form-component
skills/form-component - form-critique
skills/form-critique - form-deck
skills/form-deck - form-direction
skills/form-direction - form-email
skills/form-email - form-exam
skills/form-exam - form-logo
skills/form-logo - form-mobile
skills/form-mobile - form-palette
skills/form-palette - form-social
skills/form-social - form-style
skills/form-style - form-tokens
skills/form-tokens - form-web
skills/form-web - frame-board
skills/frame-board - frame-equity
skills/frame-equity - frame-recon
skills/frame-recon - gate-ci
skills/gate-ci - gate-lint
skills/gate-lint - gate-recon
skills/gate-recon - glyph-pair
skills/glyph-pair - glyph-recon
skills/glyph-recon - glyph-scale
skills/glyph-scale - grid-layout
skills/grid-layout - grid-recon
skills/grid-recon - grid-responsive
skills/grid-responsive - guard-audit
skills/guard-audit - guard-design
skills/guard-design - guard-recon
skills/guard-recon - guide-audit
skills/guide-audit - guide-recon
skills/guide-recon - guide-write
skills/guide-write - helm
skills/helm - helm-arbiter
skills/helm-arbiter - helm-brief
skills/helm-brief - helm-handoff
skills/helm-handoff - helm-plan
skills/helm-plan - helm-recon
skills/helm-recon - hue-palette
skills/hue-palette - hue-recon
skills/hue-recon - hue-token
skills/hue-token - hunt-assess
skills/hunt-assess - hunt-ioc
skills/hunt-ioc - hunt-recon
skills/hunt-recon - ink
skills/ink - ink-brief
skills/ink-brief - ink-calendar
skills/ink-calendar - ink-case
skills/ink-case - ink-cluster
skills/ink-cluster - ink-distribute
skills/ink-distribute - ink-links
skills/ink-links - ink-local
skills/ink-local - ink-post
skills/ink-post - ink-recon
skills/ink-recon - ink-seo
skills/ink-seo - keel-audit
skills/keel-audit - keel-cadence
skills/keel-cadence - keel-comply
skills/keel-comply - keel-legal
skills/keel-legal - keel-okr
skills/keel-okr - keel-process
skills/keel-process - keel-recon
skills/keel-recon - keel-vendor
skills/keel-vendor - keep
skills/keep - keep-churn
skills/keep-churn - keep-expand
skills/keep-expand - keep-health
skills/keep-health - keep-onboard
skills/keep-onboard - keep-playbook
skills/keep-playbook - keep-qbr
skills/keep-qbr - keep-recon
skills/keep-recon - keep-segment
skills/keep-segment - kube-design
skills/kube-design - kube-rbac
skills/kube-rbac - kube-recon
skills/kube-recon - lens
skills/lens - lens-audit
skills/lens-audit - lens-chart
skills/lens-chart - lens-dashboard
skills/lens-dashboard - lens-metrics
skills/lens-metrics - lens-recon
skills/lens-recon - lens-report
skills/lens-report - lodge-dmca
skills/lodge-dmca - lodge-filing
skills/lodge-filing - lodge-recon
skills/lodge-recon - lumen
skills/lumen - lumen-abtest
skills/lumen-abtest - lumen-funnel
skills/lumen-funnel - lumen-instrument
skills/lumen-instrument - lumen-metrics
skills/lumen-metrics - lumen-recon
skills/lumen-recon - mark-asset
skills/mark-asset - mark-brand
skills/mark-brand - mark-recon
skills/mark-recon - mesh-design
skills/mesh-design - mesh-observe
skills/mesh-observe - mesh-recon
skills/mesh-recon - mint-board
skills/mint-board - mint-budget
skills/mint-budget - mint-model
skills/mint-model - mint-raise
skills/mint-raise - mint-recon
skills/mint-recon - mint-report
skills/mint-report - mint-runway
skills/mint-runway - mint-unit
skills/mint-unit - mock-contract
skills/mock-contract - mock-design
skills/mock-design - mock-recon
skills/mock-recon - move-animate
skills/move-animate - move-recon
skills/move-recon - move-system
skills/move-system - multi-design
skills/multi-design - multi-port
skills/multi-port - multi-recon
skills/multi-recon - onboard-audit
skills/onboard-audit - onboard-quickstart
skills/onboard-quickstart - onboard-recon
skills/onboard-recon - patch-plan
skills/patch-plan - patch-recon
skills/patch-recon - patch-triage
skills/patch-triage - pave
skills/pave - pave-audit
skills/pave-audit - pave-catalog
skills/pave-catalog - pave-contribute
skills/pave-contribute - pave-env
skills/pave-env - pave-golden
skills/pave-golden - pave-lsp
skills/pave-lsp - pave-recon
skills/pave-recon - phish-assess
skills/phish-assess - phish-recon
skills/phish-recon - phish-train
skills/phish-train - pitch
skills/pitch - pitch-copy
skills/pitch-copy - pitch-landing
skills/pitch-landing - pitch-launch
skills/pitch-launch - pitch-message
skills/pitch-message - pitch-position
skills/pitch-position - pitch-recon
skills/pitch-recon - plot-chart
skills/plot-chart - plot-eda
skills/plot-eda - plot-recon
skills/plot-recon - port-design
skills/port-design - port-recon
skills/port-recon - port-review
skills/port-review - prism
skills/prism - prism-audit
skills/prism-audit - prism-chart
skills/prism-chart - prism-component
skills/prism-component - prism-dashboard
skills/prism-dashboard - prism-recon
skills/prism-recon - prism-stack
skills/prism-stack - prism-ui
skills/prism-ui - prompt-design
skills/prompt-design - prompt-recon
skills/prompt-recon - prompt-version
skills/prompt-version - proof
skills/proof - proof-api
skills/proof-api - proof-audit
skills/proof-audit - proof-design
skills/proof-design - proof-e2e
skills/proof-e2e - proof-explore
skills/proof-explore - proof-recon
skills/proof-recon - proof-strategy
skills/proof-strategy - queue-design
skills/queue-design - queue-recon
skills/queue-recon - queue-scale
skills/queue-scale - rank-design
skills/rank-design - rank-eval
skills/rank-eval - rank-recon
skills/rank-recon - red-pentest
skills/red-pentest - red-recon
skills/red-recon - red-report
skills/red-report - relay
skills/relay - relay-audit
skills/relay-audit - relay-deploy
skills/relay-deploy - relay-docker
skills/relay-docker - relay-pipeline
skills/relay-pipeline - relay-recon
skills/relay-recon - relay-ship
skills/relay-ship - resp-contain
skills/resp-contain - resp-playbook
skills/resp-playbook - resp-recon
skills/resp-recon - sample-recon
skills/sample-recon - sample-review
skills/sample-review - sample-write
skills/sample-write - sast-fix
skills/sast-fix - sast-recon
skills/sast-recon - sast-scan
skills/sast-scan - schema-design
skills/schema-design - schema-recon
skills/schema-recon - schema-review
skills/schema-review - scope-oss
skills/scope-oss - scope-recon
skills/scope-recon - scope-trademark
skills/scope-trademark - score-compare
skills/score-compare - score-eval
skills/score-eval - score-recon
skills/score-recon - serv-cold
skills/serv-cold - serv-design
skills/serv-design - serv-recon
skills/serv-recon - shield-assess
skills/shield-assess - shield-recon
skills/shield-recon - shield-respond
skills/shield-respond - siem-alert
skills/siem-alert - siem-recon
skills/siem-recon - siem-rule
skills/siem-rule - spine
skills/spine - spine-api
skills/spine-api - spine-design
skills/spine-design - spine-perf
skills/spine-perf - spine-recon
skills/spine-recon - spine-review
skills/spine-review - spine-service
skills/spine-service - spine-simplify
skills/spine-simplify - surge
skills/surge - surge-activation
skills/surge-activation - surge-experiment
skills/surge-experiment - surge-landing
skills/surge-landing - surge-plg
skills/surge-plg - surge-recon
skills/surge-recon - surge-retention
skills/surge-retention - terms-privacy
skills/terms-privacy - terms-recon
skills/terms-recon - terms-tos
skills/terms-tos - terra-drift
skills/terra-drift - terra-module
skills/terra-module - terra-recon
skills/terra-recon - token-budget
skills/token-budget - token-chunk
skills/token-chunk - token-compact
skills/token-compact - token-recon
skills/token-recon - tone-recon
skills/tone-recon - tone-theme
skills/tone-theme - tone-token
skills/tone-token - tonone-onboard
skills/tonone-onboard - touch
skills/touch - touch-app
skills/touch-app - touch-audit
skills/touch-audit - touch-feature
skills/touch-feature - touch-recon
skills/touch-recon - touch-release
skills/touch-release - touch-ui
skills/touch-ui - trace-debug
skills/trace-debug - trace-instrument
skills/trace-instrument - trace-recon
skills/trace-recon - tune-finetune
skills/tune-finetune - tune-prompt
skills/tune-prompt - tune-recon
skills/tune-recon - vect-embed
skills/vect-embed - vect-recon
skills/vect-recon - vect-search
skills/vect-search - vigil
skills/vigil - vigil-alert
skills/vigil-alert - vigil-check
skills/vigil-check - vigil-incident
skills/vigil-incident - vigil-instrument
skills/vigil-instrument - vigil-recon
skills/vigil-recon - volt
skills/volt - volt-driver
skills/volt-driver - volt-firmware
skills/volt-firmware - volt-ota
skills/volt-ota - volt-power
skills/volt-power - volt-recon
skills/volt-recon - warden
skills/warden - warden-audit
skills/warden-audit - warden-harden
skills/warden-harden - warden-iam
skills/warden-iam - warden-recon
skills/warden-recon - warden-scan
skills/warden-scan - warden-threat
skills/warden-threat - wire-prototype
skills/wire-prototype - wire-recon
skills/wire-recon - wire-spec
skills/wire-spec - zero-audit
skills/zero-audit - zero-design
skills/zero-design - zero-recon
skills/zero-recon - apex-diagnose
team/apex/skills/apex-diagnose - apex-gate
team/apex/skills/apex-gate - apex-plan
team/apex/skills/apex-plan - apex-profile
team/apex/skills/apex-profile - apex-recon
team/apex/skills/apex-recon - apex-review
team/apex/skills/apex-review - apex-route
team/apex/skills/apex-route - apex-stats
team/apex/skills/apex-stats - apex-status
team/apex/skills/apex-status - apex-takeover
team/apex/skills/apex-takeover - atlas-adr
team/atlas/skills/atlas-adr - atlas-changelog
team/atlas/skills/atlas-changelog - atlas-map
team/atlas/skills/atlas-map - atlas-onboard
team/atlas/skills/atlas-onboard - atlas-present
team/atlas/skills/atlas-present - atlas-recon
team/atlas/skills/atlas-recon - atlas-report
team/atlas/skills/atlas-report - audit-controls
team/audit/skills/audit-controls - audit-legal
team/audit/skills/audit-legal - audit-recon
team/audit/skills/audit-recon - axe-audit
team/axe/skills/axe-audit - axe-fix
team/axe/skills/axe-fix - axe-recon
team/axe/skills/axe-recon - bench-compare
team/bench/skills/bench-compare - bench-profile
team/bench/skills/bench-profile - bench-recon
team/bench/skills/bench-recon - bind-gap
team/bind/skills/bind-gap - bind-policy
team/bind/skills/bind-policy - bind-recon
team/bind/skills/bind-recon - blue-detect
team/blue/skills/blue-detect - blue-harden
team/blue/skills/blue-harden - blue-recon
team/blue/skills/blue-recon - brace-escalate
team/brace/skills/brace-escalate - brace-kb
team/brace/skills/brace-kb - brace-metrics
team/brace/skills/brace-metrics - brace-onboard
team/brace/skills/brace-onboard - brace-playbook
team/brace/skills/brace-playbook - brace-recon
team/brace/skills/brace-recon - brace-sla
team/brace/skills/brace-sla - brace-triage
team/brace/skills/brace-triage - brief-draft
team/brief/skills/brief-draft - brief-recon
team/brief/skills/brief-recon - brief-review
team/brief/skills/brief-review - budget-audit
team/budget/skills/budget-audit - budget-optimize
team/budget/skills/budget-optimize - budget-recon
team/budget/skills/budget-recon - buzz-community
team/buzz/skills/buzz-community - buzz-devrel
team/buzz/skills/buzz-devrel - buzz-hn
team/buzz/skills/buzz-hn - buzz-launch
team/buzz/skills/buzz-launch - buzz-outreach
team/buzz/skills/buzz-outreach - buzz-pitch
team/buzz/skills/buzz-pitch - buzz-recon
team/buzz/skills/buzz-recon - buzz-social
team/buzz/skills/buzz-social - cache-design
team/cache/skills/cache-design - cache-evict
team/cache/skills/cache-evict - cache-recon
team/cache/skills/cache-recon - cast-forecast
team/cast/skills/cast-forecast - cast-recon
team/cast/skills/cast-recon - cast-validate
team/cast/skills/cast-validate - chain-recon
team/chain/skills/chain-recon - chain-sbom
team/chain/skills/chain-sbom - chain-scan
team/chain/skills/chain-scan - change-policy
team/change/skills/change-policy - change-recon
team/change/skills/change-recon - change-write
team/change/skills/change-write - chaos-design
team/chaos/skills/chaos-design - chaos-game
team/chaos/skills/chaos-game - chaos-recon
team/chaos/skills/chaos-recon - cite-compare
team/cite/skills/cite-compare - cite-recon
team/cite/skills/cite-recon - cite-research
team/cite/skills/cite-research - clause-analyze
team/clause/skills/clause-analyze - clause-playbook
team/clause/skills/clause-playbook - clause-recon
team/clause/skills/clause-recon - clean-recon
team/clean/skills/clean-recon - clean-transform
team/clean/skills/clean-transform - clean-validate
team/clean/skills/clean-validate - compat-audit
team/compat/skills/compat-audit - compat-policy
team/compat/skills/compat-policy - compat-recon
team/compat/skills/compat-recon - copy-audit
team/copy/skills/copy-audit - copy-recon
team/copy/skills/copy-recon - copy-write
team/copy/skills/copy-write - cortex-eval
team/cortex/skills/cortex-eval - cortex-integrate
team/cortex/skills/cortex-integrate - cortex-model
team/cortex/skills/cortex-model - cortex-prompt
team/cortex/skills/cortex-prompt - cortex-recon
team/cortex/skills/cortex-recon - crest-compete
team/crest/skills/crest-compete - crest-narrative
team/crest/skills/crest-narrative - crest-okr
team/crest/skills/crest-okr - crest-recon
team/crest/skills/crest-recon - crest-roadmap
team/crest/skills/crest-roadmap - cut-icon
team/cut/skills/cut-icon - cut-illustrate
team/cut/skills/cut-illustrate - cut-recon
team/cut/skills/cut-recon - deal-close
team/deal/skills/deal-close - deal-outreach
team/deal/skills/deal-outreach - deal-pipeline
team/deal/skills/deal-pipeline - deal-playbook
team/deal/skills/deal-playbook - deal-pricing
team/deal/skills/deal-pricing - deal-proposal
team/deal/skills/deal-proposal - deal-qualify
team/deal/skills/deal-qualify - deal-recon
team/deal/skills/deal-recon - deal-signals
team/deal/skills/deal-signals - deploy-canary
team/deploy/skills/deploy-canary - deploy-recon
team/deploy/skills/deploy-recon - deploy-serve
team/deploy/skills/deploy-serve - draft-flow
team/draft/skills/draft-flow - draft-ia
team/draft/skills/draft-ia - draft-landing
team/draft/skills/draft-landing - draft-patterns
team/draft/skills/draft-patterns - draft-proto
team/draft/skills/draft-proto - draft-recon
team/draft/skills/draft-recon - draft-review
team/draft/skills/draft-review - draft-wireframe
team/draft/skills/draft-wireframe - drift-alert
team/drift/skills/drift-alert - drift-monitor
team/drift/skills/drift-monitor - drift-recon
team/drift/skills/drift-recon - echo-feedback
team/echo/skills/echo-feedback - echo-interview
team/echo/skills/echo-interview - echo-jobs
team/echo/skills/echo-jobs - echo-panel
team/echo/skills/echo-panel - echo-recon
team/echo/skills/echo-recon - echo-segment
team/echo/skills/echo-segment - edge-cdn
team/edge/skills/edge-cdn - edge-recon
team/edge/skills/edge-recon - edge-route
team/edge/skills/edge-route - embed-design
team/embed/skills/embed-design - embed-recon
team/embed/skills/embed-recon - embed-search
team/embed/skills/embed-search - eval-analyze
team/eval/skills/eval-analyze - eval-design
team/eval/skills/eval-design - eval-recon
team/eval/skills/eval-recon - evals-analyze
team/evals/skills/evals-analyze - evals-design
team/evals/skills/evals-design - evals-harness
team/evals/skills/evals-harness - evals-recon
team/evals/skills/evals-recon - evals-regress
team/evals/skills/evals-regress - feat-engineer
team/feat/skills/feat-engineer - feat-recon
team/feat/skills/feat-recon - feat-store
team/feat/skills/feat-store - finop-audit
team/finop/skills/finop-audit - finop-recon
team/finop/skills/finop-recon - finop-reserve
team/finop/skills/finop-reserve - fit-recon
team/fit/skills/fit-recon - fit-train
team/fit/skills/fit-train - fit-tune
team/fit/skills/fit-tune - flux-health
team/flux/skills/flux-health - flux-migrate
team/flux/skills/flux-migrate - flux-pipeline
team/flux/skills/flux-pipeline - flux-query
team/flux/skills/flux-query - flux-recon
team/flux/skills/flux-recon - flux-schema
team/flux/skills/flux-schema - folk-comp
team/folk/skills/folk-comp - folk-culture
team/folk/skills/folk-culture - folk-hire
team/folk/skills/folk-hire - folk-migrate
team/folk/skills/folk-migrate - folk-onboard
team/folk/skills/folk-onboard - folk-org
team/folk/skills/folk-org - folk-perf
team/folk/skills/folk-perf - folk-recon
team/folk/skills/folk-recon - forge-audit
team/forge/skills/forge-audit - forge-cost
team/forge/skills/forge-cost - forge-diagnose
team/forge/skills/forge-diagnose - forge-infra
team/forge/skills/forge-infra - forge-network
team/forge/skills/forge-network - forge-recon
team/forge/skills/forge-recon - form-animate
team/form/skills/form-animate - form-audit
team/form/skills/form-audit - form-brand
team/form/skills/form-brand - form-brief
team/form/skills/form-brief - form-component
team/form/skills/form-component - form-critique
team/form/skills/form-critique - form-deck
team/form/skills/form-deck - form-direction
team/form/skills/form-direction - form-email
team/form/skills/form-email - form-exam
team/form/skills/form-exam - form-logo
team/form/skills/form-logo - form-mobile
team/form/skills/form-mobile - form-palette
team/form/skills/form-palette - form-social
team/form/skills/form-social - form-style
team/form/skills/form-style - form-tokens
team/form/skills/form-tokens - form-web
team/form/skills/form-web - frame-board
team/frame/skills/frame-board - frame-equity
team/frame/skills/frame-equity - frame-recon
team/frame/skills/frame-recon - gate-ci
team/gate/skills/gate-ci - gate-lint
team/gate/skills/gate-lint - gate-recon
team/gate/skills/gate-recon - glyph-pair
team/glyph/skills/glyph-pair - glyph-recon
team/glyph/skills/glyph-recon - glyph-scale
team/glyph/skills/glyph-scale - grid-layout
team/grid/skills/grid-layout - grid-recon
team/grid/skills/grid-recon - grid-responsive
team/grid/skills/grid-responsive - guard-audit
team/guard/skills/guard-audit - guard-design
team/guard/skills/guard-design - guard-recon
team/guard/skills/guard-recon - guide-audit
team/guide/skills/guide-audit - guide-recon
team/guide/skills/guide-recon - guide-write
team/guide/skills/guide-write - helm-arbiter
team/helm/skills/helm-arbiter - helm-brief
team/helm/skills/helm-brief - helm-handoff
team/helm/skills/helm-handoff - helm-plan
team/helm/skills/helm-plan - helm-recon
team/helm/skills/helm-recon - hue-palette
team/hue/skills/hue-palette - hue-recon
team/hue/skills/hue-recon - hue-token
team/hue/skills/hue-token - hunt-assess
team/hunt/skills/hunt-assess - hunt-ioc
team/hunt/skills/hunt-ioc - hunt-recon
team/hunt/skills/hunt-recon - ink-brief
team/ink/skills/ink-brief - ink-calendar
team/ink/skills/ink-calendar - ink-case
team/ink/skills/ink-case - ink-cluster
team/ink/skills/ink-cluster - ink-distribute
team/ink/skills/ink-distribute - ink-links
team/ink/skills/ink-links - ink-local
team/ink/skills/ink-local - ink-post
team/ink/skills/ink-post - ink-recon
team/ink/skills/ink-recon - ink-seo
team/ink/skills/ink-seo - keel-audit
team/keel/skills/keel-audit - keel-cadence
team/keel/skills/keel-cadence - keel-comply
team/keel/skills/keel-comply - keel-legal
team/keel/skills/keel-legal - keel-okr
team/keel/skills/keel-okr - keel-process
team/keel/skills/keel-process - keel-recon
team/keel/skills/keel-recon - keel-vendor
team/keel/skills/keel-vendor - keep-churn
team/keep/skills/keep-churn - keep-expand
team/keep/skills/keep-expand - keep-health
team/keep/skills/keep-health - keep-onboard
team/keep/skills/keep-onboard - keep-playbook
team/keep/skills/keep-playbook - keep-qbr
team/keep/skills/keep-qbr - keep-recon
team/keep/skills/keep-recon - keep-segment
team/keep/skills/keep-segment - kube-design
team/kube/skills/kube-design - kube-rbac
team/kube/skills/kube-rbac - kube-recon
team/kube/skills/kube-recon - lens-audit
team/lens/skills/lens-audit - lens-chart
team/lens/skills/lens-chart - lens-dashboard
team/lens/skills/lens-dashboard - lens-metrics
team/lens/skills/lens-metrics - lens-recon
team/lens/skills/lens-recon - lens-report
team/lens/skills/lens-report - lodge-dmca
team/lodge/skills/lodge-dmca - lodge-filing
team/lodge/skills/lodge-filing - lodge-recon
team/lodge/skills/lodge-recon - lumen-abtest
team/lumen/skills/lumen-abtest - lumen-funnel
team/lumen/skills/lumen-funnel - lumen-instrument
team/lumen/skills/lumen-instrument - lumen-metrics
team/lumen/skills/lumen-metrics - lumen-recon
team/lumen/skills/lumen-recon - mark-asset
team/mark/skills/mark-asset - mark-brand
team/mark/skills/mark-brand - mark-recon
team/mark/skills/mark-recon - mesh-design
team/mesh/skills/mesh-design - mesh-observe
team/mesh/skills/mesh-observe - mesh-recon
team/mesh/skills/mesh-recon - mint-board
team/mint/skills/mint-board - mint-budget
team/mint/skills/mint-budget - mint-model
team/mint/skills/mint-model - mint-raise
team/mint/skills/mint-raise - mint-recon
team/mint/skills/mint-recon - mint-report
team/mint/skills/mint-report - mint-runway
team/mint/skills/mint-runway - mint-unit
team/mint/skills/mint-unit - mock-contract
team/mock/skills/mock-contract - mock-design
team/mock/skills/mock-design - mock-recon
team/mock/skills/mock-recon - move-animate
team/move/skills/move-animate - move-recon
team/move/skills/move-recon - move-system
team/move/skills/move-system - multi-design
team/multi/skills/multi-design - multi-port
team/multi/skills/multi-port - multi-recon
team/multi/skills/multi-recon - onboard-audit
team/onboard/skills/onboard-audit - onboard-quickstart
team/onboard/skills/onboard-quickstart - onboard-recon
team/onboard/skills/onboard-recon - patch-plan
team/patch/skills/patch-plan - patch-recon
team/patch/skills/patch-recon - patch-triage
team/patch/skills/patch-triage - pave-audit
team/pave/skills/pave-audit - pave-catalog
team/pave/skills/pave-catalog - pave-contribute
team/pave/skills/pave-contribute - pave-env
team/pave/skills/pave-env - pave-golden
team/pave/skills/pave-golden - pave-lsp
team/pave/skills/pave-lsp - pave-recon
team/pave/skills/pave-recon - phish-assess
team/phish/skills/phish-assess - phish-recon
team/phish/skills/phish-recon - phish-train
team/phish/skills/phish-train - pitch-copy
team/pitch/skills/pitch-copy - pitch-landing
team/pitch/skills/pitch-landing - pitch-launch
team/pitch/skills/pitch-launch - pitch-message
team/pitch/skills/pitch-message - pitch-position
team/pitch/skills/pitch-position - pitch-recon
team/pitch/skills/pitch-recon - plot-chart
team/plot/skills/plot-chart - plot-eda
team/plot/skills/plot-eda - plot-recon
team/plot/skills/plot-recon - port-design
team/port/skills/port-design - port-recon
team/port/skills/port-recon - port-review
team/port/skills/port-review - prism-audit
team/prism/skills/prism-audit - prism-chart
team/prism/skills/prism-chart - prism-component
team/prism/skills/prism-component - prism-dashboard
team/prism/skills/prism-dashboard - prism-recon
team/prism/skills/prism-recon - prism-stack
team/prism/skills/prism-stack - prism-ui
team/prism/skills/prism-ui - prompt-design
team/prompt/skills/prompt-design - prompt-recon
team/prompt/skills/prompt-recon - prompt-version
team/prompt/skills/prompt-version - proof-api
team/proof/skills/proof-api - proof-audit
team/proof/skills/proof-audit - proof-design
team/proof/skills/proof-design - proof-e2e
team/proof/skills/proof-e2e - proof-explore
team/proof/skills/proof-explore - proof-recon
team/proof/skills/proof-recon - proof-strategy
team/proof/skills/proof-strategy - queue-design
team/queue/skills/queue-design - queue-recon
team/queue/skills/queue-recon - queue-scale
team/queue/skills/queue-scale - rank-design
team/rank/skills/rank-design - rank-eval
team/rank/skills/rank-eval - rank-recon
team/rank/skills/rank-recon - red-pentest
team/red/skills/red-pentest - red-recon
team/red/skills/red-recon - red-report
team/red/skills/red-report - relay-audit
team/relay/skills/relay-audit - relay-deploy
team/relay/skills/relay-deploy - relay-docker
team/relay/skills/relay-docker - relay-pipeline
team/relay/skills/relay-pipeline - relay-recon
team/relay/skills/relay-recon - relay-ship
team/relay/skills/relay-ship - resp-contain
team/resp/skills/resp-contain - resp-playbook
team/resp/skills/resp-playbook - resp-recon
team/resp/skills/resp-recon - sample-recon
team/sample/skills/sample-recon - sample-review
team/sample/skills/sample-review - sample-write
team/sample/skills/sample-write - sast-fix
team/sast/skills/sast-fix - sast-recon
team/sast/skills/sast-recon - sast-scan
team/sast/skills/sast-scan - schema-design
team/schema/skills/schema-design - schema-recon
team/schema/skills/schema-recon - schema-review
team/schema/skills/schema-review - scope-oss
team/scope/skills/scope-oss - scope-recon
team/scope/skills/scope-recon - scope-trademark
team/scope/skills/scope-trademark - score-compare
team/score/skills/score-compare - score-eval
team/score/skills/score-eval - score-recon
team/score/skills/score-recon - serv-cold
team/serv/skills/serv-cold - serv-design
team/serv/skills/serv-design - serv-recon
team/serv/skills/serv-recon - shield-assess
team/shield/skills/shield-assess - shield-recon
team/shield/skills/shield-recon - shield-respond
team/shield/skills/shield-respond - siem-alert
team/siem/skills/siem-alert - siem-recon
team/siem/skills/siem-recon - siem-rule
team/siem/skills/siem-rule - spine-api
team/spine/skills/spine-api - spine-design
team/spine/skills/spine-design - spine-perf
team/spine/skills/spine-perf - spine-recon
team/spine/skills/spine-recon - spine-review
team/spine/skills/spine-review - spine-service
team/spine/skills/spine-service - spine-simplify
team/spine/skills/spine-simplify - surge-activation
team/surge/skills/surge-activation - surge-experiment
team/surge/skills/surge-experiment - surge-landing
team/surge/skills/surge-landing - surge-plg
team/surge/skills/surge-plg - surge-recon
team/surge/skills/surge-recon - surge-retention
team/surge/skills/surge-retention - terms-privacy
team/terms/skills/terms-privacy - terms-recon
team/terms/skills/terms-recon - terms-tos
team/terms/skills/terms-tos - terra-drift
team/terra/skills/terra-drift - terra-module
team/terra/skills/terra-module - terra-recon
team/terra/skills/terra-recon - token-budget
team/token/skills/token-budget - token-chunk
team/token/skills/token-chunk - token-compact
team/token/skills/token-compact - token-recon
team/token/skills/token-recon - tone-recon
team/tone/skills/tone-recon - tone-theme
team/tone/skills/tone-theme - tone-token
team/tone/skills/tone-token - touch-app
team/touch/skills/touch-app - touch-audit
team/touch/skills/touch-audit - touch-feature
team/touch/skills/touch-feature - touch-recon
team/touch/skills/touch-recon - touch-release
team/touch/skills/touch-release - touch-ui
team/touch/skills/touch-ui - trace-debug
team/trace/skills/trace-debug - trace-instrument
team/trace/skills/trace-instrument - trace-recon
team/trace/skills/trace-recon - tune-finetune
team/tune/skills/tune-finetune - tune-prompt
team/tune/skills/tune-prompt - tune-recon
team/tune/skills/tune-recon - vect-embed
team/vect/skills/vect-embed - vect-recon
team/vect/skills/vect-recon - vect-search
team/vect/skills/vect-search - vigil-alert
team/vigil/skills/vigil-alert - vigil-check
team/vigil/skills/vigil-check - vigil-incident
team/vigil/skills/vigil-incident - vigil-instrument
team/vigil/skills/vigil-instrument - vigil-recon
team/vigil/skills/vigil-recon - volt-driver
team/volt/skills/volt-driver - volt-firmware
team/volt/skills/volt-firmware - volt-ota
team/volt/skills/volt-ota - volt-power
team/volt/skills/volt-power - volt-recon
team/volt/skills/volt-recon - warden-audit
team/warden/skills/warden-audit - warden-harden
team/warden/skills/warden-harden - warden-iam
team/warden/skills/warden-iam - warden-recon
team/warden/skills/warden-recon - warden-scan
team/warden/skills/warden-scan - warden-threat
team/warden/skills/warden-threat - wire-prototype
team/wire/skills/wire-prototype - wire-recon
team/wire/skills/wire-recon - wire-spec
team/wire/skills/wire-spec - zero-audit
team/zero/skills/zero-audit - zero-design
team/zero/skills/zero-design - zero-recon
team/zero/skills/zero-recon - SKILL_NAME
templates/new-agent/skills/SKILL_NAME
How it works
apex-plan
When your agent uses it
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
2,078 tokensWhen the skill is activated
Reference documents
1,157 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Scripts executed separately
../../../../team/apex/scripts/setup.sh../../../../team/apex/scripts/setup.sh../../../../team/apex/scripts/setup.sh../../../../team/apex/scripts/setup.sh../../../../team/atlas/scripts/setup.sh../../../../team/atlas/scripts/setup.sh../../../../team/atlas/scripts/setup.sh../../../../team/atlas/scripts/setup.sh../../../../team/brace/scripts/setup.sh../../../../team/brace/scripts/setup.sh../../../../team/brace/scripts/setup.sh../../../../team/brace/scripts/setup.sh../../../../team/buzz/scripts/setup.sh../../../../team/buzz/scripts/setup.sh../../../../team/buzz/scripts/setup.sh../../../../team/buzz/scripts/setup.sh../../../../team/cortex/scripts/setup.sh../../../../team/cortex/scripts/setup.sh../../../../team/cortex/scripts/setup.sh../../../../team/cortex/scripts/setup.sh../../../../team/crest/scripts/setup.sh../../../../team/crest/scripts/setup.sh../../../../team/crest/scripts/setup.sh../../../../team/crest/scripts/setup.sh../../../../team/deal/scripts/setup.sh../../../../team/deal/scripts/setup.sh../../../../team/deal/scripts/setup.sh../../../../team/deal/scripts/setup.sh../../../../team/draft/scripts/setup.sh../../../../team/draft/scripts/setup.sh../../../../team/draft/scripts/setup.sh../../../../team/draft/scripts/setup.sh../../../../team/echo/scripts/setup.sh../../../../team/echo/scripts/setup.sh../../../../team/echo/scripts/setup.sh../../../../team/echo/scripts/setup.sh../../../../team/flux/scripts/setup.sh../../../../team/flux/scripts/setup.sh../../../../team/flux/scripts/setup.sh../../../../team/flux/scripts/setup.sh../../../../team/folk/scripts/setup.sh../../../../team/folk/scripts/setup.sh../../../../team/folk/scripts/setup.sh../../../../team/folk/scripts/setup.sh../../../../team/forge/scripts/setup.sh../../../../team/forge/scripts/setup.sh../../../../team/forge/scripts/setup.sh../../../../team/forge/scripts/setup.sh../../../../team/form/scripts/setup.sh../../../../team/form/scripts/setup.sh../../../../team/form/scripts/setup.sh../../../../team/form/scripts/setup.sh../../../../team/helm/scripts/setup.sh../../../../team/helm/scripts/setup.sh../../../../team/helm/scripts/setup.sh../../../../team/helm/scripts/setup.sh../../../../team/ink/scripts/setup.sh../../../../team/ink/scripts/setup.sh../../../../team/ink/scripts/setup.sh../../../../team/ink/scripts/setup.sh../../../../team/keel/scripts/setup.sh../../../../team/keel/scripts/setup.sh../../../../team/keel/scripts/setup.sh../../../../team/keel/scripts/setup.sh../../../../team/keep/scripts/setup.sh../../../../team/keep/scripts/setup.sh../../../../team/keep/scripts/setup.sh../../../../team/keep/scripts/setup.sh../../../../team/lens/scripts/setup.sh../../../../team/lens/scripts/setup.sh../../../../team/lens/scripts/setup.sh../../../../team/lens/scripts/setup.sh../../../../team/lumen/scripts/setup.sh../../../../team/lumen/scripts/setup.sh../../../../team/lumen/scripts/setup.sh../../../../team/lumen/scripts/setup.sh../../../../team/mint/scripts/setup.sh../../../../team/mint/scripts/setup.sh../../../../team/mint/scripts/setup.sh../../../../team/mint/scripts/setup.sh../../../../team/pave/scripts/setup.sh../../../../team/pave/scripts/setup.sh../../../../team/pave/scripts/setup.sh../../../../team/pave/scripts/setup.sh../../../../team/pitch/scripts/setup.sh../../../../team/pitch/scripts/setup.sh../../../../team/pitch/scripts/setup.sh../../../../team/pitch/scripts/setup.sh../../../../team/prism/scripts/setup.sh../../../../team/prism/scripts/setup.sh../../../../team/prism/scripts/setup.sh../../../../team/prism/scripts/setup.sh../../../../team/proof/scripts/setup.sh../../../../team/proof/scripts/setup.sh../../../../team/proof/scripts/setup.sh../../../../team/proof/scripts/setup.sh../../../../team/relay/scripts/setup.sh../../../../team/relay/scripts/setup.sh../../../../team/relay/scripts/setup.sh../../../../team/relay/scripts/setup.sh../../../../team/spine/scripts/setup.sh../../../../team/spine/scripts/setup.sh../../../../team/spine/scripts/setup.sh../../../../team/spine/scripts/setup.sh../../../../team/surge/scripts/setup.sh../../../../team/surge/scripts/setup.sh../../../../team/surge/scripts/setup.sh../../../../team/surge/scripts/setup.sh../../../../team/touch/scripts/setup.sh../../../../team/touch/scripts/setup.sh../../../../team/touch/scripts/setup.sh../../../../team/touch/scripts/setup.sh../../../../team/vigil/scripts/setup.sh../../../../team/vigil/scripts/setup.sh../../../../team/vigil/scripts/setup.sh../../../../team/vigil/scripts/setup.sh../../../../team/volt/scripts/setup.sh../../../../team/volt/scripts/setup.sh../../../../team/volt/scripts/setup.sh../../../../team/volt/scripts/setup.sh../../../../team/warden/scripts/setup.sh../../../../team/warden/scripts/setup.sh../../../../team/warden/scripts/setup.sh../../../../team/warden/scripts/setup.sh
Files
../../../../.claude-plugin/CLAUDE.mddoc319 bytes../../../../.claude-plugin/marketplace.jsonasset38,151 bytes../../../../.claude-plugin/marketplace.jsonasset38,151 bytes../../../../.claude-plugin/plugin.jsonasset1,551 bytes../../../ai-ops-team/.claude-plugin/plugin.jsonasset388 bytes../../../data-science-team/.claude-plugin/plugin.jsonasset403 bytes../../../design-team/.claude-plugin/plugin.jsonasset369 bytes../../../devx-team/.claude-plugin/plugin.jsonasset416 bytes../../.claude-plugin/plugin.jsonasset418 bytes../../hooks/hooks.jsonasset18 bytesSKILL.mdcore8,837 bytesSKILL.mdcore8,837 bytesSKILL.mdcore8,837 bytes../../../full-team/.claude-plugin/plugin.jsonasset446 bytes../../../full-team/hooks/hooks.jsonasset18 bytes../../../infra-specialist-team/.claude-plugin/plugin.jsonasset457 bytes../../../legal-team/.claude-plugin/plugin.jsonasset480 bytes../../../marketing-team/.claude-plugin/plugin.jsonasset327 bytes../../../marketing-team/hooks/hooks.jsonasset18 bytes../../../operations-team/.claude-plugin/plugin.jsonasset415 bytes../../../product-team/.claude-plugin/plugin.jsonasset356 bytes../../../product-team/hooks/hooks.jsonasset18 bytes../../../revenue-team/.claude-plugin/plugin.jsonasset322 bytes../../../revenue-team/hooks/hooks.jsonasset18 bytes../../../secops-team/.claude-plugin/plugin.jsonasset398 bytes../../../tonone-core/.claude-plugin/plugin.jsonasset677 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../hooks/hooks.jsonasset2,395 bytes../../../../team/apex/.claude-plugin/plugin.jsonasset379 bytes../../../../team/apex/hooks/hooks.jsonasset155 bytes../../../../team/apex/scripts/setup.shruns450 bytes../../../../team/apex/scripts/setup.shruns450 bytes../../../../team/apex/scripts/setup.shruns450 bytes../../../../team/apex/scripts/setup.shruns450 bytes../../../../team/atlas/.claude-plugin/plugin.jsonasset578 bytes../../../../team/atlas/hooks/hooks.jsonasset516 bytes../../../../team/atlas/scripts/setup.shruns451 bytes../../../../team/atlas/scripts/setup.shruns451 bytes../../../../team/atlas/scripts/setup.shruns451 bytes../../../../team/atlas/scripts/setup.shruns451 bytes../../../../team/audit/.claude-plugin/plugin.jsonasset433 bytes../../../../team/axe/.claude-plugin/plugin.jsonasset383 bytes../../../../team/bench/.claude-plugin/plugin.jsonasset443 bytes../../../../team/bind/.claude-plugin/plugin.jsonasset402 bytes../../../../team/blue/.claude-plugin/plugin.jsonasset406 bytes../../../../team/brace/.claude-plugin/plugin.jsonasset506 bytes../../../../team/brace/hooks/hooks.jsonasset169 bytes../../../../team/brace/scripts/setup.shruns451 bytes../../../../team/brace/scripts/setup.shruns451 bytes../../../../team/brace/scripts/setup.shruns451 bytes../../../../team/brace/scripts/setup.shruns451 bytes../../../../team/brief/.claude-plugin/plugin.jsonasset369 bytes../../../../team/budget/.claude-plugin/plugin.jsonasset414 bytes../../../../team/buzz/.claude-plugin/plugin.jsonasset457 bytes../../../../team/buzz/.claude-plugin/plugin.jsonasset457 bytes../../../../team/buzz/hooks/hooks.jsonasset169 bytes../../../../team/buzz/scripts/setup.shruns450 bytes../../../../team/buzz/scripts/setup.shruns450 bytes../../../../team/buzz/scripts/setup.shruns450 bytes../../../../team/buzz/scripts/setup.shruns450 bytes../../../../team/cache/.claude-plugin/plugin.jsonasset487 bytes../../../../team/cast/.claude-plugin/plugin.jsonasset411 bytes../../../../team/chain/.claude-plugin/plugin.jsonasset430 bytes../../../../team/change/.claude-plugin/plugin.jsonasset450 bytes../../../../team/chaos/.claude-plugin/plugin.jsonasset474 bytes../../../../team/cite/.claude-plugin/plugin.jsonasset432 bytes../../../../team/clause/.claude-plugin/plugin.jsonasset370 bytes../../../../team/clean/.claude-plugin/plugin.jsonasset411 bytes../../../../team/compat/.claude-plugin/plugin.jsonasset438 bytes../../../../team/copy/.claude-plugin/plugin.jsonasset400 bytes../../../../team/cortex/.claude-plugin/plugin.jsonasset375 bytes../../../../team/cortex/hooks/hooks.jsonasset169 bytes../../../../team/cortex/scripts/setup.shruns452 bytes../../../../team/cortex/scripts/setup.shruns452 bytes../../../../team/cortex/scripts/setup.shruns452 bytes../../../../team/cortex/scripts/setup.shruns452 bytes../../../../team/crest/.claude-plugin/plugin.jsonasset443 bytes../../../../team/crest/hooks/hooks.jsonasset175 bytes../../../../team/crest/scripts/setup.shruns451 bytes../../../../team/crest/scripts/setup.shruns451 bytes../../../../team/crest/scripts/setup.shruns451 bytes../../../../team/crest/scripts/setup.shruns451 bytes../../../../team/cut/.claude-plugin/plugin.jsonasset377 bytes../../../../team/deal/.claude-plugin/plugin.jsonasset447 bytes../../../../team/deal/hooks/hooks.jsonasset169 bytes../../../../team/deal/scripts/setup.shruns450 bytes../../../../team/deal/scripts/setup.shruns450 bytes../../../../team/deal/scripts/setup.shruns450 bytes../../../../team/deal/scripts/setup.shruns450 bytes../../../../team/deploy/.claude-plugin/plugin.jsonasset405 bytes../../../../team/draft/.claude-plugin/plugin.jsonasset383 bytes../../../../team/draft/hooks/hooks.jsonasset175 bytes../../../../team/draft/scripts/setup.shruns604 bytes../../../../team/draft/scripts/setup.shruns604 bytes../../../../team/draft/scripts/setup.shruns604 bytes../../../../team/draft/scripts/setup.shruns604 bytes../../../../team/drift/.claude-plugin/plugin.jsonasset413 bytes../../../../team/echo/.claude-plugin/plugin.jsonasset420 bytes../../../../team/echo/hooks/hooks.jsonasset174 bytes../../../../team/echo/scripts/setup.shruns450 bytes../../../../team/echo/scripts/setup.shruns450 bytes../../../../team/echo/scripts/setup.shruns450 bytes../../../../team/echo/scripts/setup.shruns450 bytes../../../../team/edge/.claude-plugin/plugin.jsonasset472 bytes../../../../team/embed/.claude-plugin/plugin.jsonasset406 bytes../../../../team/eval/.claude-plugin/plugin.jsonasset417 bytes../../../../team/evals/.claude-plugin/plugin.jsonasset403 bytes../../../../team/feat/.claude-plugin/plugin.jsonasset409 bytes../../../../team/finop/.claude-plugin/plugin.jsonasset472 bytes../../../../team/fit/.claude-plugin/plugin.jsonasset409 bytes../../../../team/flux/.claude-plugin/plugin.jsonasset359 bytes../../../../team/flux/hooks/hooks.jsonasset169 bytes../../../../team/flux/scripts/setup.shruns450 bytes../../../../team/flux/scripts/setup.shruns450 bytes../../../../team/flux/scripts/setup.shruns450 bytes../../../../team/flux/scripts/setup.shruns450 bytes../../../../team/folk/.claude-plugin/plugin.jsonasset516 bytes../../../../team/folk/hooks/hooks.jsonasset169 bytes../../../../team/folk/scripts/setup.shruns450 bytes../../../../team/folk/scripts/setup.shruns450 bytes../../../../team/folk/scripts/setup.shruns450 bytes../../../../team/folk/scripts/setup.shruns450 bytes../../../../team/forge/.claude-plugin/plugin.jsonasset369 bytes../../../../team/forge/hooks/hooks.jsonasset169 bytes../../../../team/forge/scripts/setup.shruns451 bytes../../../../team/forge/scripts/setup.shruns451 bytes../../../../team/forge/scripts/setup.shruns451 bytes../../../../team/forge/scripts/setup.shruns451 bytes../../../../team/form/.claude-plugin/plugin.jsonasset431 bytes../../../../team/form/hooks/hooks.jsonasset174 bytes../../../../team/form/scripts/setup.shruns603 bytes../../../../team/form/scripts/setup.shruns603 bytes../../../../team/form/scripts/setup.shruns603 bytes../../../../team/form/scripts/setup.shruns603 bytes../../../../team/frame/.claude-plugin/plugin.jsonasset440 bytes../../../../team/gate/.claude-plugin/plugin.jsonasset424 bytes../../../../team/glyph/.claude-plugin/plugin.jsonasset389 bytes../../../../team/grid/.claude-plugin/plugin.jsonasset391 bytes../../../../team/guard/.claude-plugin/plugin.jsonasset405 bytes../../../../team/guide/.claude-plugin/plugin.jsonasset423 bytes../../../../team/helm/.claude-plugin/plugin.jsonasset404 bytes../../../../team/helm/hooks/hooks.jsonasset174 bytes../../../../team/helm/scripts/setup.shruns450 bytes../../../../team/helm/scripts/setup.shruns450 bytes../../../../team/helm/scripts/setup.shruns450 bytes../../../../team/helm/scripts/setup.shruns450 bytes../../../../team/hue/.claude-plugin/plugin.jsonasset382 bytes../../../../team/hunt/.claude-plugin/plugin.jsonasset408 bytes../../../../team/ink/.claude-plugin/plugin.jsonasset456 bytes../../../../team/ink/hooks/hooks.jsonasset169 bytes../../../../team/ink/scripts/setup.shruns449 bytes../../../../team/ink/scripts/setup.shruns449 bytes../../../../team/ink/scripts/setup.shruns449 bytes../../../../team/ink/scripts/setup.shruns449 bytes../../../../team/keel/.claude-plugin/plugin.jsonasset487 bytes../../../../team/keel/hooks/hooks.jsonasset169 bytes../../../../team/keel/scripts/setup.shruns450 bytes../../../../team/keel/scripts/setup.shruns450 bytes../../../../team/keel/scripts/setup.shruns450 bytes../../../../team/keel/scripts/setup.shruns450 bytes../../../../team/keep/.claude-plugin/plugin.jsonasset468 bytes../../../../team/keep/hooks/hooks.jsonasset169 bytes../../../../team/keep/scripts/setup.shruns450 bytes../../../../team/keep/scripts/setup.shruns450 bytes../../../../team/keep/scripts/setup.shruns450 bytes../../../../team/keep/scripts/setup.shruns450 bytes../../../../team/kube/.claude-plugin/plugin.jsonasset453 bytes../../../../team/lens/.claude-plugin/plugin.jsonasset425 bytes../../../../team/lens/hooks/hooks.jsonasset155 bytes../../../../team/lens/scripts/setup.shruns603 bytes../../../../team/lens/scripts/setup.shruns603 bytes../../../../team/lens/scripts/setup.shruns603 bytes../../../../team/lens/scripts/setup.shruns603 bytes../../../../team/lodge/.claude-plugin/plugin.jsonasset452 bytes../../../../team/lumen/.claude-plugin/plugin.jsonasset435 bytes../../../../team/lumen/hooks/hooks.jsonasset175 bytes../../../../team/lumen/scripts/setup.shruns451 bytes../../../../team/lumen/scripts/setup.shruns451 bytes../../../../team/lumen/scripts/setup.shruns451 bytes../../../../team/lumen/scripts/setup.shruns451 bytes../../../../team/mark/.claude-plugin/plugin.jsonasset387 bytes../../../../team/mesh/.claude-plugin/plugin.jsonasset468 bytes../../../../team/mint/.claude-plugin/plugin.jsonasset460 bytes../../../../team/mint/hooks/hooks.jsonasset169 bytes../../../../team/mint/scripts/setup.shruns450 bytes../../../../team/mint/scripts/setup.shruns450 bytes../../../../team/mint/scripts/setup.shruns450 bytes../../../../team/mint/scripts/setup.shruns450 bytes../../../../team/mock/.claude-plugin/plugin.jsonasset420 bytes../../../../team/move/.claude-plugin/plugin.jsonasset385 bytes../../../../team/multi/.claude-plugin/plugin.jsonasset483 bytes../../../../team/onboard/.claude-plugin/plugin.jsonasset445 bytes../../../../team/patch/.claude-plugin/plugin.jsonasset420 bytes../../../../team/pave/.claude-plugin/plugin.jsonasset448 bytes../../../../team/pave/hooks/hooks.jsonasset169 bytes../../../../team/pave/scripts/setup.shruns450 bytes../../../../team/pave/scripts/setup.shruns450 bytes../../../../team/pave/scripts/setup.shruns450 bytes../../../../team/pave/scripts/setup.shruns450 bytes../../../../team/pave/skills/pave-contribute/.claude-plugin/plugin.jsonasset314 bytes../../../../team/pave/skills/pave-contribute/SKILL.mddoc4,553 bytes../../../../team/phish/.claude-plugin/plugin.jsonasset438 bytes../../../../team/pitch/.claude-plugin/plugin.jsonasset430 bytes../../../../team/pitch/hooks/hooks.jsonasset175 bytes../../../../team/pitch/scripts/setup.shruns604 bytes../../../../team/pitch/scripts/setup.shruns604 bytes../../../../team/pitch/scripts/setup.shruns604 bytes../../../../team/pitch/scripts/setup.shruns604 bytes../../../../team/plot/.claude-plugin/plugin.jsonasset425 bytes../../../../team/port/.claude-plugin/plugin.jsonasset434 bytes../../../../team/prism/.claude-plugin/plugin.jsonasset353 bytes../../../../team/prism/hooks/hooks.jsonasset169 bytes../../../../team/prism/scripts/setup.shruns604 bytes../../../../team/prism/scripts/setup.shruns604 bytes../../../../team/prism/scripts/setup.shruns604 bytes../../../../team/prism/scripts/setup.shruns604 bytes../../../../team/prompt/.claude-plugin/plugin.jsonasset429 bytes../../../../team/proof/.claude-plugin/plugin.jsonasset397 bytes../../../../team/proof/hooks/hooks.jsonasset169 bytes../../../../team/proof/scripts/setup.shruns451 bytes../../../../team/proof/scripts/setup.shruns451 bytes../../../../team/proof/scripts/setup.shruns451 bytes../../../../team/proof/scripts/setup.shruns451 bytes../../../../team/queue/.claude-plugin/plugin.jsonasset481 bytes../../../../team/rank/.claude-plugin/plugin.jsonasset419 bytes../../../../team/red/.claude-plugin/plugin.jsonasset414 bytes../../../../team/relay/.claude-plugin/plugin.jsonasset366 bytes../../../../team/relay/hooks/hooks.jsonasset169 bytes../../../../team/relay/scripts/setup.shruns451 bytes../../../../team/relay/scripts/setup.shruns451 bytes../../../../team/relay/scripts/setup.shruns451 bytes../../../../team/relay/scripts/setup.shruns451 bytes../../../../team/resp/.claude-plugin/plugin.jsonasset416 bytes../../../../team/sample/.claude-plugin/plugin.jsonasset432 bytes../../../../team/sast/.claude-plugin/plugin.jsonasset412 bytes../../../../team/schema/.claude-plugin/plugin.jsonasset423 bytes../../../../team/scope/.claude-plugin/plugin.jsonasset431 bytes../../../../team/scope/.claude-plugin/plugin.jsonasset431 bytes../../../../team/score/.claude-plugin/plugin.jsonasset431 bytes../../../../team/serv/.claude-plugin/plugin.jsonasset480 bytes../../../../team/shield/.claude-plugin/plugin.jsonasset442 bytes../../../../team/siem/.claude-plugin/plugin.jsonasset409 bytes../../../../team/spine/.claude-plugin/plugin.jsonasset406 bytes../../../../team/spine/hooks/hooks.jsonasset169 bytes../../../../team/spine/scripts/setup.shruns451 bytes../../../../team/spine/scripts/setup.shruns451 bytes../../../../team/spine/scripts/setup.shruns451 bytes../../../../team/spine/scripts/setup.shruns451 bytes../../../../team/surge/.claude-plugin/plugin.jsonasset437 bytes../../../../team/surge/hooks/hooks.jsonasset175 bytes../../../../team/surge/scripts/setup.shruns604 bytes../../../../team/surge/scripts/setup.shruns604 bytes../../../../team/surge/scripts/setup.shruns604 bytes../../../../team/surge/scripts/setup.shruns604 bytes../../../../team/terms/.claude-plugin/plugin.jsonasset414 bytes../../../../team/terra/.claude-plugin/plugin.jsonasset469 bytes../../../../team/token/.claude-plugin/plugin.jsonasset413 bytes../../../../team/tone/.claude-plugin/plugin.jsonasset394 bytes../../../../team/touch/.claude-plugin/plugin.jsonasset417 bytes../../../../team/touch/hooks/hooks.jsonasset169 bytes../../../../team/touch/scripts/setup.shruns604 bytes../../../../team/touch/scripts/setup.shruns604 bytes../../../../team/touch/scripts/setup.shruns604 bytes../../../../team/touch/scripts/setup.shruns604 bytes../../../../team/trace/.claude-plugin/plugin.jsonasset400 bytes../../../../team/tune/.claude-plugin/plugin.jsonasset402 bytes../../../../team/vect/.claude-plugin/plugin.jsonasset413 bytes../../../../team/vigil/.claude-plugin/plugin.jsonasset428 bytes../../../../team/vigil/hooks/hooks.jsonasset169 bytes../../../../team/vigil/scripts/setup.shruns451 bytes../../../../team/vigil/scripts/setup.shruns451 bytes../../../../team/vigil/scripts/setup.shruns451 bytes../../../../team/vigil/scripts/setup.shruns451 bytes../../../../team/volt/.claude-plugin/plugin.jsonasset422 bytes../../../../team/volt/hooks/hooks.jsonasset169 bytes../../../../team/volt/scripts/setup.shruns450 bytes../../../../team/volt/scripts/setup.shruns450 bytes../../../../team/volt/scripts/setup.shruns450 bytes../../../../team/volt/scripts/setup.shruns450 bytes../../../../team/warden/.claude-plugin/plugin.jsonasset362 bytes../../../../team/warden/hooks/hooks.jsonasset169 bytes../../../../team/warden/scripts/setup.shruns452 bytes../../../../team/warden/scripts/setup.shruns452 bytes../../../../team/warden/scripts/setup.shruns452 bytes../../../../team/warden/scripts/setup.shruns452 bytes../../../../team/wire/.claude-plugin/plugin.jsonasset387 bytes../../../../team/zero/.claude-plugin/plugin.jsonasset424 bytes../../../../templates/new-agent/.claude-plugin/plugin.jsonasset255 bytes../../../../templates/new-agent/hooks/hooks.jsonasset215 bytes../../../../templates/new-agent/hooks/hooks.jsonasset215 bytes
Read SKILL.md
# Apex Plan
You are Apex — the engineering lead. Scope a project. Understand the real problem, challenge complexity, present clear options so the user can decide.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Discovery** — ask clarifying questions to understand the real problem. Challenge complexity. Dig for the actual need behind the requested solution. Don't accept the first framing — ask what problem this solves, who is affected, what the simplest version looks like, and whether this is blocking revenue or a nice-to-have.
2. **Assess which specialists are needed and at what depth.** Map the problem to the team roster: Forge (infra), Relay (CI/CD), Spine (backend), Flux (data), Warden (security), Vigil (observability), Prism (frontend), Cortex (ML/AI), Touch (mobile), Volt (embedded), Atlas (architecture docs), Lens (analytics). Only include specialists who are actually needed — 6 specialists when 2 would do is waste, not thoroughness.
3. **Optional: get a tier proposal from the decision layer.** The depth pick is a position on a 6-level ordered rubric — a `score` question. Run it as an assist that _proposes_. It never selects, and Step 5 still waits for the user.View the complete source on GitHubapex-recon
When your agent uses it
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
803 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytes
Read SKILL.md
# Engineering Reconnaissance
You are Apex — the engineering lead on the Engineering Team. Map the project before you plan anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for project structure indicators:
```bash
ls -laView the complete source on GitHubapex-review
When your agent uses it
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,445 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytes
Read SKILL.md
# Apex Review
You are Apex — the engineering lead. Review recent work with a cross-cutting eye. Catch what individual specialists miss: gaps between components, concerns that span domains.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
0. **Run the automated health snapshot.** From the repo root:
```bash
cd team/apex/scripts && pip install -e . --quiet && python apex_agent/apex_scan.py . --skip-health --skip-deps --out /tmp/apex-scan.json 2>/dev/null || true
python apex_agent/apex_scan.py . --skip-endpoints 2>&1 | tail -20
```View the complete source on GitHubapex-status
When your agent uses it
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
378 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytes
Read SKILL.md
# Apex Status
You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Check recent commits.**
```bash
git log --oneline -20
```
View the complete source on GitHubapex-takeover
When your agent uses it
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
924 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore4,127 bytes
Read SKILL.md
# Apex Takeover
You are Apex — the engineering lead. Take ownership of an inherited system. Structured reconnaissance operation: understand before changing anything. Move through three phases, delivering findings at each stage.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Phase 1 — Reconnaissance** (parallel specialist dispatches):
Run these in parallel — they are independent:
- **Atlas**: Map the codebase — architecture, dependencies, tech stack, directory structure, key abstractions. Read project manifests, config files, and entrypoints.
- **Forge**: Inventory infrastructure — what's running, where, how much. Check for IaC files (Terraform, CloudFormation, Dockerfiles, docker-compose, k8s manifests).
- **Relay**: Assess the pipeline — how does code get to production. Check CI configs (.github/workflows, Jenkinsfile, .gitlab-ci.yml), deployment scripts, release process.View the complete source on GitHubatlas-adr
When your agent uses it
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,494 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Detect ADR Conventions
- Step 1: Gather the Decision Context
- Step 2: Write the ADR
- Step 3: Save the ADR
- Step 4: Output Summary (CLI)
- Delivery
Files
SKILL.mdcore7,221 bytes
Read SKILL.md
# Write an Architecture Decision Record
You are Atlas — the knowledge engineer from the Engineering Team. Produce a complete, honest ADR — not a template exercise, not a coaching session. Given a decision, write the record.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
ADR is an explanation-type document. Its only job: preserve the context of a decision so future engineers understand _why_ the system is shaped as it is — and don't unknowingly undermine choices that had good reasons, or re-fight battles already settled.
What makes ADRs fail in practice:
- **Thin context.** "We needed a database" is not context. Context is constraints, team state, scale, timeline, existing stack.
- **Fake alternatives.** One obvious loser next to the winner is theater. List the real contenders.View the complete source on GitHubatlas-changelog
When your agent uses it
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,237 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore5,228 bytes
Read SKILL.md
# Maintain Changelog
You are Atlas — the knowledge engineer on the Engineering Team. Maintain the team's change history across repos.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Workspace
Scan the workspace layout:
- Check for sub-repos — directories containing `.git/`
- Check for existing `.changelog/` directoriesView the complete source on GitHubatlas-map
When your agent uses it
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,762 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Read the Codebase
- Step 1: Identify the Pieces
- Step 2: Produce the C4 Level 1 — System Context
- Step 3: Produce the C4 Level 2 — Container Diagram
- Step 4: Component Descriptions
- Step 5: Observations
- Step 6: Save
- Output Summary (CLI)
- Delivery
Files
SKILL.mdcore7,742 bytes
Read SKILL.md
# Map the System Architecture
You are Atlas — the knowledge engineer from the Engineering Team. Produce an actual architecture map — not a template for making one. Read the codebase, understand the system, write the diagrams and descriptions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
The map must answer one question clearly: _How is this system structured and how do the pieces talk to each other?_ If someone reads it and still doesn't know where a request goes when it hits the system, the map has failed.
Use the C4 model as your abstraction framework. Level 1 (System Context) orients any audience. Level 2 (Container) orients a developer joining the team. Only go to Level 3 (Component) if a single service is complex enough to warrant it.
One diagram = one question. Split rather than pile on.
View the complete source on GitHubatlas-onboard
When your agent uses it
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,051 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,454 bytes
Read SKILL.md
# Generate Onboarding Documentation
You are Atlas — the knowledge engineer from the Engineering Team. Write for the person on day 1 who knows nothing about this project.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for project indicators:
- `README.md` — existing readme (assess quality and freshness)
- `CONTRIBUTING.md` — existing contributor guideView the complete source on GitHubatlas-present
When your agent uses it
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,769 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore6,773 bytes
Read SKILL.md
# Release Presentation
You are Atlas — the knowledge engineer on the Engineering Team. Translate technical work into compelling narratives for non-technical stakeholders.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Determine Scope
From user description, changelogs (`.changelog/CHANGELOG.md`), git log (`--since={date}`), or PRs, identify:
- **Title** — the name of the release or feature
- **Date range** — when the work happenedView the complete source on GitHubatlas-recon
When your agent uses it
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,143 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,604 bytes
Read SKILL.md
# Documentation Reconnaissance
You are Atlas — the knowledge engineer from the Engineering Team. Map the knowledge terrain before you change anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for documentation in all locations:
- `README.md` (root and nested)
- `docs/`, `doc/`, `documentation/` directoriesView the complete source on GitHubatlas-report
When your agent uses it
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
2,742 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
Files
SKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytes
Read SKILL.md
# Render HTML Report
You are Atlas — the knowledge engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Context
Determine what to report on. Sources (in priority order):
1. **Conversation context** — recent agent output, findings, or analysis in this session
2. **Explicit request** — user specifies a file, skill output, or topicView the complete source on GitHubcortex-eval
When your agent uses it
Evaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,563 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../../../team/cortex/scripts/cortex_agent/eval_scan.py
Files
SKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytes../../../../team/cortex/scripts/cortex_agent/eval_scan.pyruns3,112 bytes
Read SKILL.md
# Evaluate Model Performance
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run Static Analysis
Before any LLM-based evaluation, run the static analysis scanner to find LLM usage anti-patterns and prompt quality issues:
```bash
# From the project root (or team/cortex/scripts/)View the complete source on GitHubcortex-integrate
When your agent uses it
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
2,005 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Scan the Codebase
- Step 1: Apply the Architecture Decision Tree
- Step 2: Select the Model
- Step 3: Design the Integration Architecture
- Step 4: Implement
- Step 5: Write Baseline Evals
- Step 6: Output
- Delivery
Files
SKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytes
Read SKILL.md
# AI Feature Integration
You are Cortex — the ML/AI engineer on the Engineering Team. Given a feature description, produce the integration architecture with all decisions made, then implement it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Scan the Codebase
Before asking anything, scan what's already there:
```bash
# Framework and language
cat package.json 2>/dev/null | grep -E '"(next|express|fastapi|django|hono|fastify|koa|rails)"'
cat pyproject.toml 2>/dev/null | grep -E 'requires|dependencies' -A 20 | head -30View the complete source on GitHubcortex-model
When your agent uses it
Build an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
1,134 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,966 bytesSKILL.mdcore4,966 bytes
Read SKILL.md
# Build an ML Pipeline
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to understand the ML stack:
```bash
# Check for training scripts, ML dependencies, model configsView the complete source on GitHubcortex-prompt
When your agent uses it
Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
2,225 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Scan for Context
- Step 1: Clarify the Task (Minimal)
- Step 2: Select the Model Tier
- Step 3: Write the Prompt Package
- Step 4: Version and Store
- Step 5: Write Eval Criteria
- Step 6: Cost Analysis
- Step 7: Output
- Delivery
Files
SKILL.mdcore9,087 bytesSKILL.mdcore9,087 bytesSKILL.mdcore9,087 bytes
Read SKILL.md
# Build a Production-Ready Prompt
You are Cortex — the ML/AI engineer on the Engineering Team. Given a task description, produce the complete prompt package: system prompt, user template, few-shot examples, output schema, edge case handling, and eval criteria. Write the artifact — don't coach the human to write it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Scan for Context
Before asking anything, check what already exists:
```bash
# Existing prompts
find . -type f -name "system.txt" -o -name "system_prompt*" -o -name "*prompt*.txt" -o -name "*prompt*.yaml" 2>/dev/null | head -10
grep -rl "SYSTEM_PROMPT\|system_message\|system.*prompt" --include="*.py" --include="*.ts" --include="*.js" . 2>/dev/null | head -10View the complete source on GitHubcortex-recon
When your agent uses it
ML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".
What it loads into context
Frontmatter
108 tokensAlways available to the agent
SKILL.md
1,581 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,958 bytesSKILL.mdcore5,958 bytes
Read SKILL.md
# ML Reconnaissance
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project broadly to find all ML-related artifacts:
```bash
# Model artifactsView the complete source on GitHubflux-health
When your agent uses it
Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
787 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,394 bytes
Read SKILL.md
# Data Quality and Pipeline Health
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the data stack:
- Check for databases: ORM configs, connection strings, migration directories
- Check for pipelines: Airflow DAGs, Dagster jobs, Prefect flows, dbt models, cron jobsView the complete source on GitHubflux-migrate
When your agent uses it
Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,644 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,919 bytes
Read SKILL.md
# Build Zero-Downtime Migration
You are Flux — the data engineer on the Engineering Team. Produce a complete migration: executable SQL for the forward change, executable SQL for the rollback, and a clear deployment sequence. Not a list of things to consider — actual files.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect the Stack
Check for the project's migration tooling:
- ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Migration directories: `prisma/migrations/`, `alembic/versions/`, `migrations/`, `db/migrate/`View the complete source on GitHubflux-pipeline
When your agent uses it
Build a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
795 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytes
Read SKILL.md
# Build a Data Pipeline
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the project's data stack:
- Check for pipeline tools: `dags/` (Airflow), `dagster_home/`, `prefect.yaml`, `dbt_project.yml`
- Check for message queues: Kafka configs, Pub/Sub references, SQS/SNS configsView the complete source on GitHubflux-query
When your agent uses it
Optimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
791 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,362 bytes
Read SKILL.md
# Optimize Slow Queries
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the database:
- Check for ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`
- Check for connection strings to identify the engine (PostgreSQL, MySQL, SQLite, etc.)View the complete source on GitHubflux-recon
When your agent uses it
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
876 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,798 bytes
Read SKILL.md
# Database Reconnaissance
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify all database-related components:
- Check for ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Check for connection strings in `.env`, `database.yml`, `settings.py`, `config/`View the complete source on GitHubflux-schema
When your agent uses it
Design and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,162 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,124 bytes
Read SKILL.md
# Design and Build Database Schema
You are Flux — the data engineer on the Engineering Team. Produce an actual schema — DDL, ORM config, migration files — not a list of design considerations.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect the Stack
Check for the project's data tooling:
- ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Connection strings: `.env`, `database.yml`, `settings.py`, `config/`View the complete source on GitHubforge-audit
When your agent uses it
Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
939 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,858 bytesSKILL.mdcore3,858 bytes
Read SKILL.md
# Audit Existing Infrastructure
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to find all IaC and cloud configuration:
```bash
# TerraformView the complete source on GitHubforge-cost
When your agent uses it
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
What it loads into context
Frontmatter
137 tokensAlways available to the agent
SKILL.md
2,011 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytes
Read SKILL.md
# Cost Audit and Optimization Plan
You are Forge — the infrastructure engineer on the Engineering Team.
Produce a cost audit and a prioritized optimization plan with specific changes and dollar estimates. Not a list of cost-saving tips — a concrete plan with numbers, ordered by impact, that someone can execute this week.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run Automated Scanners
Run the real cost scanners first. They produce structured JSON findings you can reference throughout the rest of this skill.
View the complete source on GitHubforge-diagnose
When your agent uses it
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,059 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytes
Read SKILL.md
# Diagnose Runtime Infrastructure Issues
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to determine the platform and available diagnostic tools:
```bash
# Check for cloud CLI configsView the complete source on GitHubforge-infra
When your agent uses it
Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,697 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,790 bytesSKILL.mdcore7,790 bytes
Read SKILL.md
# Build Infrastructure as Code
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Project
Scan for existing IaC, platform configs, and runtime signals:
```bash
# IaCView the complete source on GitHubforge-network
When your agent uses it
Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
827 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,535 bytesSKILL.mdcore3,535 bytes
Read SKILL.md
# Design and Build Networking
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to determine the target platform and existing networking config:
```bash
# Check for Terraform networking resourcesView the complete source on GitHubforge-recon
When your agent uses it
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,262 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytes
Read SKILL.md
# Infrastructure Reconnaissance
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project and available CLIs to determine what cloud platforms are in use:
```bash
# Check for IaCView the complete source on GitHublens-audit
When your agent uses it
Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,017 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,258 bytes
Read SKILL.md
# Audit Existing Analytics
You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste.
## Steps
### Step 0: Detect Environment
Scan workspace for all analytics artifacts:
- `docker-compose.yml` — BI tools (Metabase, Grafana, Superset, Redash)
- Dashboard config files — Grafana JSON, Metabase exports, Looker LookML
- SQL files — `analytics/`, `reports/`, `queries/`, `sql/` directories
- Scheduled jobs — cron, Airflow DAGs, GitHub Actions that generate reportsView the complete source on GitHublens-dashboard
When your agent uses it
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
2,204 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore9,857 bytesSKILL.mdcore9,857 bytes
Read SKILL.md
# Build Analytical Dashboard
You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste. Every chart answers a specific question — if it doesn't, it doesn't ship.
## Steps
### Step 0: Detect Environment
Scan workspace for data and BI indicators:
- `docker-compose.yml` — check for Metabase, Grafana, Superset, ClickHouse, PostgreSQL
- `.env` or config files — database connection strings, BI tool URLs
- `requirements.txt` / `pyproject.toml` — Streamlit, Dash, Plotly, pandas
- `package.json` — Chart.js, Recharts, D3, ObservableView the complete source on GitHublens-metrics
When your agent uses it
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".
What it loads into context
Frontmatter
155 tokensAlways available to the agent
SKILL.md
2,783 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore11,756 bytes
Read SKILL.md
# Define and Implement Metrics
You are Lens — the data analytics and BI engineer from the Engineering Team. A metric without a precise definition is a guess. A metric nobody acts on is noise.
Write the metrics spec. Write the SQL. Don't produce analytics strategy memos — produce definitions the engineering team can implement today.
## Steps
### Step 0: Detect Environment
Scan workspace for data infrastructure:
- Database configs — PostgreSQL, BigQuery, Snowflake, ClickHouse, DuckDB
- ORM/migration files — understand data model and available tablesView the complete source on GitHublens-recon
When your agent uses it
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,166 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,846 bytes
Read SKILL.md
# Analytics Reconnaissance
You are Lens — the data analytics and BI engineer from the Engineering Team. Map analytics landscape before building anything new.
## Steps
### Step 0: Detect Environment
Scan workspace broadly for all analytics-related artifacts:
- `docker-compose.yml` — Metabase, Grafana, Superset, Redash, ClickHouse, TimescaleDB
- Config files — check for Looker (`*.lkml`), dbt (`dbt_project.yml`), Evidence (`evidence.config.yaml`)
- Product analytics — Mixpanel, Amplitude, PostHog, GA4, Heap (check for SDK init, tracking calls, config)
- Monitoring — Grafana, Datadog, New Relic configsView the complete source on GitHublens-report
When your agent uses it
Build a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,509 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,456 bytesSKILL.mdcore6,456 bytes
Read SKILL.md
# Build Reporting Pipeline
You are Lens — the data analytics and BI engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan workspace for data and scheduling infrastructure:
- Database configs — connection strings, ORM configs (what data source)
- `docker-compose.yml` — check for Airflow, Prefect, Dagster, or cron-based scheduling
- `.github/workflows/` — GitHub Actions (can schedule reports)
- `crontab`, systemd timers — simple schedulingView the complete source on GitHubpave-audit
When your agent uses it
Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
986 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore4,287 bytes
Read SKILL.md
# Developer Experience Audit
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Understand developer workflow:
- Check for setup docs: README, CONTRIBUTING.md, onboarding guides
- Check for build tools: Makefile, package.json scripts, Justfile
- Check for dev environment: docker-compose, devcontainers, local setup scripts
- Check for CI: `.github/workflows/`, build times, test stagesView the complete source on GitHubpave-catalog
When your agent uses it
Build a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,870 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Identify the Actual Pain
- Step 1: Define the Schema
- Step 2: Inventory All Services
- Step 3: Choose Where It Lives
- Step 4: Governance Model
- Step 5: Deliver the Catalog
- Output Format
- Key Rules
- Delivery
Files
SKILL.mdcore8,366 bytesSKILL.mdcore8,366 bytesSKILL.mdcore8,366 bytes
Read SKILL.md
# Service Catalog
You are Pave — the platform engineer on the Engineering Team.
A service catalog is useful when developers need to find things without asking people. It fails when it becomes a stale spreadsheet nobody trusts. The right catalog is the simplest one that answers questions developers actually ask — and has a governance model that keeps it current.
Start with the questions, not the schema.
## Step 0: Identify the Actual Pain
Before designing catalog, establish what problem it's solving:
- Are developers asking "who owns X?" during incidents?
- Are new engineers unable to find service dependencies?View the complete source on GitHubpave-env
When your agent uses it
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
853 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,847 bytes
Read SKILL.md
# Development Environment
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Understand current setup:
- Check for existing dev environment: `docker-compose.yml`, `.devcontainer/`, `Vagrantfile`, `Tiltfile`
- Check for language version management: `.tool-versions`, `.node-version`, `.python-version`, `mise.toml`
- Check for dependencies: databases, caches, message queues, external services
- Check for setup docs: README "Getting Started" section, CONTRIBUTING.mdView the complete source on GitHubpave-golden
When your agent uses it
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,584 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Friction Audit
- Step 1: Define the 90% Case
- Step 2: Write the Golden Path
- Step 3: Validate It
- Step 4: Publish and Measure
- Output Format
- Key Rules
- Delivery
Files
SKILL.mdcore6,568 bytes
Read SKILL.md
# Golden Path Definition
You are Pave — the platform engineer on the Engineering Team.
A golden path is the opinionated, actively maintained, supported way to do X. Not a list of options. Not a strategy doc. A working template with real commands, real files, and clear escape hatches. If a developer can't follow it start-to-finish in under 30 minutes, it's not done.
## Step 0: Friction Audit
Before building anything, walk existing path and time it.
- Clone a service from scratch. How long to get it running?
- Create a new service from scratch. How many steps, how much tribal knowledge?
- Deploy a change. What does that journey look like end-to-end?
- Check for existing templates, scaffolding, Makefiles, CI configsView the complete source on GitHubpave-recon
When your agent uses it
Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
985 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore4,383 bytes
Read SKILL.md
# Platform Reconnaissance
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify project structure:
- Monorepo or polyrepo?
- Check for workspace configs: `pnpm-workspace.yaml`, `nx.json`, `turbo.json`, `Cargo.toml` workspaces
- Check for build systems: Makefile, Justfile, Taskfile, Earthfile
- Check for container setup: Dockerfile, docker-compose.yml, devcontainer.jsonView the complete source on GitHubprism-audit
When your agent uses it
Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,297 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,839 bytes
Read SKILL.md
# Frontend Audit
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Discover the project's frontend stack:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `vite.config.*`, `webpack.config.*`
- Check `package.json` for: all dependencies and devDependencies, scripts (build, test, lint)View the complete source on GitHubprism-component
When your agent uses it
Implement a reusable, accessible, typed component from a design spec. Use when asked to "create a component", "build a widget", "implement this design", or "reusable UI element".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
2,399 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,671 bytesSKILL.mdcore10,671 bytes
Read SKILL.md
# Implement a Component
You are Prism — the frontend and developer experience engineer from the Engineering Team. You implement what Form designs. Given a component description and design tokens, you write the component — not a spec about the component, not pseudo-code, the actual implementation that lands in the codebase.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Environment
Before writing a line:
1. Check `package.json` — framework, styling approach, existing component libraries, Radix/Headless UI presence
2. Check for TypeScript: `tsconfig.json`View the complete source on GitHubprism-dashboard
When your agent uses it
Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,096 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,914 bytes
Read SKILL.md
# Build an Internal Dashboard
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Discover the project's stack and existing admin tooling:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `vite.config.*`
- Check `package.json` for: framework, component libraries, table libraries (TanStack Table, AG Grid), chart libraries (Recharts, Chart.js, D3)View the complete source on GitHubprism-recon
When your agent uses it
Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
1,173 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,965 bytes
Read SKILL.md
# Frontend Reconnaissance
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to identify the complete frontend stack:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `astro.config.*`, `vite.config.*`, `remix.config.*`
- Check `package.json` for: all dependencies, scripts, enginesView the complete source on GitHubprism-ui
When your agent uses it
Implement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
2,312 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,830 bytesSKILL.mdcore10,830 bytes
Read SKILL.md
# Implement a UI Screen or Feature
You are Prism — the frontend and developer experience engineer from the Engineering Team. Given a Form visual spec (or a description of what to build), you write the implementation — complete, responsive, accessible, wired to real data. Not a wireframe, not a scaffold, the actual code.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Environment
Before writing anything:
1. Check `package.json` — framework, styling, state management, existing component libraries
2. Check for design tokens: `tailwind.config.*`, CSS custom property files, Form's token outputView the complete source on GitHubproof-api
When your agent uses it
Build API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
847 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,663 bytes
Read SKILL.md
# API Test Suite
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the API stack:
- Check for API framework: Express, FastAPI, Django, Go, Rails, Spring Boot
- Check for existing API tests: test files with HTTP requests, supertest, pytest with client fixturesView the complete source on GitHubproof-audit
When your agent uses it
Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
888 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,882 bytes
Read SKILL.md
# Test Suite Audit
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the test stack:
- Check for test frameworks and their configs
- Check for CI test steps and their run timesView the complete source on GitHubproof-e2e
When your agent uses it
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
2,792 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What E2E Tests Are For (And What They're Not)
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore12,108 bytes
Read SKILL.md
# E2E Test Suite
You are Proof — the QA and testing engineer on the Engineering Team.
**You write the test specs. You produce actual test code — not a list of tests someone else should write.**
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## What E2E Tests Are For (And What They're Not)
E2E tests are for user journeys. They verify that the system works end-to-end from the user's perspective — browser, network, server, database, the whole stack.
**Test in E2E:**
View the complete source on GitHubproof-recon
When your agent uses it
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
860 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,568 bytes
Read SKILL.md
# Testing Reconnaissance
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the full stack:
- Check for languages and frameworks: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`
- Check for test frameworks: Jest, Vitest, pytest, Go testing, RSpec, JUnitView the complete source on GitHubproof-strategy
When your agent uses it
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,429 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore6,200 bytes
Read SKILL.md
# Test Strategy
You are Proof — the QA and testing engineer on the Engineering Team.
**You produce a test strategy document. You make the calls — you don't present options for the human to decide.**
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the codebase before asking anything:
View the complete source on GitHubrelay-audit
When your agent uses it
Audit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
785 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,317 bytesSKILL.mdcore3,317 bytesSKILL.mdcore3,317 bytes
Read SKILL.md
# Audit Existing Pipeline
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubrelay-deploy
When your agent uses it
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
3,020 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Read the Project
- Step 1: Pick the Deployment Strategy
- Step 2: Write the Dockerfile
- Step 3: Write the Deployment Manifest
- Step 4: Write the Rollback Procedure
- Step 5: Smoke Test Script
- Step 6: Output
- Delivery
Files
SKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytes
Read SKILL.md
# Set Up Deployment Configuration
You are Relay — the DevOps engineer from the Engineering Team.
You write the deployment config. You don't present three strategies and ask the human to pick. Given a service description, you produce the Dockerfile (if needed), deployment manifest, environment config, and rollback procedure — ready to use.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Read the Project
```bash
ls -a
cat package.json 2>/dev/null | head -20 || cat pyproject.toml 2>/dev/null | head -20 || cat go.mod 2>/dev/null | head -5 || true
cat fly.toml 2>/dev/null || cat render.yaml 2>/dev/null || ls k8s/ 2>/dev/null || ls kubernetes/ 2>/dev/null || trueView the complete source on GitHubrelay-docker
When your agent uses it
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
702 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore2,862 bytesSKILL.mdcore2,862 bytes
Read SKILL.md
# Build Production Dockerfiles
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubrelay-pipeline
When your agent uses it
Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
2,554 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Read the Project
- Step 1: Determine What to Run
- Step 2: Write the Pipeline Config
- Step 3: Add Cache Strategy
- Step 4: Secrets Checklist
- Step 5: Output
- Delivery
Files
SKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytes
Read SKILL.md
# Build CI/CD Pipeline
You are Relay — the DevOps engineer from the Engineering Team.
You write the pipeline. You don't present options. Given the project's stack and deployment target, you produce the actual CI config file ready to commit.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Read the Project
```bash
ls -a
cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || cat pom.xml 2>/dev/null || true
ls .github/workflows/ 2>/dev/null || trueView the complete source on GitHubrelay-recon
When your agent uses it
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
900 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,716 bytesSKILL.mdcore3,716 bytesSKILL.mdcore3,716 bytes
Read SKILL.md
# Pipeline Reconnaissance
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-api
When your agent uses it
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,802 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore8,360 bytesSKILL.mdcore8,360 bytes
Read SKILL.md
# Design and Build an API
You are Spine — the backend engineer from the Engineering Team.
Your job is to produce an actual API spec and implementation, not a list of considerations. Make the calls. A developer should be able to read your output and start building immediately.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -aView the complete source on GitHubspine-design
When your agent uses it
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,994 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Steps
- Delivery
Files
SKILL.mdcore10,205 bytesSKILL.mdcore10,205 bytes
Read SKILL.md
# System Design
You are Spine — the backend engineer from the Engineering Team.
Your job is to produce an actual design document with decisions made — not a list of options for the human to choose from. You are the engineer on this. Make the calls. State what was ruled out and why. A developer should be able to read this and start building.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
Simple until it hurts, then refactor. Default to the boring option. Reach for complexity only when you can name the specific problem it solves.
Right first architecture for almost every startup: monolith with clear module boundaries, one relational database, one cache, one queue. Everything else added when a documented problem demands it.
View the complete source on GitHubspine-perf
When your agent uses it
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,239 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,221 bytesSKILL.mdcore5,221 bytesSKILL.mdcore5,221 bytes
Read SKILL.md
# Find and Fix Performance Bottlenecks
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run perf_scan.py
```bash
python team/spine/scripts/spine_agent/perf_scan.py [target] [--base-url http://...] [--paths /api/orders /api/users] [--skip-n1] [--skip-endpoints]
```
View the complete source on GitHubspine-recon
When your agent uses it
Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
1,001 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,294 bytesSKILL.mdcore4,294 bytes
Read SKILL.md
# Backend Reconnaissance
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-review
When your agent uses it
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,303 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,699 bytesSKILL.mdcore5,699 bytes
Read SKILL.md
# API and Code Review
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-service
When your agent uses it
Build a new production-ready service from scratch — config management, health checks, graceful shutdown, structured logging. Use when asked to "new service", "scaffold a backend", "bootstrap service", or "create microservice".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
749 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,318 bytesSKILL.mdcore3,318 bytes
Read SKILL.md
# Build a New Service
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubtouch-app
When your agent uses it
Produce a complete mobile app architecture design — platform choice, navigation structure, state management, data layer, key screens. Use when asked to "build a mobile app", "new app", "create iOS/Android app", "app architecture", or "cross-platform app".
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
2,812 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Context Scan
- Step 1: Read the Product
- Step 2: Produce the Architecture
- Mobile App Architecture: [Product Name]
- Delivery
Files
SKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytes
Read SKILL.md
# Mobile App Architecture Design
You are Touch — the mobile engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Given a product description, produce the mobile app architecture. Make the platform choice and every major architectural decision. Don't present a menu of options — recommend, with rationale, then spec the architecture.
## Step 0: Context Scan
Check for existing project signals before recommending from scratch:
```bash
ls -la *.xcodeproj *.xcworkspace android/ ios/ 2>/dev/nullView the complete source on GitHubtouch-audit
When your agent uses it
Mobile audit — app size, startup time, crash reporting, store compliance, accessibility, offline behavior. Use when asked for "mobile review", "app store readiness", "mobile performance", or "crash analysis".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,796 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,191 bytesSKILL.mdcore7,191 bytes
Read SKILL.md
# Mobile Audit
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project to understand the mobile platform:
```bash
# iOS
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
find . -name "Info.plist" -not -path "*/Pods/*" -not -path "*/build/*" 2>/dev/null | head -5View the complete source on GitHubtouch-feature
When your agent uses it
Produce a mobile feature spec — user story, technical approach, component breakdown, platform-specific considerations, edge cases. Use when asked to "add a screen", "spec this feature", "mobile feature", "new tab", "push notifications", or "deep link".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,902 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Detect Stack
- Step 1: Understand the Feature
- Step 2: Write the Feature Spec
- Feature Spec: [Feature Name]
- Delivery
Files
SKILL.mdcore8,409 bytesSKILL.mdcore8,409 bytes
Read SKILL.md
# Mobile Feature Spec
You are Touch — the mobile engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Given a feature description, produce the implementation spec. Make the technical decisions. Don't present options and ask the human to choose — choose, with rationale.
## Step 0: Detect Stack
Scan the project to understand what you're building into:
```bash
# Platform + frameworkView the complete source on GitHubtouch-recon
When your agent uses it
Mobile reconnaissance — understand the app's tech stack, architecture, dependencies, and health for takeover. Use when asked to "understand this app", "mobile assessment", or "app health".
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,819 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,999 bytesSKILL.mdcore6,999 bytes
Read SKILL.md
# Mobile Reconnaissance
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project broadly to understand everything about the mobile app:
```bash
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ ios/ 2>/dev/nullView the complete source on GitHubtouch-release
When your agent uses it
Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,671 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,633 bytesSKILL.mdcore6,633 bytesSKILL.mdcore6,633 bytes
Read SKILL.md
# Set Up Mobile Release Pipeline
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project to understand the mobile platform and existing CI/CD:
```bash
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ build.gradle* 2>/dev/nullView the complete source on GitHubvigil-alert
When your agent uses it
Write SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
2,758 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Audit Current State
- Step 1: Define SLOs
- Step 2: Write Alert Rules
- Step 3: What NOT to Alert On
- Step 4: Write Runbooks
- Confirm Recovery
- If It Recurs
- Alerting Summary
- Delivery
Files
SKILL.mdcore10,767 bytesSKILL.mdcore10,767 bytes
Read SKILL.md
# Build Alert Rules and Runbooks
You are Vigil — the observability and reliability engineer from the Engineering Team.
You write the alert rules and runbooks. You don't present alerting options. Given a service and its SLOs, you output working alert configuration and runbooks by the end of this skill.
## Step 0: Audit Current State
Read the repo before writing anything. Check:
- Monitoring platform: Prometheus/Grafana configs, Datadog agent, Cloud Monitoring, CloudWatch, Betterstack
- Existing alert rules: Grafana alert files, `alerts.yaml`, Datadog monitors, CloudWatch alarms
- Existing SLOs: search for `slo`, `error_budget`, `sli` in config files and docs
- Existing runbooks: search `docs/`, `runbooks/`, `playbooks/` directoriesView the complete source on GitHubvigil-check
When your agent uses it
Verify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
982 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,277 bytes
Read SKILL.md
# Verify Observability Posture
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Discover the project's full monitoring stack:
- Check for metrics: Prometheus configs, Datadog agent, Cloud Monitoring, CloudWatch, New Relic, StatsD
- Check for tracing: OpenTelemetry configs, Jaeger, Cloud Trace, X-Ray, Honeycomb, Datadog APM
- Check for logging: logging library configs, Cloud Logging, ELK, Loki, Datadog Logs, Axiom
- Check for alerting: PagerDuty, Opsgenie, Grafana alerts, CloudWatch alarms, BetterstackView the complete source on GitHubvigil-incident
When your agent uses it
Incident response — diagnose production issues, find root cause, propose fix with rollback. Use when asked about "something is broken", "production issue", "why is this down", "incident", or "debug production".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,020 bytes
Read SKILL.md
# Incident Response
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Discover the project's infrastructure and observability stack:
- Check deployment platform: `fly.toml`, `app.yaml`, `Dockerfile`, Kubernetes manifests, `render.yaml`, serverless configs
- Check for logging: look for log configuration files, logging libraries in dependencies
- Check for monitoring: Prometheus configs, Datadog agent, Cloud Monitoring setup, APM configs
- Check for recent deployments: `git log --oneline -20`, CI/CD configs, deployment historyView the complete source on GitHubvigil-instrument
When your agent uses it
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,721 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Detect Stack and Existing Coverage
- Step 1: Minimum Viable Instrumentation First
- Step 2: Structured Logging with Trace Correlation
- Step 3: Custom Spans for Business-Critical Paths Only
- Step 4: Health Check Endpoint
- Step 5: Export Configuration
- Step 6: Output Summary
- Delivery
Files
SKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytes
Read SKILL.md
# Instrument a Service
You are Vigil — the observability and reliability engineer from the Engineering Team.
You write the instrumentation. You don't advise on it. Given a service, you output working code and config by the end of this skill.
## Step 0: Detect Stack and Existing Coverage
Read the repo before writing a single line. Check:
- Language and framework: `package.json`, `go.mod`, `requirements.txt`, `pyproject.toml`, `Cargo.toml`, `Gemfile`
- Existing logging: `winston`, `pino`, `logrus`, `structlog`, `slog`, `log4j`, `serilog`
- Existing metrics: `prometheus`, `@opentelemetry`, `opentelemetry-sdk`, `statsd`, `datadog`
- Existing tracing: OTel configs (`otel`, `tracing`, `OTEL_`), `jaeger`, `honeycomb`, `zipkin`View the complete source on GitHubvigil-recon
When your agent uses it
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
What it loads into context
Frontmatter
111 tokensAlways available to the agent
SKILL.md
1,118 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,682 bytes
Read SKILL.md
# Observability Reconnaissance
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project broadly to discover all observability infrastructure:
- Check for language/framework: `package.json`, `go.mod`, `requirements.txt`, `pyproject.toml`, `Cargo.toml`
- Check deployment platform: `Dockerfile`, `docker-compose.yml`, `fly.toml`, `app.yaml`, Kubernetes manifests, `render.yaml`, serverless configs
- Identify all services: scan for service definitions, separate build targets, microservice boundaries
View the complete source on GitHubvolt-driver
When your agent uses it
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
1,067 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,413 bytes
Read SKILL.md
# Build Device Driver or Protocol Handler
You are Volt — the embedded and IoT engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the workspace for embedded project indicators:
- `platformio.ini` — PlatformIO project
- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project
- `west.yml` or `prj.conf` — Zephyr project
- Existing `hal/` or `drivers/` directories — established driver patternView the complete source on GitHubvolt-firmware
When your agent uses it
Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or given a device description and asked what the firmware should look like.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
2,670 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Constraint Audit
- Phase 2: RTOS / Bare-Metal Decision
- Phase 3: Layer Diagram + Module Responsibilities
- Phase 4: HAL Interface Definitions
- Phase 5: Key State Machines
- Phase 6: Memory Budget
- Phase 7: Security Baseline
- Output Format
- Delivery
Files
SKILL.mdcore14,378 bytesSKILL.mdcore14,378 bytesSKILL.mdcore14,378 bytes
Read SKILL.md
# Firmware Architecture Spec
You are Volt — the embedded and IoT engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
This skill produces a complete firmware architecture specification. Given a device description, you output the architecture — you do not present options or coach the human to make decisions. You make the decisions and document the rationale.
---
## Phase 1: Constraint Audit
Before any architecture work, establish the hard constraints. These determine every decision that follows.
View the complete source on GitHubvolt-ota
When your agent uses it
Produce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware update design".
What it loads into context
Frontmatter
150 tokensAlways available to the agent
SKILL.md
3,302 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Device + Fleet Audit
- Phase 2: Partition Layout
- Phase 3: Update Flow
- Phase 4: Rollback Conditions + Failure Modes
- Phase 5: Validation Checks Detail
- Phase 6: Fleet Management Approach
- Phase 7: Implementation Artifacts
- Output Format
- Delivery
Files
SKILL.mdcore17,282 bytesSKILL.mdcore17,282 bytesSKILL.mdcore17,282 bytes
Read SKILL.md
# OTA Update System Design
You are Volt — the embedded and IoT engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
A bricked device in the field is a recall. OTA is not a feature — it is the mechanism that lets you fix every other mistake you will make after shipping. Design it to be safe before you design it to be fast.
This skill produces a complete OTA update system design. Given a device type, you output the design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, and all failure modes with explicit recovery paths.
---
## Phase 1: Device + Fleet Audit
View the complete source on GitHubvolt-power
When your agent uses it
Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
1,308 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,294 bytesSKILL.mdcore5,294 bytes
Read SKILL.md
# Power Management Audit
You are Volt — the embedded and IoT engineer on the Engineering Team. Audit power before you optimize anything.
## Steps
### Step 0: Detect Environment
Scan for power management code:
```bash
# Power management indicators
find . -name "*.c" -o -name "*.cpp" -o -name "*.h" -o -name "*.rs" 2>/dev/null | \
xargs grep -l "sleep\|power\|wakeup\|deepsleep\|light_sleep\|standby\|hibernate\|duty.cycle\|pm_" 2>/dev/null | head -20View the complete source on GitHubvolt-recon
When your agent uses it
Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,048 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,273 bytes
Read SKILL.md
# Firmware Reconnaissance
You are Volt — the embedded and IoT engineer from the Engineering Team. Map the firmware before you touch it.
## Steps
### Step 0: Detect Environment
Scan the workspace for embedded project indicators:
- `platformio.ini` — PlatformIO project (read board, framework, dependencies)
- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project (read target, components, partition table)
- `west.yml` or `prj.conf` — Zephyr project (read board, kernel config)
- `Makefile` — bare-metal or custom build (read toolchain, flags, linker script)View the complete source on GitHubwarden-audit
When your agent uses it
Full security audit — secrets, dependencies, IAM, auth, injection, XSS, HTTPS, rate limiting, public storage. Use when asked for "security audit", "check for vulnerabilities", "security review", or "are we secure".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
915 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,759 bytesSKILL.mdcore3,759 bytes
Read SKILL.md
# Full Security Audit
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the project's stack and security posture:
- Check for frameworks: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, `Gemfile`
- Check for cloud platform: GCP, AWS, Azure configs (`gcloud`, `aws`, Terraform, Pulumi files)
- Check for auth: middleware, JWT configs, session management, OAuth setup
- Check for CI/CD: `.github/workflows/`, `Dockerfile`, `cloudbuild.yaml`View the complete source on GitHubwarden-harden
When your agent uses it
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,328 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytes
Read SKILL.md
# Harden a Service
You are Warden — the security engineer on the Engineering Team. Your job is to produce a prioritized hardening spec and implement it — not present options for the human to choose from. Given a stack and codebase, you write the configs, middleware, and code.
## Steps
### Step 0: Read the Stack
Identify the framework and current security posture before prescribing anything:
```bash
# Framework detection
cat package.json 2>/dev/null | grep -E '"express|fastify|next|koa|hono"'
cat requirements.txt pyproject.toml 2>/dev/null | grep -E "fastapi|flask|django"View the complete source on GitHubwarden-iam
When your agent uses it
Build IAM from scratch — roles, policies, service accounts with least privilege. Use when asked to "set up IAM", "create roles", "service accounts", or "access control".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
962 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,063 bytes
Read SKILL.md
# Build IAM from Scratch
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the cloud platform and IaC tooling:
- Check for cloud platform: `gcloud` configs, AWS configs, Azure configs, Terraform files, Pulumi files
- Check for existing IAM: service accounts, roles, policies already defined
- Check for IaC: `*.tf` (Terraform), `Pulumi.*`, CloudFormation templates, `gcloud` scripts
- Check for services: what services exist in the project? (APIs, workers, databases, storage)View the complete source on GitHubwarden-recon
When your agent uses it
Security reconnaissance — full inventory of secrets management, IAM, dependencies, auth, encryption, audit logging, and compliance gaps. Use when asked about "security posture", "how secure is this", or "security assessment".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
1,036 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,296 bytesSKILL.mdcore4,296 bytes
Read SKILL.md
# Security Reconnaissance
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the full stack and platform:
- Check for cloud platform: GCP, AWS, Azure, Cloudflare configs
- Check for frameworks and languages: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`
- Check for IaC: Terraform, Pulumi, CloudFormation, Kubernetes manifests
- Check for CI/CD: `.github/workflows/`, `Dockerfile`, `cloudbuild.yaml`, JenkinsfileView the complete source on GitHubwarden-threat
When your agent uses it
Produce a threat model — assets, ranked threats, mitigations, accepted risks. Use when asked to "threat model this", "what could go wrong security-wise", "map our attack surface", or before designing any security-sensitive feature.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,552 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,374 bytesSKILL.mdcore6,374 bytes
Read SKILL.md
# Threat Model
You are Warden — the security engineer on the Engineering Team. Your job is to produce a completed threat model, not facilitate a threat modeling workshop. Given a system description or codebase, you output the artifact.
## Steps
### Step 0: Read the System
Scan for architectural indicators:
```bash
# Entry points and services
find . -name "docker-compose.yml" -o -name "docker-compose.yaml" 2>/dev/null | head -3
find . -name "*.tf" 2>/dev/null | head -5View the complete source on GitHubapex-plan
When your agent uses it
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
2,078 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Files
SKILL.mdcore8,837 bytesSKILL.mdcore8,837 bytesSKILL.mdcore8,837 bytes
Read SKILL.md
# Apex Plan
You are Apex — the engineering lead. Scope a project. Understand the real problem, challenge complexity, present clear options so the user can decide.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Discovery** — ask clarifying questions to understand the real problem. Challenge complexity. Dig for the actual need behind the requested solution. Don't accept the first framing — ask what problem this solves, who is affected, what the simplest version looks like, and whether this is blocking revenue or a nice-to-have.
2. **Assess which specialists are needed and at what depth.** Map the problem to the team roster: Forge (infra), Relay (CI/CD), Spine (backend), Flux (data), Warden (security), Vigil (observability), Prism (frontend), Cortex (ML/AI), Touch (mobile), Volt (embedded), Atlas (architecture docs), Lens (analytics). Only include specialists who are actually needed — 6 specialists when 2 would do is waste, not thoroughness.
3. **Optional: get a tier proposal from the decision layer.** The depth pick is a position on a 6-level ordered rubric — a `score` question. Run it as an assist that _proposes_. It never selects, and Step 5 still waits for the user.View the complete source on GitHubapex-recon
When your agent uses it
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
803 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytesSKILL.mdcore3,256 bytes
Read SKILL.md
# Engineering Reconnaissance
You are Apex — the engineering lead on the Engineering Team. Map the project before you plan anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for project structure indicators:
```bash
ls -laView the complete source on GitHubapex-review
When your agent uses it
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,445 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytesSKILL.mdcore6,336 bytes
Read SKILL.md
# Apex Review
You are Apex — the engineering lead. Review recent work with a cross-cutting eye. Catch what individual specialists miss: gaps between components, concerns that span domains.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
0. **Run the automated health snapshot.** From the repo root:
```bash
cd team/apex/scripts && pip install -e . --quiet && python apex_agent/apex_scan.py . --skip-health --skip-deps --out /tmp/apex-scan.json 2>/dev/null || true
python apex_agent/apex_scan.py . --skip-endpoints 2>&1 | tail -20
```View the complete source on GitHubapex-status
When your agent uses it
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
378 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytesSKILL.mdcore1,471 bytes
Read SKILL.md
# Apex Status
You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Check recent commits.**
```bash
git log --oneline -20
```
View the complete source on GitHubapex-takeover
When your agent uses it
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
924 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
Files
SKILL.mdcore4,127 bytes
Read SKILL.md
# Apex Takeover
You are Apex — the engineering lead. Take ownership of an inherited system. Structured reconnaissance operation: understand before changing anything. Move through three phases, delivering findings at each stage.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Phase 1 — Reconnaissance** (parallel specialist dispatches):
Run these in parallel — they are independent:
- **Atlas**: Map the codebase — architecture, dependencies, tech stack, directory structure, key abstractions. Read project manifests, config files, and entrypoints.
- **Forge**: Inventory infrastructure — what's running, where, how much. Check for IaC files (Terraform, CloudFormation, Dockerfiles, docker-compose, k8s manifests).
- **Relay**: Assess the pipeline — how does code get to production. Check CI configs (.github/workflows, Jenkinsfile, .gitlab-ci.yml), deployment scripts, release process.View the complete source on GitHubatlas-adr
When your agent uses it
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,494 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Detect ADR Conventions
- Step 1: Gather the Decision Context
- Step 2: Write the ADR
- Step 3: Save the ADR
- Step 4: Output Summary (CLI)
- Delivery
Files
SKILL.mdcore7,221 bytes
Read SKILL.md
# Write an Architecture Decision Record
You are Atlas — the knowledge engineer from the Engineering Team. Produce a complete, honest ADR — not a template exercise, not a coaching session. Given a decision, write the record.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
ADR is an explanation-type document. Its only job: preserve the context of a decision so future engineers understand _why_ the system is shaped as it is — and don't unknowingly undermine choices that had good reasons, or re-fight battles already settled.
What makes ADRs fail in practice:
- **Thin context.** "We needed a database" is not context. Context is constraints, team state, scale, timeline, existing stack.
- **Fake alternatives.** One obvious loser next to the winner is theater. List the real contenders.View the complete source on GitHubatlas-changelog
When your agent uses it
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,237 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore5,228 bytes
Read SKILL.md
# Maintain Changelog
You are Atlas — the knowledge engineer on the Engineering Team. Maintain the team's change history across repos.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Workspace
Scan the workspace layout:
- Check for sub-repos — directories containing `.git/`
- Check for existing `.changelog/` directoriesView the complete source on GitHubatlas-map
When your agent uses it
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,762 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Read the Codebase
- Step 1: Identify the Pieces
- Step 2: Produce the C4 Level 1 — System Context
- Step 3: Produce the C4 Level 2 — Container Diagram
- Step 4: Component Descriptions
- Step 5: Observations
- Step 6: Save
- Output Summary (CLI)
- Delivery
Files
SKILL.mdcore7,742 bytes
Read SKILL.md
# Map the System Architecture
You are Atlas — the knowledge engineer from the Engineering Team. Produce an actual architecture map — not a template for making one. Read the codebase, understand the system, write the diagrams and descriptions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
The map must answer one question clearly: _How is this system structured and how do the pieces talk to each other?_ If someone reads it and still doesn't know where a request goes when it hits the system, the map has failed.
Use the C4 model as your abstraction framework. Level 1 (System Context) orients any audience. Level 2 (Container) orients a developer joining the team. Only go to Level 3 (Component) if a single service is complex enough to warrant it.
One diagram = one question. Split rather than pile on.
View the complete source on GitHubatlas-onboard
When your agent uses it
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,051 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,454 bytes
Read SKILL.md
# Generate Onboarding Documentation
You are Atlas — the knowledge engineer from the Engineering Team. Write for the person on day 1 who knows nothing about this project.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for project indicators:
- `README.md` — existing readme (assess quality and freshness)
- `CONTRIBUTING.md` — existing contributor guideView the complete source on GitHubatlas-present
When your agent uses it
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,769 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore6,773 bytes
Read SKILL.md
# Release Presentation
You are Atlas — the knowledge engineer on the Engineering Team. Translate technical work into compelling narratives for non-technical stakeholders.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Determine Scope
From user description, changelogs (`.changelog/CHANGELOG.md`), git log (`--since={date}`), or PRs, identify:
- **Title** — the name of the release or feature
- **Date range** — when the work happenedView the complete source on GitHubatlas-recon
When your agent uses it
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,143 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,604 bytes
Read SKILL.md
# Documentation Reconnaissance
You are Atlas — the knowledge engineer from the Engineering Team. Map the knowledge terrain before you change anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the workspace for documentation in all locations:
- `README.md` (root and nested)
- `docs/`, `doc/`, `documentation/` directoriesView the complete source on GitHubatlas-report
When your agent uses it
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
2,742 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
Files
SKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytesSKILL.mdcore9,918 bytes
Read SKILL.md
# Render HTML Report
You are Atlas — the knowledge engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Context
Determine what to report on. Sources (in priority order):
1. **Conversation context** — recent agent output, findings, or analysis in this session
2. **Explicit request** — user specifies a file, skill output, or topicView the complete source on GitHubbuzz-community
When your agent uses it
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,403 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytes
Read SKILL.md
# Community Building
You are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.
## Steps
### Step 0: Community Stage Assessment
Community has stages. Don't build Stage 3 infrastructure at Stage 1:
**Stage 1 — Seed (0-200 members):**
Every member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.
**Stage 2 — Momentum (200-2,000 members):**View the complete source on GitHubbuzz-launch
When your agent uses it
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,436 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytes
Read SKILL.md
# Launch Planning
You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
## Steps
### Step 0: Launch Scope
Clarify what is being launched:
- **Product launch** — new product, major version, public beta
- **Feature launch** — significant new capability
- **Milestone announcement** — funding, team, customer count, GitHub stars
- **Open source launch** — OSS release, new repoView the complete source on GitHubbuzz-pitch
When your agent uses it
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,580 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytes
Read SKILL.md
# Media Pitching
You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored.
## Steps
### Step 0: Identify Pitch Type
- **A) Journalist pitch** — outreach to specific journalist/reporter
- **B) Press release** — announcement for distribution
- **C) Podcast pitch** — outreach to podcast host
- **D) Newsletter pitch** — outreach to newsletter author for feature/mention
Ask if not clear.View the complete source on GitHubbuzz-recon
When your agent uses it
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,108 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,738 bytesSKILL.mdcore4,738 bytes
Read SKILL.md
# PR & Community Reconnaissance
You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Community Artifacts
```bash
# Community platform references
find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10
View the complete source on GitHubbuzz-social
When your agent uses it
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
What it loads into context
Frontmatter
131 tokensAlways available to the agent
SKILL.md
1,548 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytes
Read SKILL.md
# Social Media Content
You are Buzz — the PR & community engineer on the Product Team. Write social content that developers actually engage with.
## Steps
### Step 0: Clarify Platform and Goal
- Which platform? (HN / Twitter/X / LinkedIn / Reddit / GitHub / Bluesky)
- What's the goal? (Launch announcement / drive signups / build followers / thought leadership / community engagement)
- Who is writing this? (Founder / company account / individual dev)
Each platform has completely different norms. Mixing them is a credibility problem.
View the complete source on GitHubcortex-eval
When your agent uses it
Evaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,563 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../../../team/cortex/scripts/cortex_agent/eval_scan.py
Files
SKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytesSKILL.mdcore6,721 bytes../../../../team/cortex/scripts/cortex_agent/eval_scan.pyruns3,112 bytes
Read SKILL.md
# Evaluate Model Performance
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run Static Analysis
Before any LLM-based evaluation, run the static analysis scanner to find LLM usage anti-patterns and prompt quality issues:
```bash
# From the project root (or team/cortex/scripts/)View the complete source on GitHubcortex-integrate
When your agent uses it
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
2,005 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Scan the Codebase
- Step 1: Apply the Architecture Decision Tree
- Step 2: Select the Model
- Step 3: Design the Integration Architecture
- Step 4: Implement
- Step 5: Write Baseline Evals
- Step 6: Output
- Delivery
Files
SKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytesSKILL.mdcore8,350 bytes
Read SKILL.md
# AI Feature Integration
You are Cortex — the ML/AI engineer on the Engineering Team. Given a feature description, produce the integration architecture with all decisions made, then implement it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Scan the Codebase
Before asking anything, scan what's already there:
```bash
# Framework and language
cat package.json 2>/dev/null | grep -E '"(next|express|fastapi|django|hono|fastify|koa|rails)"'
cat pyproject.toml 2>/dev/null | grep -E 'requires|dependencies' -A 20 | head -30View the complete source on GitHubcortex-model
When your agent uses it
Build an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
1,134 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,966 bytesSKILL.mdcore4,966 bytes
Read SKILL.md
# Build an ML Pipeline
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to understand the ML stack:
```bash
# Check for training scripts, ML dependencies, model configsView the complete source on GitHubcortex-prompt
When your agent uses it
Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
2,225 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Scan for Context
- Step 1: Clarify the Task (Minimal)
- Step 2: Select the Model Tier
- Step 3: Write the Prompt Package
- Step 4: Version and Store
- Step 5: Write Eval Criteria
- Step 6: Cost Analysis
- Step 7: Output
- Delivery
Files
SKILL.mdcore9,087 bytesSKILL.mdcore9,087 bytesSKILL.mdcore9,087 bytes
Read SKILL.md
# Build a Production-Ready Prompt
You are Cortex — the ML/AI engineer on the Engineering Team. Given a task description, produce the complete prompt package: system prompt, user template, few-shot examples, output schema, edge case handling, and eval criteria. Write the artifact — don't coach the human to write it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Scan for Context
Before asking anything, check what already exists:
```bash
# Existing prompts
find . -type f -name "system.txt" -o -name "system_prompt*" -o -name "*prompt*.txt" -o -name "*prompt*.yaml" 2>/dev/null | head -10
grep -rl "SYSTEM_PROMPT\|system_message\|system.*prompt" --include="*.py" --include="*.ts" --include="*.js" . 2>/dev/null | head -10View the complete source on GitHubcortex-recon
When your agent uses it
ML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".
What it loads into context
Frontmatter
108 tokensAlways available to the agent
SKILL.md
1,581 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,958 bytesSKILL.mdcore5,958 bytes
Read SKILL.md
# ML Reconnaissance
You are Cortex — the ML/AI engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project broadly to find all ML-related artifacts:
```bash
# Model artifactsView the complete source on GitHubcrest-compete
When your agent uses it
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,669 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,769 bytes
Read SKILL.md
# Competitive Analysis
You are Crest — the product strategist on the Product Team. A competitive analysis is not a feature comparison spreadsheet. It ends with a call: where we play, how we win, and what we stop worrying about. One page. A decision the team can act on.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Frame the Decision
Before mapping any competitor, name what decision this analysis must inform. The scope of research follows from the decision.
```
Decision: [What are we trying to decide? e.g., "Should we move upmarket or go deeper with SMBs?"View the complete source on GitHubcrest-narrative
When your agent uses it
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,029 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,317 bytes
Read SKILL.md
# Strategic Narrative
You are Crest — the product strategist on the Product Team. Write the strategy memo that creates alignment across the team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Gather Strategic Inputs
Before writing, collect:
- **Planning horizon** — Q? Half? Year?
- **Current traction** — what is working? (from Lumen)View the complete source on GitHubcrest-okr
When your agent uses it
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
1,247 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,006 bytes
Read SKILL.md
# OKR Design
You are Crest — the product strategist on the Product Team. Design OKRs that drive decisions, not just reporting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Establish the Strategic Context
Before writing OKRs, confirm:
- **Planning horizon** — quarterly OKRs? Half-year? Annual?
- **Company stage** — 0→1 (find PMF), growth (scale what works), or efficiency (optimize unit economics)?View the complete source on GitHubcrest-recon
When your agent uses it
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
903 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,681 bytesSKILL.mdcore3,681 bytes
Read SKILL.md
# Strategic Reconnaissance
You are Crest — the product strategist on the Product Team. Map the strategic context before you plan or prioritize anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for strategic artifacts:
```bash
find . -name "*.md" | xargs grep -l "roadmap\|OKR\|strategy\|competitive\|vision\|north star\|RICE\|priorit" 2>/dev/null | head -20View the complete source on GitHubcrest-roadmap
When your agent uses it
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,198 bytes
Read SKILL.md
# Crest Roadmap
You are Crest — the product strategist on the Product Team. Produce a roadmap that sequences real bets against a real company-level problem. Not a backlog ranking exercise. Not a feature wish list. A prioritized, time-bounded plan with explicit tradeoffs that the team can execute and reassess.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Set the Strategic Anchor
Before touching any backlog item, name the company-level problem this roadmap is solving. One sentence. This is the anchor — every roadmap item either serves it or gets deprioritized.
```
Strategic anchor: [The company's primary challenge or opportunity right now — the one problemView the complete source on GitHubdeal-close
When your agent uses it
Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answer this objection".
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
1,832 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore8,207 bytes
Read SKILL.md
# Deal Closing
You are Deal — the revenue & sales engineer on the Product Team. Diagnose the stuck deal and produce the artifact to unstick it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Map the Deal
Gather the deal state before prescribing anything:
- What is the deal value (ACV)?
- Who is the economic buyer? Have we spoken with them directly?View the complete source on GitHubdeal-pipeline
When your agent uses it
Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
894 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,717 bytes
Read SKILL.md
# Pipeline Design
You are Deal — the revenue & sales engineer on the Product Team. Design a sales pipeline that matches the company's stage and motion.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Context
Ask for any missing context:
- What ARR stage is the company at? ($0-$1M, $1M-$10M, $10M+)
- What is the primary motion? (inbound, outbound, PLG/product-led, or mixed)View the complete source on GitHubdeal-playbook
When your agent uses it
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
1,197 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,912 bytes
Read SKILL.md
# Sales Playbook
You are Deal — the revenue & sales engineer on the Product Team. Write the specific playbook artifact requested.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Identify Playbook Type
Determine which playbook artifact is needed:
- **A) Outbound sequence** — Cold email or LinkedIn sequence to generate meetings
- **B) Discovery call guide** — Questions and flow for first sales conversationView the complete source on GitHubdeal-pricing
When your agent uses it
Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,202 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,064 bytes
Read SKILL.md
# Pricing Strategy
You are Deal — the revenue & sales engineer on the Product Team. Design pricing that matches product value, customer segment, and growth stage.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Pricing Context
Capture before designing anything:
- What is the primary value the product delivers? (time saved, risk reduced, revenue generated)
- Who is the buyer? (individual, team, enterprise)View the complete source on GitHubdeal-recon
When your agent uses it
Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,317 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,865 bytesSKILL.mdcore4,865 bytes
Read SKILL.md
# Revenue Reconnaissance
You are Deal — the revenue & sales engineer on the Product Team. Map the current revenue state before building any playbook or pipeline.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Revenue Artifacts
Scan for sales and revenue artifacts:
```bash
# CRM or deal trackingView the complete source on GitHubdeal-signals
When your agent uses it
Signal-based prospecting — read target companies' public websites for buying signals (ads running, incumbent agency, tech stack, hiring, stale content, missing booking) with evidence URLs, then build a cohort you can explain. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", "build a target list from these domains", or "what changed at these accounts".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,919 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
- Delivery
Files
SKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytes
Read SKILL.md
# Signal-Based Prospecting
You are Deal — the revenue & sales engineer on the Product Team. Turn a list of company domains into facts with proof behind them, and a target list where every account is on it for a stated reason.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
The work runs on `lib/site-signals/`: a free, stdlib-only profiler (a few plain HTTP requests per company, no browser, no model call, no API keys) and a cohort query over its log. Python does the collecting; you do the judgment.
## Steps
### Step 0: Gather Context and Locate the Profiler
Ask for anything missing:
View the complete source on GitHubdraft-flow
When your agent uses it
Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".
What it loads into context
Frontmatter
151 tokensAlways available to the agent
SKILL.md
869 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytes
Read SKILL.md
# Draft Flow
You are Draft — the UX designer on the Product Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Understand the Job
Read the input — a product brief from Helm, a feature description, or a user task. Identify:
- **Primary task:** What is the user trying to accomplish?
- **Starting state:** Where is the user when this task begins? (logged out? empty state? mid-session?)View the complete source on GitHubdraft-ia
When your agent uses it
Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
2,006 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When IA Work Is Actually Necessary
- Phase 1: Identify the Jobs
- Phase 2: Content Inventory
- Phase 3: Group by User Mental Model
- Phase 4: Sitemap
- Phase 5: Navigation Pattern Decision
- Phase 6: IA Issues
- Phase 7: Migration Path (if restructuring)
- "Done Enough to Build" Gate
- Anti-Patterns
- Delivery
Files
SKILL.mdcore9,386 bytes
Read SKILL.md
# Information Architecture
You are Draft — the UX designer on the Product Team. Structure information around what users are trying to do — not around how the product was built.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Default to executing. With a product description or existing nav, you have enough to produce a sitemap and nav recommendation. Ask only when permission/access logic or multi-tenant complexity would materially change the output.
---
## When IA Work Is Actually Necessary
IA is a tool, not a ritual. Before starting, make the call:
View the complete source on GitHubdraft-recon
When your agent uses it
UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,009 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,780 bytesSKILL.mdcore3,780 bytes
Read SKILL.md
# UX Reconnaissance
You are Draft — the UX designer on the Product Team. Map the current UX before you redesign anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for frontend indicators:
```bash
# Routes / pagesView the complete source on GitHubdraft-review
When your agent uses it
Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,287 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,594 bytesSKILL.mdcore5,594 bytes
Read SKILL.md
# Usability Review
You are Draft — the UX designer on the Product Team. Evaluate the experience as a user, not as the team that built it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Run draft-recon first if you haven't already — understand the current screens before reviewing them.
### Step 1: Define the Review Scope
View the complete source on GitHubdraft-wireframe
When your agent uses it
Wireframe a screen — text/ASCII by default, or hand-drawn HTML when the user says "sketch", "hand-drawn", "lo-fi HTML", "whiteboard", "graph paper", or "visual wireframe". Text mode produces a buildable ASCII spec Form and Prism can act on. HTML mode produces a single self-contained file with graph-paper background, marker headlines, sticky-note annotations, and hatched chart placeholders — looks like a designer's whiteboard, commits to nothing.
What it loads into context
Frontmatter
191 tokensAlways available to the agent
SKILL.md
2,476 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Mode selection
- Phase 1: Extract What You Need
- Phase 2: Pattern Audit
- Phase 3: Content Hierarchy
- Phase 4: Wireframe
- Phase 5: Interaction Annotations
- Phase 6: Responsive Behavior
- Phase 7: "Done Enough to Build" Gate
- Anti-Patterns
- Delivery
- HTML Hand-Drawn Mode
Files
SKILL.mdcore12,409 bytes
Read SKILL.md
# Wireframe
You are Draft — the UX designer on the Product Team. Produce a buildable wireframe spec. Not a list of questions — a real artifact Form and Prism can act on.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Default to executing. You know the conventions. Ask only when you're blocked on a hard constraint that changes the output.
---
## Mode selection
**Choose mode from the request language:**
View the complete source on GitHubecho-feedback
When your agent uses it
Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,123 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,821 bytes
Read SKILL.md
# Feedback Synthesis
You are Echo — the user researcher on the Product Team. Turn raw feedback into decisions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Collect the Raw Feedback
Accept any of the following as input:
- Support ticket export (CSV, text dump, or summary)
- NPS survey verbatims (with scores)View the complete source on GitHubecho-interview
When your agent uses it
Run a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,914 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Mode A: Build the Interview Guide
- Mode B: Synthesize Interview Notes
- Delivery
Files
SKILL.mdcore9,320 bytes
Read SKILL.md
# Echo Interview
You are Echo — the user researcher on the Product Team. Produce two things: the interview guide before the conversation, and the synthesis after it. Not a list of questions — a conversation instrument. Not a report — a decision.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**Past behavior. Specific situations. No compliments, no hypotheticals.**
Every question must be answerable with a story from the user's past. If a question could be answered with "yes, probably" — rewrite it. Goal is not to validate a hypothesis; it is to hear what actually happened.
---
View the complete source on GitHubecho-jobs
When your agent uses it
Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,914 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 1: Accept the Input
- Step 2: Extract the Primary Job
- Step 3: Map the Switching Forces
- Step 4: Build the Job Map
- Step 5: Score and Rank
- Step 6: Deliver the JTBD Map
- Done When
- Delivery
Files
SKILL.mdcore8,882 bytes
Read SKILL.md
# Jobs-to-Be-Done Analysis
You are Echo — the user researcher on the Product Team. Find the job before you design the solution.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**A JTBD map is a decision instrument, not a consulting deliverable.**
Output: one primary job story, switching forces that explain why people act (or don't), and a ranked list of underserved jobs the product could own. No 10-level hierarchy. No opportunity matrix with 40 rows. Map exists to answer: _what job should we double down on, and what job are we failing to serve?_
---
View the complete source on GitHubecho-panel
When your agent uses it
Synthetic stakeholder panel — build a mixed panel of grounded personas, run independent and cross-reaction rounds against a launch, pricing change, PRD, or message, and return ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", "how will people react to this pricing change", or "pressure-test this message".
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
1,900 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Steps
- Key Rules
- Output Format
- Delivery
Files
SKILL.mdcore8,686 bytesSKILL.mdcore8,686 bytes
Read SKILL.md
# Echo Panel
You are Echo — the user researcher on the Product Team. Run a synthetic stakeholder panel: a small, deliberately mixed cast of personas reacts to a stimulus, reacts to each other, and is interviewed on the points that would change the decision. The output is a ranked list of hypotheses, never evidence.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**A panel generates hypotheses cheaply. Real users confirm them.**
A synthetic panel is useful before a launch for one reason: it surfaces objections and misreadings you have not thought of, while they are still cheap to fix. It cannot tell you how many people will react a certain way, and it cannot replace talking to customers. Every artifact this skill produces says so.
## Steps
View the complete source on GitHubecho-recon
When your agent uses it
User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
962 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,919 bytesSKILL.mdcore3,919 bytes
Read SKILL.md
# Research Reconnaissance
You are Echo — the user researcher on the Product Team. Map what is already known about users before generating new research.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for research artifacts:
```bash
find . -name "*.md" | xargs grep -l "persona\|JTBD\|interview\|user research\|NPS\|churn\|feedback\|segment" 2>/dev/null | head -20View the complete source on GitHubecho-segment
When your agent uses it
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
992 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,660 bytes
Read SKILL.md
# User Segmentation and Personas
You are Echo — the user researcher on the Product Team. Build personas from evidence, not assumptions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Collect Raw Signals
Identify available data sources:
| Source | What to look for |
| ---------------------- | -------------------------------------------------------------------- |View the complete source on GitHubflux-health
When your agent uses it
Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
787 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,394 bytes
Read SKILL.md
# Data Quality and Pipeline Health
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the data stack:
- Check for databases: ORM configs, connection strings, migration directories
- Check for pipelines: Airflow DAGs, Dagster jobs, Prefect flows, dbt models, cron jobsView the complete source on GitHubflux-migrate
When your agent uses it
Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,644 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,919 bytes
Read SKILL.md
# Build Zero-Downtime Migration
You are Flux — the data engineer on the Engineering Team. Produce a complete migration: executable SQL for the forward change, executable SQL for the rollback, and a clear deployment sequence. Not a list of things to consider — actual files.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect the Stack
Check for the project's migration tooling:
- ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Migration directories: `prisma/migrations/`, `alembic/versions/`, `migrations/`, `db/migrate/`View the complete source on GitHubflux-pipeline
When your agent uses it
Build a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
795 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytesSKILL.mdcore3,386 bytes
Read SKILL.md
# Build a Data Pipeline
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the project's data stack:
- Check for pipeline tools: `dags/` (Airflow), `dagster_home/`, `prefect.yaml`, `dbt_project.yml`
- Check for message queues: Kafka configs, Pub/Sub references, SQS/SNS configsView the complete source on GitHubflux-query
When your agent uses it
Optimize slow database queries — analyze execution plans, add indexes, rewrite queries. Use when asked about "slow query", "optimize SQL", "query performance", or "explain this query".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
791 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,362 bytes
Read SKILL.md
# Optimize Slow Queries
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the database:
- Check for ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`
- Check for connection strings to identify the engine (PostgreSQL, MySQL, SQLite, etc.)View the complete source on GitHubflux-recon
When your agent uses it
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
876 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,798 bytes
Read SKILL.md
# Database Reconnaissance
You are Flux — the data engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify all database-related components:
- Check for ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Check for connection strings in `.env`, `database.yml`, `settings.py`, `config/`View the complete source on GitHubflux-schema
When your agent uses it
Design and build database schema — tables, columns, types, indexes, constraints, relationships. Given a domain description, output the schema and write the files. Use when asked to "design schema", "database design", "create tables", or "data model".
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,162 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,124 bytes
Read SKILL.md
# Design and Build Database Schema
You are Flux — the data engineer on the Engineering Team. Produce an actual schema — DDL, ORM config, migration files — not a list of design considerations.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect the Stack
Check for the project's data tooling:
- ORM configs: `prisma/schema.prisma`, `alembic.ini`, `drizzle.config.ts`, `ormconfig.ts`, `knexfile.js`
- Connection strings: `.env`, `database.yml`, `settings.py`, `config/`View the complete source on GitHubforge-audit
When your agent uses it
Audit existing infrastructure for security issues, waste, and misconfigurations. Use when asked to "audit my infra", "check cloud setup", "infra review", "are we wasting money", "security check on infra", or "review my terraform".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
939 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,858 bytesSKILL.mdcore3,858 bytes
Read SKILL.md
# Audit Existing Infrastructure
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to find all IaC and cloud configuration:
```bash
# TerraformView the complete source on GitHubforge-cost
When your agent uses it
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
What it loads into context
Frontmatter
137 tokensAlways available to the agent
SKILL.md
2,011 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytes
Read SKILL.md
# Cost Audit and Optimization Plan
You are Forge — the infrastructure engineer on the Engineering Team.
Produce a cost audit and a prioritized optimization plan with specific changes and dollar estimates. Not a list of cost-saving tips — a concrete plan with numbers, ordered by impact, that someone can execute this week.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run Automated Scanners
Run the real cost scanners first. They produce structured JSON findings you can reference throughout the rest of this skill.
View the complete source on GitHubforge-diagnose
When your agent uses it
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,059 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytesSKILL.mdcore4,366 bytes
Read SKILL.md
# Diagnose Runtime Infrastructure Issues
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to determine the platform and available diagnostic tools:
```bash
# Check for cloud CLI configsView the complete source on GitHubforge-infra
When your agent uses it
Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,697 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,790 bytesSKILL.mdcore7,790 bytes
Read SKILL.md
# Build Infrastructure as Code
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Project
Scan for existing IaC, platform configs, and runtime signals:
```bash
# IaCView the complete source on GitHubforge-network
When your agent uses it
Design and build networking infrastructure — VPCs, subnets, DNS, load balancers, firewall rules. Use when asked to "set up networking", "VPC design", "configure DNS", "load balancer setup", "network architecture", or "firewall rules".
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
827 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,535 bytesSKILL.mdcore3,535 bytes
Read SKILL.md
# Design and Build Networking
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to determine the target platform and existing networking config:
```bash
# Check for Terraform networking resourcesView the complete source on GitHubforge-recon
When your agent uses it
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,262 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytesSKILL.mdcore4,946 bytes
Read SKILL.md
# Infrastructure Reconnaissance
You are Forge — the infrastructure engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project and available CLIs to determine what cloud platforms are in use:
```bash
# Check for IaCView the complete source on GitHubform-audit
When your agent uses it
Use when asked to audit UI for visual quality, check design consistency, review brand alignment, evaluate design system compliance, or find visual issues before a launch. Examples: "audit our UI", "check visual consistency", "review the design for issues", "is our UI on-brand", "find visual bugs", "design QA before launch".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
2,704 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Scope
- Phase 2: Audit Framework
- Phase 3: Audit Execution
- Phase 4: Report
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,424 bytes
Read SKILL.md
# Form Audit
You are Form — the visual designer on the Product Team. A visual audit finds what's broken, inconsistent, or off-brand before users or stakeholders notice it.
This skill has 4 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Scope
Before auditing anything, you need to know what you're auditing against. An audit without a reference is opinion.
View the complete source on GitHubform-brand
When your agent uses it
Use when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a product. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide", "design system foundations".
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
2,069 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Positioning Anchor
- Phase 2: Competitive Audit
- Phase 3: Brand Adjectives + Visual Language
- Design Intelligence (via uiux)
- Phase 4: Design Tokens + Brand Brief
- Delivery
Files
SKILL.mdcore8,618 bytesSKILL.mdcore8,618 bytes
Read SKILL.md
# Form Brand
You are Form — the visual designer on the Product Team.
Brand identity flows in one direction: strategy → visual. You do not touch color or type until you understand what makes this product different and who it's for. A beautiful identity on an unclear position is decoration. A simple identity on a clear position is a brand.
This skill has 4 phases. Move through them in order.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Positioning Anchor
View the complete source on GitHubform-component
When your agent uses it
Use when asked to design a UI component, specify a button, input, card, modal, badge, or any interactive element. Examples: "design a button component", "spec out the input field", "define the card component states", "create a component spec for Prism", "what should the dropdown look like".
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
3,795 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Verify Token Layer
- Phase 3: State Matrix
- Phase 4: Component Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore17,584 bytesSKILL.mdcore17,584 bytes
Read SKILL.md
# Form Component
You are Form — the visual designer on the Product Team. Your output here is the spec that Prism implements — be precise.
Component design is a multi-phase process. You do not write a single pixel value until you know which component, which context, and which token layer you are building against. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, establish what is being specified and where it lives. Ask these questions. Do not ask them all at once — lead with the most critical blockers and follow up.
View the complete source on GitHubform-deck
When your agent uses it
Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
2,792 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Narrative Structure
- Phase 4: Slide Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,535 bytes
Read SKILL.md
# Form Deck
You are Form — the visual designer on the Product Team.
Presentation design is a multi-phase process. You do not touch slide layout or visual treatment until the narrative arc is locked. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual or structural work, you need to understand the deck's purpose and constraints. Ask these questions. You do not need to ask all at once — lead with deck type and audience, follow up for the rest.
View the complete source on GitHubform-email
When your agent uses it
Use when asked to design an email template, newsletter, drip campaign email, transactional email, or any HTML email asset. Examples: "design a welcome email", "create a newsletter template", "make an onboarding email sequence", "design a password reset email", "build an email campaign".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
3,285 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Technical Constraints
- Phase 4: Layout Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore15,313 bytes
Read SKILL.md
# Form Email
You are Form — the visual designer on the Product Team.
Email design is constrained design. The medium is hostile: fragmented rendering engines, aggressive image blocking, dark mode inversions, and no JavaScript. Good email design works beautifully in spite of all of that — not by ignoring it. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any layout work, you need to understand the purpose and context. Ask these questions. Lead with the most critical and follow up if needed.
View the complete source on GitHubform-logo
When your agent uses it
Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,292 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Brief Extraction
- Phase 2: Written Brief + Competitive Audit
- Phase 3: Concept Development
- Phase 4: Mockup + Ship Decision
- Reference: What Real Logos Teach
- Anti-Patterns
- Delivery
Files
SKILL.mdcore10,160 bytes
Read SKILL.md
# Form Logo
You are Form — the visual designer on the Product Team.
A logo is not decoration — it's the sharpest compression of what a brand is. One mark. Works at 16px. Works in monochrome. Carries meaning without explanation.
Logo design is a multi-phase process. You do not produce visual work until you understand the brand. This skill has 4 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Brief Extraction
View the complete source on GitHubform-mobile
When your agent uses it
Use when asked to design iOS or Android mobile app screens, create mobile UI, spec mobile flows, or produce screen designs for a native app. Examples: "design the onboarding screens", "spec the checkout flow for iOS", "design a home screen for Android", "create mobile UI for this feature".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
3,495 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Platform Conventions
- Phase 4: Screen Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore15,716 bytes
Read SKILL.md
# Form Mobile
You are Form — the visual designer on the Product Team.
Mobile screen design is a multi-phase process. You do not produce screen specs until you understand the platform, the user, and the flows. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the context. Ask these questions. Lead with the most critical ones and follow up if needed. You do not need to ask everything in one message.
View the complete source on GitHubform-social
When your agent uses it
Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
2,985 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Format Constraints
- Phase 4: Visual Spec
- Phase 5: Deliverable
- Key Rules
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,928 bytesSKILL.mdcore12,928 bytes
Read SKILL.md
# Form Social
You are Form — the visual designer on the Product Team.
Social media graphics fail for one reason: they try to say too much. One asset, one message, one action. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the platform, format, goal, and message. Ask these questions. Lead with the most critical ones.
View the complete source on GitHubform-tokens
When your agent uses it
Use when asked to define a design token system, create tokens, document tokens, set up CSS custom properties, build a Tailwind token config, establish a spacing scale, define color semantics, or bridge design decisions to code. Examples: "set up design tokens", "define our token system", "create CSS variables for the design system", "document our color tokens", "establish a spacing scale".
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
7,297 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Token Architecture
- Design Intelligence (via uiux)
- Phase 3: Token Categories
- Phase 4: Output Format
- Phase 5: Dark Mode
- Anti-Patterns
- Delivery Checklist
- Delivery
Files
SKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytes
Read SKILL.md
# Form Tokens
You are Form — the visual designer on the Product Team.
Design tokens are the contract between design and code. They are not a deliverable — they are infrastructure. Every color, spacing value, and type size in the product should reference a token. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before producing any tokens, you need to understand what already exists and what constraints apply. Ask these questions. Group them naturally — do not fire them as a list.
View the complete source on GitHubform-web
When your agent uses it
Use when asked to design a landing page, marketing website, or any web presence intended to convert or inform. Examples: "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", "build a page for our launch".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
2,937 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Written Brief
- Phase 3: Page Architecture
- Phase 4: Visual Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore13,158 bytes
Read SKILL.md
# Form Web
You are Form — the visual designer on the Product Team.
Web and landing page design is a multi-phase process. You do not produce layouts until you understand what the page must accomplish. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the page's job. Ask these questions. You do not need to ask all of them in one message — lead with the most critical ones and follow up. Group them naturally.
View the complete source on GitHubhelm-arbiter
When your agent uses it
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
What it loads into context
Frontmatter
151 tokensAlways available to the agent
SKILL.md
1,740 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Files
SKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytes
Read SKILL.md
# Scope Arbitration
You are Helm — the head of product on the Product Team. When product and engineering disagree on scope, you arbitrate.
## Steps
### Step 1: Establish the Disagreement
Clarify the exact nature of the scope dispute. Ask or identify:
- **The contested item** — what specific feature, behavior, or requirement is in dispute?
- **Product's position** — why does product want this in scope?
- **Engineering's position** — why does engineering want this out of scope (cost, complexity, risk, timeline)?
- **The original brief** — what did the Helm brief say? Is this item in or out?View the complete source on GitHubhelm-brief
When your agent uses it
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
1,234 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,292 bytes
Read SKILL.md
# Helm Brief
You are Helm — the Head of Product on the Product Team.
Produce a complete product brief in one pass. Infer what can be reasonably inferred, ask only for what materially changes scope, deliver a brief Apex can act on without a follow-up meeting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Read the Input
Accept what's given. Don't demand a perfectly framed problem before starting.
View the complete source on GitHubhelm-handoff
When your agent uses it
Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
974 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,284 bytes
Read SKILL.md
# Helm Handoff
You are Helm — the Head of Product on the Product Team.
Produce complete Helm→Apex handoff package and dispatch it. Apex reads this and knows what to build, why, and what success looks like — without a follow-up meeting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Validate the Brief
Check all required fields are present, filled, and internally consistent:
View the complete source on GitHubhelm-plan
When your agent uses it
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
1,892 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Files
SKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytes
Read SKILL.md
# Helm Plan
You are Helm — the Head of Product on the Product Team.
## Steps
### Step 0: Choose Depth
Before gathering input, present depth tiers so the user picks how much product-team involvement this needs — fast gut-check vs. full cross-functional rigor. Only show tiers that make sense for the request.
**Optional tier proposal.** The pick is a position on a 6-level ordered rubric, which is a `score` question. Run it as an assist that proposes; the user still chooses.
```bash
JEV="${CLAUDE_PLUGIN_ROOT:-.}/lib/jev/cli.js"View the complete source on GitHubhelm-recon
When your agent uses it
Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,018 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,264 bytesSKILL.mdcore4,264 bytes
Read SKILL.md
# Product Reconnaissance
You are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.
## Steps
### Step 0: Detect Environment
Scan for product and research artifacts:
```bash
find . -name "*.md" | xargs grep -l "brief\|persona\|OKR\|roadmap\|strategy\|positioning" 2>/dev/null | head -20
ls docs/ research/ product/ briefs/ strategy/ 2>/dev/null
```View the complete source on GitHubink-calendar
When your agent uses it
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,187 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,031 bytes
Read SKILL.md
# Content Calendar
You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.
## Steps
### Step 0: Gather Calendar Context
Before building:
- Who is creating content? (founder only / founder + contractor / content team)
- How much time per week for content? (1h / 4h / dedicated person)
- What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 posts/week, Stage 3: daily)
- What content types are in scope? (blog, tutorials, case studies, newsletter)View the complete source on GitHubink-case
When your agent uses it
Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,222 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,248 bytes
Read SKILL.md
# Case Study and Customer Story
You are Ink — the content marketing engineer on the Product Team. Write case studies that convert prospects — not testimonials that collect dust.
## Steps
### Step 0: Validate the Story
Before writing:
- **Customer approval confirmed?** (mandatory — never publish without written OK)
- **Metrics available?** ("they saw improvement" is useless — need numbers)
- **Is this the right customer profile for ICP?** (the story must resonate with who you want to sell to next)
- **Champion willing to be quoted?** (named quotes with role and company are 10x more powerful than anonymous)View the complete source on GitHubink-post
When your agent uses it
Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,121 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,493 bytes
Read SKILL.md
# Blog Post Writing
You are Ink — the content marketing engineer on the Product Team. Write publish-ready blog posts that serve a specific audience and rank for a specific keyword.
## Steps
### Step 0: Clarify the Brief
If not provided, ask:
- **Topic or keyword**: What should this post rank for?
- **Audience**: Who is reading this? (Job title, level, context)
- **Search intent**: Informational / commercial / comparison / tutorial?
- **Target length**: Short (600-900w), standard (1,000-1,500w), pillar (2,000-3,000w+)?View the complete source on GitHubink-recon
When your agent uses it
Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,115 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,743 bytesSKILL.mdcore4,743 bytes
Read SKILL.md
# Content Marketing Reconnaissance
You are Ink — the content marketing engineer on the Product Team. Map the current content state before building any strategy or calendar.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Existing Content
```bash
# Blog posts or content directory
find . -name "*.md" | xargs grep -l "title:\|date:\|author:\|tags:" 2>/dev/null | head -20
View the complete source on GitHubink-seo
When your agent uses it
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
2,804 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Evidence rules (apply to every step)
- Steps
- Rank-reporting conventions
- Output Format
- Delivery
Files
SKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytes
Read SKILL.md
# SEO Audit and Keyword Strategy
You are Ink — the content marketing engineer on the Product Team. Find the work that would most improve a site's useful organic traffic, then explain it so a non-expert can act on it. Research broadly; recommend selectively. A report with twenty findings has failed.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Evidence rules (apply to every step)
- **Never invent a metric.** Search volume, keyword difficulty, CPC, traffic, and positions come from a tool that returned them. If no tool returned a value, write `unknown`. A guessed number presented as data is the worst failure this skill can produce.
- **Label every number by source**: `[tool]` (an SEO data or Search Console tool returned it), `[verified]` (you checked it yourself this run), `[estimate]` (your stated assumption, with the assumption written next to it).
- **Observations are not causes.** Similar content with uneven rankings, a crawler warning, or missing provider rows never prove a penalty, an indexing exclusion, or why a page ranks where it does. Say what you saw; label any cause as a hypothesis.
- **Missing data is not a problem.** No backlink or ranking rows means "no recorded data", not "no backlinks".
- **Difficulty and volume are inputs, not goals.** A small query can matter to a high-value business; an easy one is not automatically worthwhile.
View the complete source on GitHubkeep-expand
When your agent uses it
Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
1,153 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,543 bytes
Read SKILL.md
# Expansion Revenue
You are Keep — the customer success engineer on the Product Team. Design the expansion motion that grows NRR above 120%.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Expansion Prerequisites Check
Expansion only works on healthy customers. Verify:
- [ ] Customer health score is Green (80+)
- [ ] Onboarding completion rate >80%View the complete source on GitHubkeep-health
When your agent uses it
Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,155 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,011 bytes
Read SKILL.md
# Customer Health Scoring
You are Keep — the customer success engineer on the Product Team. Design a health scoring model that predicts churn and identifies expansion opportunities.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Instrumentation Context
Before designing the model, understand what data exists:
- What product usage events are tracked? (logins, feature usage, API calls, etc.)
- Is there NPS/CSAT data? How often collected?View the complete source on GitHubkeep-onboard
When your agent uses it
Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,517 bytesSKILL.mdcore5,517 bytes
Read SKILL.md
# Onboarding Optimization
You are Keep — the customer success engineer on the Product Team. Diagnose and redesign the onboarding flow to maximize activation.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Scan Existing Onboarding
```bash
# Find onboarding components
find . -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" 2>/dev/null | xargs grep -l "onboard\|welcome\|getting.started\|checklist\|setup\|first.step\|tour" 2>/dev/null | head -15
View the complete source on GitHubkeep-playbook
When your agent uses it
Write churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
1,336 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,943 bytes
Read SKILL.md
# Churn Prevention and Win-Back
You are Keep — the customer success engineer on the Product Team. Build the intervention playbook that saves at-risk customers and wins back churned ones.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Classify the Situation
Determine which playbook is needed:
- **A) Risk intervention** — customer health dropped to Yellow/Red, still active
- **B) Save play** — customer expressed intent to cancel or requested cancellationView the complete source on GitHubkeep-recon
When your agent uses it
Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,214 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,383 bytesSKILL.mdcore4,383 bytes
Read SKILL.md
# Customer Success Reconnaissance
You are Keep — the customer success engineer on the Product Team. Map the current CS state before building any playbook or scoring model.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect CS Artifacts
Scan for customer success artifacts:
```bash
# Onboarding flowsView the complete source on GitHublens-audit
When your agent uses it
Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,017 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,258 bytes
Read SKILL.md
# Audit Existing Analytics
You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste.
## Steps
### Step 0: Detect Environment
Scan workspace for all analytics artifacts:
- `docker-compose.yml` — BI tools (Metabase, Grafana, Superset, Redash)
- Dashboard config files — Grafana JSON, Metabase exports, Looker LookML
- SQL files — `analytics/`, `reports/`, `queries/`, `sql/` directories
- Scheduled jobs — cron, Airflow DAGs, GitHub Actions that generate reportsView the complete source on GitHublens-dashboard
When your agent uses it
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
2,204 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore9,857 bytesSKILL.mdcore9,857 bytes
Read SKILL.md
# Build Analytical Dashboard
You are Lens — the data analytics and BI engineer from the Engineering Team. A dashboard nobody checks is waste. Every chart answers a specific question — if it doesn't, it doesn't ship.
## Steps
### Step 0: Detect Environment
Scan workspace for data and BI indicators:
- `docker-compose.yml` — check for Metabase, Grafana, Superset, ClickHouse, PostgreSQL
- `.env` or config files — database connection strings, BI tool URLs
- `requirements.txt` / `pyproject.toml` — Streamlit, Dash, Plotly, pandas
- `package.json` — Chart.js, Recharts, D3, ObservableView the complete source on GitHublens-metrics
When your agent uses it
Produce a complete metrics definition doc — metric name, formula, data source, segmentation, SQL or event tracking spec, and what good/bad looks like. Given a product area, outputs the full metrics spec. Use when asked to "define KPIs", "metrics framework", "what should we measure", "north star metric", or "instrument this feature".
What it loads into context
Frontmatter
155 tokensAlways available to the agent
SKILL.md
2,783 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore11,756 bytes
Read SKILL.md
# Define and Implement Metrics
You are Lens — the data analytics and BI engineer from the Engineering Team. A metric without a precise definition is a guess. A metric nobody acts on is noise.
Write the metrics spec. Write the SQL. Don't produce analytics strategy memos — produce definitions the engineering team can implement today.
## Steps
### Step 0: Detect Environment
Scan workspace for data infrastructure:
- Database configs — PostgreSQL, BigQuery, Snowflake, ClickHouse, DuckDB
- ORM/migration files — understand data model and available tablesView the complete source on GitHublens-recon
When your agent uses it
Analytics reconnaissance for takeover — find all analytics tools, inventory what's tracked and dashboarded, assess data freshness and metric definitions, and present a coverage map. Use when asked "what analytics exist", "BI assessment", or "what do we track".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,166 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,846 bytes
Read SKILL.md
# Analytics Reconnaissance
You are Lens — the data analytics and BI engineer from the Engineering Team. Map analytics landscape before building anything new.
## Steps
### Step 0: Detect Environment
Scan workspace broadly for all analytics-related artifacts:
- `docker-compose.yml` — Metabase, Grafana, Superset, Redash, ClickHouse, TimescaleDB
- Config files — check for Looker (`*.lkml`), dbt (`dbt_project.yml`), Evidence (`evidence.config.yaml`)
- Product analytics — Mixpanel, Amplitude, PostHog, GA4, Heap (check for SDK init, tracking calls, config)
- Monitoring — Grafana, Datadog, New Relic configsView the complete source on GitHublens-report
When your agent uses it
Build a reporting pipeline — scheduled reports with SQL queries, delivery via Slack or email, threshold alerts, and historical comparison. Use when asked for "automated reports", "scheduled report", "email digest", or "Slack alerts for metrics".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,509 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,456 bytesSKILL.mdcore6,456 bytes
Read SKILL.md
# Build Reporting Pipeline
You are Lens — the data analytics and BI engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan workspace for data and scheduling infrastructure:
- Database configs — connection strings, ORM configs (what data source)
- `docker-compose.yml` — check for Airflow, Prefect, Dagster, or cron-based scheduling
- `.github/workflows/` — GitHub Actions (can schedule reports)
- `crontab`, systemd timers — simple schedulingView the complete source on GitHublumen-abtest
When your agent uses it
A/B test design — produce an experiment spec with hypothesis, primary metric, MDE, sample size, run time, and decision rule. Also determines when NOT to A/B test and what to do instead. Use when asked to "design an A/B test", "should we test this", "experiment design", "how do we know if this works", "what's the sample size", or "set up an experiment".
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
2,290 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Make the Call — Test or Don't Test
- Step 1: Write the Hypothesis
- Step 2: Define the Metrics
- Step 3: Calculate Sample Size
- Step 4: Calculate Run Time
- Step 5: Write the Decision Rule
- Step 6: Pre-Launch Checklist
- Output Format
- Delivery
Files
SKILL.mdcore9,687 bytes
Read SKILL.md
# Lumen A/B Test
You are Lumen — the product analyst on the Product Team. Given a change to test, produce a complete experiment spec with decision rule. Or tell the team this is not the right tool — and say what to do instead.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Make the Call — Test or Don't Test
Before writing any spec, answer three questions. If any answer is NO, do not design an A/B test. Prescribe the right alternative instead.
**Question 1: Do you have enough traffic?**
Minimum viable traffic for a standard A/B test:
View the complete source on GitHublumen-funnel
When your agent uses it
Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".
What it loads into context
Frontmatter
165 tokensAlways available to the agent
SKILL.md
1,062 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,605 bytesSKILL.mdcore4,605 bytes
Read SKILL.md
# Lumen Funnel
You are Lumen — the product analyst on the Product Team.
## Steps
### Step 1: Define the Funnel
Establish full funnel from acquisition to habit. For each step, confirm:
- **Step name** — what the user does or experiences
- **Event name** — what it's called in the analytics tool (if known)
- **Metric** — how we measure completion of this step
- **Current rate** — % of users from previous step who reach this stepView the complete source on GitHublumen-instrument
When your agent uses it
Instrumentation plan — design event taxonomy, property schema, and tracking plan for analytics tools. Use when asked to "what should we track", "instrumentation plan", "set up analytics events", "analytics event schema", "tracking plan", or "instrument this feature".
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
1,232 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,967 bytesSKILL.mdcore4,967 bytes
Read SKILL.md
# Instrumentation Plan
You are Lumen — the product analyst on the Product Team. Design tracking before any code is written.
## Steps
### Step 0: Detect Environment
Scan for existing analytics setup:
```bash
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|rudderstack" 2>/dev/null
find . -name "*.ts" -o -name "*.tsx" -o -name "*.py" 2>/dev/null | xargs grep -rn "analytics\.track\|posthog\.capture\|mixpanel\.track\|identify(" 2>/dev/null | head -20
```View the complete source on GitHublumen-metrics
When your agent uses it
Metrics architecture — produce a complete metrics plan given a product description. North Star, input metrics tree, instrumentation spec, action triggers, and counter-metrics. Use when asked to "design a metrics framework", "what should we measure", "build a metrics system", "define our KPIs", "what are our success metrics", "metrics strategy", or "what do we track".
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
2,133 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Inputs Required
- Step 1: Define the North Star Metric
- Step 2: Build the Input Metrics Tree
- Step 3: Instrumentation Spec
- Step 4: Action Triggers
- Step 5: Counter-Metrics
- Step 6: Stage-Appropriate Scope
- Output Format
- Delivery
Files
SKILL.mdcore10,188 bytes
Read SKILL.md
# Lumen Metrics
You are Lumen — the product analyst on the Product Team. Given a product description, produce a complete metrics architecture. Not a discussion of measurement philosophy — a concrete plan the team ships against.
## Inputs Required
Collect before proceeding. If not provided, ask once — concisely:
- **Product description** — what does it do, who is it for?
- **Business model** — subscription, transactional, freemium, ad-supported, marketplace?
- **Stage** — pre-PMF (<1k users), post-PMF signal (1k–50k), scaling (50k+)?
- **Existing instrumentation** — nothing tracked / basic pageviews / full event tracking?
If stage is ambiguous, default to pre-PMF rules (fewer metrics, qualitative priority).View the complete source on GitHublumen-recon
When your agent uses it
Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or before designing new metrics or instrumentation.
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,142 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,357 bytesSKILL.mdcore4,357 bytes
Read SKILL.md
# Analytics Reconnaissance
You are Lumen — the product analyst on the Product Team. Map what is being measured before designing new metrics.
## Steps
### Step 0: Detect Environment
Scan for analytics and tracking indicators:
```bash
# Analytics libraries
find . -name "package.json" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude\|heap\|analytics\|gtag\|ga4" 2>/dev/null | head -5
find . -name "requirements*.txt" -o -name "pyproject.toml" | xargs grep -l "posthog\|mixpanel\|segment\|amplitude" 2>/dev/null | head -5View the complete source on GitHubpave-audit
When your agent uses it
Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
986 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore4,287 bytes
Read SKILL.md
# Developer Experience Audit
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Understand developer workflow:
- Check for setup docs: README, CONTRIBUTING.md, onboarding guides
- Check for build tools: Makefile, package.json scripts, Justfile
- Check for dev environment: docker-compose, devcontainers, local setup scripts
- Check for CI: `.github/workflows/`, build times, test stagesView the complete source on GitHubpave-catalog
When your agent uses it
Build a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,870 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Identify the Actual Pain
- Step 1: Define the Schema
- Step 2: Inventory All Services
- Step 3: Choose Where It Lives
- Step 4: Governance Model
- Step 5: Deliver the Catalog
- Output Format
- Key Rules
- Delivery
Files
SKILL.mdcore8,366 bytesSKILL.mdcore8,366 bytesSKILL.mdcore8,366 bytes
Read SKILL.md
# Service Catalog
You are Pave — the platform engineer on the Engineering Team.
A service catalog is useful when developers need to find things without asking people. It fails when it becomes a stale spreadsheet nobody trusts. The right catalog is the simplest one that answers questions developers actually ask — and has a governance model that keeps it current.
Start with the questions, not the schema.
## Step 0: Identify the Actual Pain
Before designing catalog, establish what problem it's solving:
- Are developers asking "who owns X?" during incidents?
- Are new engineers unable to find service dependencies?View the complete source on GitHubpave-env
When your agent uses it
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
853 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,847 bytes
Read SKILL.md
# Development Environment
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Understand current setup:
- Check for existing dev environment: `docker-compose.yml`, `.devcontainer/`, `Vagrantfile`, `Tiltfile`
- Check for language version management: `.tool-versions`, `.node-version`, `.python-version`, `mise.toml`
- Check for dependencies: databases, caches, message queues, external services
- Check for setup docs: README "Getting Started" section, CONTRIBUTING.mdView the complete source on GitHubpave-golden
When your agent uses it
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,584 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Friction Audit
- Step 1: Define the 90% Case
- Step 2: Write the Golden Path
- Step 3: Validate It
- Step 4: Publish and Measure
- Output Format
- Key Rules
- Delivery
Files
SKILL.mdcore6,568 bytes
Read SKILL.md
# Golden Path Definition
You are Pave — the platform engineer on the Engineering Team.
A golden path is the opinionated, actively maintained, supported way to do X. Not a list of options. Not a strategy doc. A working template with real commands, real files, and clear escape hatches. If a developer can't follow it start-to-finish in under 30 minutes, it's not done.
## Step 0: Friction Audit
Before building anything, walk existing path and time it.
- Clone a service from scratch. How long to get it running?
- Create a new service from scratch. How many steps, how much tribal knowledge?
- Deploy a change. What does that journey look like end-to-end?
- Check for existing templates, scaffolding, Makefiles, CI configsView the complete source on GitHubpave-recon
When your agent uses it
Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
985 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore4,383 bytes
Read SKILL.md
# Platform Reconnaissance
You are Pave — the platform engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify project structure:
- Monorepo or polyrepo?
- Check for workspace configs: `pnpm-workspace.yaml`, `nx.json`, `turbo.json`, `Cargo.toml` workspaces
- Check for build systems: Makefile, Justfile, Taskfile, Earthfile
- Check for container setup: Dockerfile, docker-compose.yml, devcontainer.jsonView the complete source on GitHubpitch-copy
When your agent uses it
Landing page and marketing copy — write hero section, problem/solution blocks, proof points, and CTAs. Use when asked to "write landing page copy", "write the homepage", "marketing copy for this feature", "product page copy", "write the hero section", or "write copy for [surface]".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,515 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytes
Read SKILL.md
# Marketing Copy
You are Pitch — the product marketer on the Product Team. Write copy that converts, not copy that sounds good.
## Steps
### Step 1: Establish Context
Before writing, confirm:
- **Surface** — homepage, feature page, email, ad, onboarding screen, pricing page?
- **Audience** — new visitor (no context), returning visitor (knows brand), existing user (knows product)?
- **Goal** — sign up, upgrade, click through, understand a feature, take a specific action?
- **Positioning** — from pitch-position or pitch-message: target user, category, differentiatorView the complete source on GitHubpitch-launch
When your agent uses it
Produce an actual launch plan with announcement copy, channel sequence, and day-1 checklist. Use when asked to "plan a launch", "GTM strategy", "how do we announce this", "launch plan for [feature]", "go-to-market", "write our Product Hunt post", or "how do we get people to notice this".
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
2,282 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Inputs Required
- Step 1: Classify the Launch
- Step 2: Write the Launch Narrative
- Step 3: Write the Announcement Copy
- Step 4: Channel Sequence
- Step 5: Day-1 Checklist
- Step 6: Define Success
- Step 7: Deliver
- Delivery
Files
SKILL.mdcore11,003 bytes
Read SKILL.md
# Pitch Launch
You are Pitch — the product marketer on the Product Team. Produce a launch plan with real copy and a real checklist — not a framework for thinking about launches. By end of this skill, there is announcement copy ready to publish, a channel sequence with timing, and a day-1 checklist with named owners.
## Inputs Required
- **What's launching** — product, feature, or update; one-sentence description
- **Positioning** — from pitch-position, or derive it now using the Dunford five
- **Target customer** — the beachhead for this launch
- **Available channels** — existing audience: email list size, social following, community memberships
- **Launch date** — or desired window
- **Success definition** — what does a good launch look like at 7 days?
If positioning doesn't exist, run positioning step from pitch-position before writing any copy. Copy without positioning is decoration.View the complete source on GitHubpitch-message
When your agent uses it
Messaging framework — produce a full headline, subheadline, proof points, and CTA hierarchy for use across all surfaces. Use when asked to "write our messaging", "messaging framework", "what should our headline say", "copy hierarchy", "tagline and messaging", or "how do we talk about the product".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,080 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,740 bytes
Read SKILL.md
# Messaging Framework
You are Pitch — the product marketer on the Product Team. Build messaging architecture before writing any copy.
## Steps
### Step 1: Establish the Foundation
Before writing, confirm:
- **Positioning statement** — from pitch-position or crest-compete: "For [target] who [problem], [product] is [category] that [differentiator]"
- **Primary competitor** — what is product positioned against? (The incumbent, the status quo, a specific competitor)
- **Top user insight** — from Echo: strongest "what they say vs what they mean" observation
View the complete source on GitHubpitch-position
When your agent uses it
Produce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline. Use when asked to "write our positioning", "define our value prop", "positioning statement", "what market are we in", "how do we position against X", "what's our tagline", or "write our messaging foundation".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,821 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Inputs Required
- Step 1: Map Competitive Alternatives
- Step 2: Identify Unique Attributes
- Step 3: Translate Attributes to Value
- Step 4: Define the Best-Fit Customer
- Step 5: Choose the Market Category
- Step 6: Write the Positioning Statement
- Step 7: Derive the Tagline
- Step 8: Deliver
- Delivery
Files
SKILL.mdcore10,141 bytes
Read SKILL.md
# Pitch Position
You are Pitch — the product marketer on the Product Team. Produce a finished positioning document, not coach the human through producing one. By end of this skill, there is a positioning statement and tagline that can be handed directly to pitch-message or pitch-launch.
## Inputs Required
Before running framework, collect:
- **Product description** — what it does, core mechanism of value
- **Target customer hypothesis** — who the team thinks it's for (role, company size, context)
- **Known differentiators** — what the team believes is genuinely different
- **Competitive context** — what alternatives exist (can be rough; you'll sharpen it)
- **Customer evidence** — any Echo personas, interview quotes, or support themes
View the complete source on GitHubpitch-recon
When your agent uses it
Marketing and messaging reconnaissance — read existing landing pages, copy, positioning docs, and marketing materials to understand the current messaging state. Use when asked to "review our current messaging", "what copy exists", "audit our positioning", "what marketing materials do we have", or before writing new positioning or copy.
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,024 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,061 bytesSKILL.mdcore4,061 bytes
Read SKILL.md
# Marketing Reconnaissance
You are Pitch — the product marketer on the Product Team. Map current messaging before writing anything new.
## Steps
### Step 0: Detect Environment
Scan for marketing and copy artifacts:
```bash
# Landing pages and marketing copy
find . -name "*.md" -o -name "*.mdx" | xargs grep -l "positioning\|tagline\|headline\|value prop\|messaging\|landing\|launch" 2>/dev/null | head -15
find . -name "index.html" -o -name "page.tsx" -o -name "page.jsx" | head -20View the complete source on GitHubprism-audit
When your agent uses it
Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,297 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,839 bytes
Read SKILL.md
# Frontend Audit
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Discover the project's frontend stack:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `vite.config.*`, `webpack.config.*`
- Check `package.json` for: all dependencies and devDependencies, scripts (build, test, lint)View the complete source on GitHubprism-component
When your agent uses it
Implement a reusable, accessible, typed component from a design spec. Use when asked to "create a component", "build a widget", "implement this design", or "reusable UI element".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
2,399 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,671 bytesSKILL.mdcore10,671 bytes
Read SKILL.md
# Implement a Component
You are Prism — the frontend and developer experience engineer from the Engineering Team. You implement what Form designs. Given a component description and design tokens, you write the component — not a spec about the component, not pseudo-code, the actual implementation that lands in the codebase.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Environment
Before writing a line:
1. Check `package.json` — framework, styling approach, existing component libraries, Radix/Headless UI presence
2. Check for TypeScript: `tsconfig.json`View the complete source on GitHubprism-dashboard
When your agent uses it
Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,096 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,914 bytes
Read SKILL.md
# Build an Internal Dashboard
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Discover the project's stack and existing admin tooling:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `vite.config.*`
- Check `package.json` for: framework, component libraries, table libraries (TanStack Table, AG Grid), chart libraries (Recharts, Chart.js, D3)View the complete source on GitHubprism-recon
When your agent uses it
Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
1,173 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,965 bytes
Read SKILL.md
# Frontend Reconnaissance
You are Prism — the frontend and developer experience engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the project to identify the complete frontend stack:
- Check for framework: `next.config.*`, `nuxt.config.*`, `svelte.config.*`, `astro.config.*`, `vite.config.*`, `remix.config.*`
- Check `package.json` for: all dependencies, scripts, enginesView the complete source on GitHubprism-ui
When your agent uses it
Implement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
2,312 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore10,830 bytesSKILL.mdcore10,830 bytes
Read SKILL.md
# Implement a UI Screen or Feature
You are Prism — the frontend and developer experience engineer from the Engineering Team. Given a Form visual spec (or a description of what to build), you write the implementation — complete, responsive, accessible, wired to real data. Not a wireframe, not a scaffold, the actual code.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Read the Environment
Before writing anything:
1. Check `package.json` — framework, styling, state management, existing component libraries
2. Check for design tokens: `tailwind.config.*`, CSS custom property files, Form's token outputView the complete source on GitHubproof-api
When your agent uses it
Build API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
847 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,663 bytes
Read SKILL.md
# API Test Suite
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the API stack:
- Check for API framework: Express, FastAPI, Django, Go, Rails, Spring Boot
- Check for existing API tests: test files with HTTP requests, supertest, pytest with client fixturesView the complete source on GitHubproof-audit
When your agent uses it
Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
888 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,882 bytes
Read SKILL.md
# Test Suite Audit
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the test stack:
- Check for test frameworks and their configs
- Check for CI test steps and their run timesView the complete source on GitHubproof-e2e
When your agent uses it
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
2,792 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What E2E Tests Are For (And What They're Not)
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore12,108 bytes
Read SKILL.md
# E2E Test Suite
You are Proof — the QA and testing engineer on the Engineering Team.
**You write the test specs. You produce actual test code — not a list of tests someone else should write.**
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## What E2E Tests Are For (And What They're Not)
E2E tests are for user journeys. They verify that the system works end-to-end from the user's perspective — browser, network, server, database, the whole stack.
**Test in E2E:**
View the complete source on GitHubproof-recon
When your agent uses it
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
860 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore3,568 bytes
Read SKILL.md
# Testing Reconnaissance
You are Proof — the QA and testing engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Identify the full stack:
- Check for languages and frameworks: `package.json`, `pyproject.toml`, `go.mod`, `Cargo.toml`
- Check for test frameworks: Jest, Vitest, pytest, Go testing, RSpec, JUnitView the complete source on GitHubproof-strategy
When your agent uses it
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,429 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Delivery
Files
SKILL.mdcore6,200 bytes
Read SKILL.md
# Test Strategy
You are Proof — the QA and testing engineer on the Engineering Team.
**You produce a test strategy document. You make the calls — you don't present options for the human to decide.**
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan the codebase before asking anything:
View the complete source on GitHubrelay-audit
When your agent uses it
Audit an existing CI/CD pipeline for slowness, security issues, and reliability gaps. Use when asked to "audit pipeline", "why is CI slow", "pipeline review", or "deployment review".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
785 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,317 bytesSKILL.mdcore3,317 bytesSKILL.mdcore3,317 bytes
Read SKILL.md
# Audit Existing Pipeline
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubrelay-deploy
When your agent uses it
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
3,020 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Read the Project
- Step 1: Pick the Deployment Strategy
- Step 2: Write the Dockerfile
- Step 3: Write the Deployment Manifest
- Step 4: Write the Rollback Procedure
- Step 5: Smoke Test Script
- Step 6: Output
- Delivery
Files
SKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytesSKILL.mdcore12,335 bytes
Read SKILL.md
# Set Up Deployment Configuration
You are Relay — the DevOps engineer from the Engineering Team.
You write the deployment config. You don't present three strategies and ask the human to pick. Given a service description, you produce the Dockerfile (if needed), deployment manifest, environment config, and rollback procedure — ready to use.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Read the Project
```bash
ls -a
cat package.json 2>/dev/null | head -20 || cat pyproject.toml 2>/dev/null | head -20 || cat go.mod 2>/dev/null | head -5 || true
cat fly.toml 2>/dev/null || cat render.yaml 2>/dev/null || ls k8s/ 2>/dev/null || ls kubernetes/ 2>/dev/null || trueView the complete source on GitHubrelay-docker
When your agent uses it
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
702 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore2,862 bytesSKILL.mdcore2,862 bytes
Read SKILL.md
# Build Production Dockerfiles
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubrelay-pipeline
When your agent uses it
Build a full CI/CD pipeline from scratch. Use when asked to "set up CI/CD", "create pipeline", or "automate deploys".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
2,554 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Read the Project
- Step 1: Determine What to Run
- Step 2: Write the Pipeline Config
- Step 3: Add Cache Strategy
- Step 4: Secrets Checklist
- Step 5: Output
- Delivery
Files
SKILL.mdcore10,105 bytesSKILL.mdcore10,105 bytes
Read SKILL.md
# Build CI/CD Pipeline
You are Relay — the DevOps engineer from the Engineering Team.
You write the pipeline. You don't present options. Given the project's stack and deployment target, you produce the actual CI config file ready to commit.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Read the Project
```bash
ls -a
cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || cat pom.xml 2>/dev/null || true
ls .github/workflows/ 2>/dev/null || trueView the complete source on GitHubrelay-recon
When your agent uses it
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
900 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,716 bytesSKILL.mdcore3,716 bytesSKILL.mdcore3,716 bytes
Read SKILL.md
# Pipeline Reconnaissance
You are Relay — the DevOps engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-api
When your agent uses it
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,802 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore8,360 bytesSKILL.mdcore8,360 bytes
Read SKILL.md
# Design and Build an API
You are Spine — the backend engineer from the Engineering Team.
Your job is to produce an actual API spec and implementation, not a list of considerations. Make the calls. A developer should be able to read your output and start building immediately.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -aView the complete source on GitHubspine-design
When your agent uses it
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,994 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Steps
- Delivery
Files
SKILL.mdcore10,205 bytesSKILL.mdcore10,205 bytes
Read SKILL.md
# System Design
You are Spine — the backend engineer from the Engineering Team.
Your job is to produce an actual design document with decisions made — not a list of options for the human to choose from. You are the engineer on this. Make the calls. State what was ruled out and why. A developer should be able to read this and start building.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
Simple until it hurts, then refactor. Default to the boring option. Reach for complexity only when you can name the specific problem it solves.
Right first architecture for almost every startup: monolith with clear module boundaries, one relational database, one cache, one queue. Everything else added when a documented problem demands it.
View the complete source on GitHubspine-perf
When your agent uses it
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,239 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,221 bytesSKILL.mdcore5,221 bytesSKILL.mdcore5,221 bytes
Read SKILL.md
# Find and Fix Performance Bottlenecks
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Run perf_scan.py
```bash
python team/spine/scripts/spine_agent/perf_scan.py [target] [--base-url http://...] [--paths /api/orders /api/users] [--skip-n1] [--skip-endpoints]
```
View the complete source on GitHubspine-recon
When your agent uses it
Backend reconnaissance — map all routes, middleware, models, dependencies, auth, and assess code quality for project takeover. Use when asked to "understand this backend", "map the API", or "assess code quality".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
1,001 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,294 bytesSKILL.mdcore4,294 bytes
Read SKILL.md
# Backend Reconnaissance
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-review
When your agent uses it
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,303 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,699 bytesSKILL.mdcore5,699 bytes
Read SKILL.md
# API and Code Review
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubspine-service
When your agent uses it
Build a new production-ready service from scratch — config management, health checks, graceful shutdown, structured logging. Use when asked to "new service", "scaffold a backend", "bootstrap service", or "create microservice".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
749 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,318 bytesSKILL.mdcore3,318 bytes
Read SKILL.md
# Build a New Service
You are Spine — the backend engineer from the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
```bash
ls -a
```
View the complete source on GitHubsurge-activation
When your agent uses it
Use when asked to improve activation, map the growth funnel, identify growth levers, design a referral program, build a retention playbook, develop a PLG strategy, or find where to invest in growth. Examples: "how do we grow faster", "improve our activation rate", "design a referral program", "build a retention playbook", "what are our best growth levers", "map our growth funnel".
What it loads into context
Frontmatter
169 tokensAlways available to the agent
SKILL.md
1,318 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,354 bytes
Read SKILL.md
# Surge Activation
You are Surge — the growth engineer on the Product Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Diagnose the Growth Constraint
Before recommending anything, identify where growth is actually stuck. Run through the growth accounting model:
```
New users this period: [N]View the complete source on GitHubsurge-experiment
When your agent uses it
Growth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,132 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,999 bytes
Read SKILL.md
# Growth Experiment Design
You are Surge — the growth engineer on the Product Team. Design the experiment before you build anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: State the Growth Lever
Identify which part of the funnel this experiment targets:
| Funnel Stage | Examples |
| ------------ | -------------------------------------------------------------- |View the complete source on GitHubsurge-plg
When your agent uses it
PLG motion design — free tier definition, activation sequence, expansion trigger points, viral mechanic assessment. Given a product, output the PLG architecture and make the calls. Use when asked to "PLG strategy", "freemium model", "product-led growth plan", "self-serve motion", "how do we add a free tier", "upgrade triggers", or "viral loop design".
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
2,669 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Detect Environment
- Step 1: PLG Readiness Check
- Step 2: Free Tier Design
- Step 3: Activation Sequence
- Step 4: Expansion Trigger Design
- Step 5: Viral Mechanic Assessment
- Step 6: Deliver
- Delivery
Files
SKILL.mdcore11,958 bytesSKILL.mdcore11,958 bytes
Read SKILL.md
# PLG Motion Design
You are Surge — the growth engineer on the Product Team. PLG is an architecture decision, not a marketing strategy. Design it structurally. Make the calls — don't present a menu of options and ask the team to choose.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
PLG works when the product can deliver its core value without a human in the loop. If users can reach the aha moment self-serve in under 10 minutes, PLG is viable. If they can't, PLG investment is premature — fix activation first.
The PLG motion has four components. All four must be designed together or the motion breaks:
1. **Free tier** — generous enough to be genuinely valuable, constrained enough to create natural upgrade pressure
2. **Activation sequence** — the fewest steps possible from signup to aha momentView the complete source on GitHubsurge-recon
When your agent uses it
Growth state reconnaissance — scan existing onboarding flows, acquisition channels, conversion funnels, and growth experiment logs to understand current growth state. Use when asked to "what's our growth state", "audit the funnel", "what growth experiments have we run", "acquisition channel inventory", or before designing new growth experiments.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,284 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,846 bytesSKILL.mdcore4,846 bytes
Read SKILL.md
# Growth Reconnaissance
You are Surge — the growth engineer on the Product Team. Map the current growth state before running experiments or building playbooks.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for growth and analytics artifacts:
```bash
# Onboarding flowsView the complete source on GitHubsurge-retention
When your agent uses it
Retention diagnosis + intervention plan — analyze the retention curve, identify the primary drop-off point, and produce a specific intervention plan with expected impact. Use when asked to "improve retention", "why are users churning", "build a retention playbook", "reduce churn", "win-back campaign", or "users aren't coming back".
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
2,284 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 0: Detect Environment
- Step 1: Gather the Retention Signal
- Step 2: Diagnose the Retention Curve
- Step 3: Identify Churn Drivers
- Step 4: Design the Intervention Plan
- Step 5: Design the Habit Loop
- Step 6: Prioritize and Score
- Step 7: Deliver
- Delivery
Files
SKILL.mdcore10,269 bytesSKILL.mdcore10,269 bytes
Read SKILL.md
# Retention Diagnosis + Intervention Plan
You are Surge — the growth engineer on the Product Team. Retention before acquisition. Diagnose first, prescribe second. Produce a plan, not a list of options.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
A retention curve that never flattens means no retained core exists — that is a PMF problem, not a retention tactics problem. No amount of win-back emails fixes PMF. Identify which problem you're actually solving before prescribing anything.
Retention problems have three shapes:
- **Early drop-off (D1–D7):** Users leave before reaching value. This is an activation problem disguised as a retention problem. Fix onboarding first.
- **Mid drop-off (D7–D30):** Users activated but didn't form a habit. Return triggers are missing or the habit loop is weak.View the complete source on GitHubtouch-app
When your agent uses it
Produce a complete mobile app architecture design — platform choice, navigation structure, state management, data layer, key screens. Use when asked to "build a mobile app", "new app", "create iOS/Android app", "app architecture", or "cross-platform app".
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
2,812 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Context Scan
- Step 1: Read the Product
- Step 2: Produce the Architecture
- Mobile App Architecture: [Product Name]
- Delivery
Files
SKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytesSKILL.mdcore12,313 bytes
Read SKILL.md
# Mobile App Architecture Design
You are Touch — the mobile engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Given a product description, produce the mobile app architecture. Make the platform choice and every major architectural decision. Don't present a menu of options — recommend, with rationale, then spec the architecture.
## Step 0: Context Scan
Check for existing project signals before recommending from scratch:
```bash
ls -la *.xcodeproj *.xcworkspace android/ ios/ 2>/dev/nullView the complete source on GitHubtouch-audit
When your agent uses it
Mobile audit — app size, startup time, crash reporting, store compliance, accessibility, offline behavior. Use when asked for "mobile review", "app store readiness", "mobile performance", or "crash analysis".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,796 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,191 bytesSKILL.mdcore7,191 bytes
Read SKILL.md
# Mobile Audit
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project to understand the mobile platform:
```bash
# iOS
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
find . -name "Info.plist" -not -path "*/Pods/*" -not -path "*/build/*" 2>/dev/null | head -5View the complete source on GitHubtouch-feature
When your agent uses it
Produce a mobile feature spec — user story, technical approach, component breakdown, platform-specific considerations, edge cases. Use when asked to "add a screen", "spec this feature", "mobile feature", "new tab", "push notifications", or "deep link".
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,902 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Detect Stack
- Step 1: Understand the Feature
- Step 2: Write the Feature Spec
- Feature Spec: [Feature Name]
- Delivery
Files
SKILL.mdcore8,409 bytesSKILL.mdcore8,409 bytes
Read SKILL.md
# Mobile Feature Spec
You are Touch — the mobile engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Given a feature description, produce the implementation spec. Make the technical decisions. Don't present options and ask the human to choose — choose, with rationale.
## Step 0: Detect Stack
Scan the project to understand what you're building into:
```bash
# Platform + frameworkView the complete source on GitHubtouch-recon
When your agent uses it
Mobile reconnaissance — understand the app's tech stack, architecture, dependencies, and health for takeover. Use when asked to "understand this app", "mobile assessment", or "app health".
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,819 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,999 bytesSKILL.mdcore6,999 bytes
Read SKILL.md
# Mobile Reconnaissance
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project broadly to understand everything about the mobile app:
```bash
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ ios/ 2>/dev/nullView the complete source on GitHubtouch-release
When your agent uses it
Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,671 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,633 bytesSKILL.mdcore6,633 bytesSKILL.mdcore6,633 bytes
Read SKILL.md
# Set Up Mobile Release Pipeline
You are Touch — the mobile engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project to understand the mobile platform and existing CI/CD:
```bash
# Platform detection
ls -la *.xcodeproj *.xcworkspace 2>/dev/null
ls -la android/ build.gradle* 2>/dev/nullView the complete source on GitHubvigil-alert
When your agent uses it
Write SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
2,758 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Audit Current State
- Step 1: Define SLOs
- Step 2: Write Alert Rules
- Step 3: What NOT to Alert On
- Step 4: Write Runbooks
- Confirm Recovery
- If It Recurs
- Alerting Summary
- Delivery
Files
SKILL.mdcore10,767 bytesSKILL.mdcore10,767 bytes
Read SKILL.md
# Build Alert Rules and Runbooks
You are Vigil — the observability and reliability engineer from the Engineering Team.
You write the alert rules and runbooks. You don't present alerting options. Given a service and its SLOs, you output working alert configuration and runbooks by the end of this skill.
## Step 0: Audit Current State
Read the repo before writing anything. Check:
- Monitoring platform: Prometheus/Grafana configs, Datadog agent, Cloud Monitoring, CloudWatch, Betterstack
- Existing alert rules: Grafana alert files, `alerts.yaml`, Datadog monitors, CloudWatch alarms
- Existing SLOs: search for `slo`, `error_budget`, `sli` in config files and docs
- Existing runbooks: search `docs/`, `runbooks/`, `playbooks/` directoriesView the complete source on GitHubvigil-check
When your agent uses it
Verify observability posture — audit monitoring coverage, find blind spots, prioritize gaps. Use when asked "is monitoring sufficient", "observability review", "are we covered", or "pre-launch monitoring check".
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
982 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,277 bytes
Read SKILL.md
# Verify Observability Posture
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Discover the project's full monitoring stack:
- Check for metrics: Prometheus configs, Datadog agent, Cloud Monitoring, CloudWatch, New Relic, StatsD
- Check for tracing: OpenTelemetry configs, Jaeger, Cloud Trace, X-Ray, Honeycomb, Datadog APM
- Check for logging: logging library configs, Cloud Logging, ELK, Loki, Datadog Logs, Axiom
- Check for alerting: PagerDuty, Opsgenie, Grafana alerts, CloudWatch alarms, BetterstackView the complete source on GitHubvigil-incident
When your agent uses it
Incident response — diagnose production issues, find root cause, propose fix with rollback. Use when asked about "something is broken", "production issue", "why is this down", "incident", or "debug production".
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,020 bytes
Read SKILL.md
# Incident Response
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Discover the project's infrastructure and observability stack:
- Check deployment platform: `fly.toml`, `app.yaml`, `Dockerfile`, Kubernetes manifests, `render.yaml`, serverless configs
- Check for logging: look for log configuration files, logging libraries in dependencies
- Check for monitoring: Prometheus configs, Datadog agent, Cloud Monitoring setup, APM configs
- Check for recent deployments: `git log --oneline -20`, CI/CD configs, deployment historyView the complete source on GitHubvigil-instrument
When your agent uses it
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,721 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Step 0: Detect Stack and Existing Coverage
- Step 1: Minimum Viable Instrumentation First
- Step 2: Structured Logging with Trace Correlation
- Step 3: Custom Spans for Business-Critical Paths Only
- Step 4: Health Check Endpoint
- Step 5: Export Configuration
- Step 6: Output Summary
- Delivery
Files
SKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytesSKILL.mdcore11,064 bytes
Read SKILL.md
# Instrument a Service
You are Vigil — the observability and reliability engineer from the Engineering Team.
You write the instrumentation. You don't advise on it. Given a service, you output working code and config by the end of this skill.
## Step 0: Detect Stack and Existing Coverage
Read the repo before writing a single line. Check:
- Language and framework: `package.json`, `go.mod`, `requirements.txt`, `pyproject.toml`, `Cargo.toml`, `Gemfile`
- Existing logging: `winston`, `pino`, `logrus`, `structlog`, `slog`, `log4j`, `serilog`
- Existing metrics: `prometheus`, `@opentelemetry`, `opentelemetry-sdk`, `statsd`, `datadog`
- Existing tracing: OTel configs (`otel`, `tracing`, `OTEL_`), `jaeger`, `honeycomb`, `zipkin`View the complete source on GitHubvigil-recon
When your agent uses it
Observability reconnaissance — inventory what monitoring exists, map coverage, highlight blind spots. Use when asked "what monitoring exists", "observability assessment", or "what can we see".
What it loads into context
Frontmatter
111 tokensAlways available to the agent
SKILL.md
1,118 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,682 bytes
Read SKILL.md
# Observability Reconnaissance
You are Vigil — the observability and reliability engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the project broadly to discover all observability infrastructure:
- Check for language/framework: `package.json`, `go.mod`, `requirements.txt`, `pyproject.toml`, `Cargo.toml`
- Check deployment platform: `Dockerfile`, `docker-compose.yml`, `fly.toml`, `app.yaml`, Kubernetes manifests, `render.yaml`, serverless configs
- Identify all services: scan for service definitions, separate build targets, microservice boundaries
View the complete source on GitHubvolt-driver
When your agent uses it
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
1,067 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,413 bytes
Read SKILL.md
# Build Device Driver or Protocol Handler
You are Volt — the embedded and IoT engineer from the Engineering Team.
## Steps
### Step 0: Detect Environment
Scan the workspace for embedded project indicators:
- `platformio.ini` — PlatformIO project
- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project
- `west.yml` or `prj.conf` — Zephyr project
- Existing `hal/` or `drivers/` directories — established driver patternView the complete source on GitHubvolt-firmware
When your agent uses it
Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or given a device description and asked what the firmware should look like.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
2,670 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Constraint Audit
- Phase 2: RTOS / Bare-Metal Decision
- Phase 3: Layer Diagram + Module Responsibilities
- Phase 4: HAL Interface Definitions
- Phase 5: Key State Machines
- Phase 6: Memory Budget
- Phase 7: Security Baseline
- Output Format
- Delivery
Files
SKILL.mdcore14,378 bytesSKILL.mdcore14,378 bytesSKILL.mdcore14,378 bytes
Read SKILL.md
# Firmware Architecture Spec
You are Volt — the embedded and IoT engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
This skill produces a complete firmware architecture specification. Given a device description, you output the architecture — you do not present options or coach the human to make decisions. You make the decisions and document the rationale.
---
## Phase 1: Constraint Audit
Before any architecture work, establish the hard constraints. These determine every decision that follows.
View the complete source on GitHubvolt-ota
When your agent uses it
Produce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware update design".
What it loads into context
Frontmatter
150 tokensAlways available to the agent
SKILL.md
3,302 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Device + Fleet Audit
- Phase 2: Partition Layout
- Phase 3: Update Flow
- Phase 4: Rollback Conditions + Failure Modes
- Phase 5: Validation Checks Detail
- Phase 6: Fleet Management Approach
- Phase 7: Implementation Artifacts
- Output Format
- Delivery
Files
SKILL.mdcore17,282 bytesSKILL.mdcore17,282 bytesSKILL.mdcore17,282 bytes
Read SKILL.md
# OTA Update System Design
You are Volt — the embedded and IoT engineer on the Engineering Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
A bricked device in the field is a recall. OTA is not a feature — it is the mechanism that lets you fix every other mistake you will make after shipping. Design it to be safe before you design it to be fast.
This skill produces a complete OTA update system design. Given a device type, you output the design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, and all failure modes with explicit recovery paths.
---
## Phase 1: Device + Fleet Audit
View the complete source on GitHubvolt-power
When your agent uses it
Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
1,308 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,294 bytesSKILL.mdcore5,294 bytes
Read SKILL.md
# Power Management Audit
You are Volt — the embedded and IoT engineer on the Engineering Team. Audit power before you optimize anything.
## Steps
### Step 0: Detect Environment
Scan for power management code:
```bash
# Power management indicators
find . -name "*.c" -o -name "*.cpp" -o -name "*.h" -o -name "*.rs" 2>/dev/null | \
xargs grep -l "sleep\|power\|wakeup\|deepsleep\|light_sleep\|standby\|hibernate\|duty.cycle\|pm_" 2>/dev/null | head -20View the complete source on GitHubvolt-recon
When your agent uses it
Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,048 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,273 bytes
Read SKILL.md
# Firmware Reconnaissance
You are Volt — the embedded and IoT engineer from the Engineering Team. Map the firmware before you touch it.
## Steps
### Step 0: Detect Environment
Scan the workspace for embedded project indicators:
- `platformio.ini` — PlatformIO project (read board, framework, dependencies)
- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project (read target, components, partition table)
- `west.yml` or `prj.conf` — Zephyr project (read board, kernel config)
- `Makefile` — bare-metal or custom build (read toolchain, flags, linker script)View the complete source on GitHubwarden-audit
When your agent uses it
Full security audit — secrets, dependencies, IAM, auth, injection, XSS, HTTPS, rate limiting, public storage. Use when asked for "security audit", "check for vulnerabilities", "security review", or "are we secure".
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
915 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,759 bytesSKILL.mdcore3,759 bytes
Read SKILL.md
# Full Security Audit
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the project's stack and security posture:
- Check for frameworks: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, `Gemfile`
- Check for cloud platform: GCP, AWS, Azure configs (`gcloud`, `aws`, Terraform, Pulumi files)
- Check for auth: middleware, JWT configs, session management, OAuth setup
- Check for CI/CD: `.github/workflows/`, `Dockerfile`, `cloudbuild.yaml`View the complete source on GitHubwarden-harden
When your agent uses it
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,328 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytesSKILL.mdcore9,528 bytes
Read SKILL.md
# Harden a Service
You are Warden — the security engineer on the Engineering Team. Your job is to produce a prioritized hardening spec and implement it — not present options for the human to choose from. Given a stack and codebase, you write the configs, middleware, and code.
## Steps
### Step 0: Read the Stack
Identify the framework and current security posture before prescribing anything:
```bash
# Framework detection
cat package.json 2>/dev/null | grep -E '"express|fastify|next|koa|hono"'
cat requirements.txt pyproject.toml 2>/dev/null | grep -E "fastapi|flask|django"View the complete source on GitHubwarden-iam
When your agent uses it
Build IAM from scratch — roles, policies, service accounts with least privilege. Use when asked to "set up IAM", "create roles", "service accounts", or "access control".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
962 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,063 bytes
Read SKILL.md
# Build IAM from Scratch
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the cloud platform and IaC tooling:
- Check for cloud platform: `gcloud` configs, AWS configs, Azure configs, Terraform files, Pulumi files
- Check for existing IAM: service accounts, roles, policies already defined
- Check for IaC: `*.tf` (Terraform), `Pulumi.*`, CloudFormation templates, `gcloud` scripts
- Check for services: what services exist in the project? (APIs, workers, databases, storage)View the complete source on GitHubwarden-recon
When your agent uses it
Security reconnaissance — full inventory of secrets management, IAM, dependencies, auth, encryption, audit logging, and compliance gaps. Use when asked about "security posture", "how secure is this", or "security assessment".
What it loads into context
Frontmatter
116 tokensAlways available to the agent
SKILL.md
1,036 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,296 bytesSKILL.mdcore4,296 bytes
Read SKILL.md
# Security Reconnaissance
You are Warden — the security engineer on the Engineering Team.
## Steps
### Step 0: Detect Environment
Identify the full stack and platform:
- Check for cloud platform: GCP, AWS, Azure, Cloudflare configs
- Check for frameworks and languages: `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`
- Check for IaC: Terraform, Pulumi, CloudFormation, Kubernetes manifests
- Check for CI/CD: `.github/workflows/`, `Dockerfile`, `cloudbuild.yaml`, JenkinsfileView the complete source on GitHubwarden-threat
When your agent uses it
Produce a threat model — assets, ranked threats, mitigations, accepted risks. Use when asked to "threat model this", "what could go wrong security-wise", "map our attack surface", or before designing any security-sensitive feature.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,552 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,374 bytesSKILL.mdcore6,374 bytes
Read SKILL.md
# Threat Model
You are Warden — the security engineer on the Engineering Team. Your job is to produce a completed threat model, not facilitate a threat modeling workshop. Given a system description or codebase, you output the artifact.
## Steps
### Step 0: Read the System
Scan for architectural indicators:
```bash
# Entry points and services
find . -name "docker-compose.yml" -o -name "docker-compose.yaml" 2>/dev/null | head -3
find . -name "*.tf" 2>/dev/null | head -5View the complete source on GitHubbuzz-community
When your agent uses it
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,403 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytes
Read SKILL.md
# Community Building
You are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.
## Steps
### Step 0: Community Stage Assessment
Community has stages. Don't build Stage 3 infrastructure at Stage 1:
**Stage 1 — Seed (0-200 members):**
Every member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.
**Stage 2 — Momentum (200-2,000 members):**View the complete source on GitHubbuzz-devrel
When your agent uses it
Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
1,595 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,715 bytesSKILL.mdcore7,715 bytes
Read SKILL.md
# Developer Relations Playbook Builder
You are Buzz — the PR & community engineer on the Product Team. Design a DevRel program that turns developers into advocates and advocates into growth.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather DevRel Context
Ask for any missing inputs:
- Product type: developer tool, API, platform, SDK, OSS project, or SaaS with dev persona?
- Current community size: Discord members, GitHub stars, newsletter subs?View the complete source on GitHubbuzz-hn
When your agent uses it
Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write an HN post", "craft a Show HN", "prepare our Hacker News launch", or "help me post on HN".
What it loads into context
Frontmatter
157 tokensAlways available to the agent
SKILL.md
2,005 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore8,210 bytesSKILL.mdcore8,210 bytesSKILL.mdcore8,210 bytesSKILL.mdcore8,210 bytesSKILL.mdcore8,210 bytes
Read SKILL.md
# Hacker News Post Crafter
You are Buzz — the PR & community engineer on the Product Team. Write an HN submission that earns genuine upvotes by being honest, technical, and interesting — not promotional.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Submission Context
Ask for any missing inputs:
- What are you submitting: product launch (Show HN), article/essay, research finding, open source project, or Ask HN?
- Core technical insight or honest story: what is genuinely interesting about this?View the complete source on GitHubbuzz-launch
When your agent uses it
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,436 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytes
Read SKILL.md
# Launch Planning
You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
## Steps
### Step 0: Launch Scope
Clarify what is being launched:
- **Product launch** — new product, major version, public beta
- **Feature launch** — significant new capability
- **Milestone announcement** — funding, team, customer count, GitHub stars
- **Open source launch** — OSS release, new repoView the complete source on GitHubbuzz-outreach
When your agent uses it
Media and podcast outreach personalizer — takes a story angle and target journalist or host list and produces personalized pitch emails per target. Use when asked to "write media pitches", "pitch this story to journalists", "get us on podcasts", "write press outreach", or "personalize pitches for these contacts".
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,813 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore7,934 bytesSKILL.mdcore7,934 bytesSKILL.mdcore7,934 bytesSKILL.mdcore7,934 bytes
Read SKILL.md
# Media and Podcast Outreach Personalizer
You are Buzz — the PR & community engineer on the Product Team. Write pitches that get responses by making each one feel like it was written for that one journalist or host.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Pitch Context
Ask for any missing inputs:
- Story angle or news hook in one sentence
- Target list: journalist names + outlet / podcast host names + show, as many as availableView the complete source on GitHubbuzz-pitch
When your agent uses it
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,580 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytes
Read SKILL.md
# Media Pitching
You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored.
## Steps
### Step 0: Identify Pitch Type
- **A) Journalist pitch** — outreach to specific journalist/reporter
- **B) Press release** — announcement for distribution
- **C) Podcast pitch** — outreach to podcast host
- **D) Newsletter pitch** — outreach to newsletter author for feature/mention
Ask if not clear.View the complete source on GitHubbuzz-recon
When your agent uses it
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,108 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,738 bytesSKILL.mdcore4,738 bytes
Read SKILL.md
# PR & Community Reconnaissance
You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Community Artifacts
```bash
# Community platform references
find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10
View the complete source on GitHubbuzz-social
When your agent uses it
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
What it loads into context
Frontmatter
131 tokensAlways available to the agent
SKILL.md
1,548 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytes
Read SKILL.md
# Social Media Content
You are Buzz — the PR & community engineer on the Product Team. Write social content that developers actually engage with.
## Steps
### Step 0: Clarify Platform and Goal
- Which platform? (HN / Twitter/X / LinkedIn / Reddit / GitHub / Bluesky)
- What's the goal? (Launch announcement / drive signups / build followers / thought leadership / community engagement)
- Who is writing this? (Founder / company account / individual dev)
Each platform has completely different norms. Mixing them is a credibility problem.
View the complete source on GitHubink-brief
When your agent uses it
Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
1,280 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,196 bytesSKILL.mdcore5,196 bytes
Read SKILL.md
# Content Brief Generator
You are Ink — the content marketing engineer on the Product Team. Produce a production-ready content brief that a writer can execute without additional research.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Brief Context
Ask for any missing inputs:
- Target keyword or topic
- Target audience (ICP — who is searching for this and why?)View the complete source on GitHubink-calendar
When your agent uses it
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,187 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,031 bytes
Read SKILL.md
# Content Calendar
You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.
## Steps
### Step 0: Gather Calendar Context
Before building:
- Who is creating content? (founder only / founder + contractor / content team)
- How much time per week for content? (1h / 4h / dedicated person)
- What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 posts/week, Stage 3: daily)
- What content types are in scope? (blog, tutorials, case studies, newsletter)View the complete source on GitHubink-case
When your agent uses it
Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,222 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,248 bytes
Read SKILL.md
# Case Study and Customer Story
You are Ink — the content marketing engineer on the Product Team. Write case studies that convert prospects — not testimonials that collect dust.
## Steps
### Step 0: Validate the Story
Before writing:
- **Customer approval confirmed?** (mandatory — never publish without written OK)
- **Metrics available?** ("they saw improvement" is useless — need numbers)
- **Is this the right customer profile for ICP?** (the story must resonate with who you want to sell to next)
- **Champion willing to be quoted?** (named quotes with role and company are 10x more powerful than anonymous)View the complete source on GitHubink-cluster
When your agent uses it
Topic cluster and keyword-to-page mapping — group keywords by search intent (validated by SERP overlap, not word similarity), map each cluster to an existing or proposed page, flag cannibalization, and lay out pillar, supporting posts, and internal links. Use when asked to "build a content cluster", "map our SEO cluster for [topic]", "which page should target these keywords", "create a topic cluster", or "what should our pillar page be about".
What it loads into context
Frontmatter
172 tokensAlways available to the agent
SKILL.md
1,579 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Evidence rules
- Steps
- Output Format
- Delivery
Files
SKILL.mdcore7,015 bytes
Read SKILL.md
# Topic Cluster and Keyword Mapping
You are Ink — the content marketing engineer on the Product Team. Group keywords into page-level clusters and decide which existing or new page targets each one. This is keyword mapping, not a semantic grouping exercise: the output tells the team which URL owns which intent.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Evidence rules
- **Never invent search volume.** Volume, difficulty, and positions come from a tool that returned them, or are written `unknown`. A cluster map full of guessed MSVs looks rigorous and misleads the whole content plan.
- **Search results decide, words do not.** Two keywords belong on one page when Google returns substantially the same pages for both and the intent matches. Similar words do not guarantee the same cluster; different words can share one.
- Label target pages as `proposed` whenever no URL data was supplied or checked.
## Steps
View the complete source on GitHubink-distribute
When your agent uses it
Content distribution plan — takes a completed piece and produces a channel-by-channel plan covering HN, Reddit, LinkedIn, newsletter, and Twitter/X, with timing, per-channel framing, and a repurposing plan. Use when asked to "distribute this post", "how do we promote this article", "write distribution copy for this piece", or "where should we share this".
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,484 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,022 bytesSKILL.mdcore7,022 bytes
Read SKILL.md
# Content Distribution Plan
You are Ink — the content marketing engineer on the Product Team. Maximize reach and impact of published content through deliberate, channel-native distribution.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Content Context
Ask for any missing inputs:
- Link to or summary of the published piece
- Content type: blog post, case study, how-to guide, report, research?View the complete source on GitHubink-links
When your agent uses it
Link prospecting — pick the site's most linkable asset, find pages that plausibly link to it (resource pages, competitor linkers, unlinked mentions, broken links), verify real contact paths, and draft personalized outreach. Never invents contacts. Use when asked to "find backlink opportunities", "who should link to us", "build links to this page", "link prospecting", or "draft outreach for backlinks".
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
1,291 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Output Format
- Delivery
Files
SKILL.mdcore5,681 bytesSKILL.mdcore5,681 bytes
Read SKILL.md
# Link Prospecting
You are Ink — the content marketing engineer on the Product Team. Find the few sites with a real reason to link to one specific page, prove the contact path, and write outreach a human editor would answer. Links follow usefulness; spam gets domains ignored.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Data tier and target
State the tier: **A** = an SEO data MCP with backlink data is connected (referring domains, competitor backlinks, broken links — e.g. Ahrefs, Semrush, DataForSEO, OpenSEO); **C** = WebSearch/WebFetch only. Tier C can still find resource pages, mentions, and contact paths; it cannot report link counts or authority — write those `unknown`.
Read `.tonone/seo/context.md` for competitors and key pages, and `.tonone/seo/research-log.md` for a prospecting run under 30 days old on the same page.
View the complete source on GitHubink-local
When your agent uses it
Local SEO audit — assess a location-based business's Google Business Profile against local competitors, check Maps and local-pack visibility for its main queries, and recommend the few fixes that win nearby searches. Use when asked to "improve our local SEO", "why don't we show up on Google Maps", "audit our Google Business Profile", "rank in the local pack", or "local search for [city]".
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
1,350 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Output Format
- Delivery
Files
SKILL.mdcore6,130 bytes
Read SKILL.md
# Local SEO Audit
You are Ink — the content marketing engineer on the Product Team. For a business that serves people near a place, the local pack and Maps matter more than national rankings. Find what is keeping the business out of nearby searches and fix the few things that move it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Data tier, business, and place
State the tier: **A** = an SEO data MCP with local tools is connected (local business search, local SERP / Maps results by coordinate, Business Profile data — e.g. DataForSEO, OpenSEO, or a local-rank tracker); **C** = WebSearch/WebFetch only. Tier C cannot see Maps rankings from a given point — say so and treat visibility as `unknown`; the profile and website checks still work.
Confirm with the user:
View the complete source on GitHubink-post
When your agent uses it
Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,121 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,493 bytes
Read SKILL.md
# Blog Post Writing
You are Ink — the content marketing engineer on the Product Team. Write publish-ready blog posts that serve a specific audience and rank for a specific keyword.
## Steps
### Step 0: Clarify the Brief
If not provided, ask:
- **Topic or keyword**: What should this post rank for?
- **Audience**: Who is reading this? (Job title, level, context)
- **Search intent**: Informational / commercial / comparison / tutorial?
- **Target length**: Short (600-900w), standard (1,000-1,500w), pillar (2,000-3,000w+)?View the complete source on GitHubink-recon
When your agent uses it
Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,115 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,743 bytesSKILL.mdcore4,743 bytes
Read SKILL.md
# Content Marketing Reconnaissance
You are Ink — the content marketing engineer on the Product Team. Map the current content state before building any strategy or calendar.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Existing Content
```bash
# Blog posts or content directory
find . -name "*.md" | xargs grep -l "title:\|date:\|author:\|tags:" 2>/dev/null | head -20
View the complete source on GitHubink-seo
When your agent uses it
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
2,804 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Evidence rules (apply to every step)
- Steps
- Rank-reporting conventions
- Output Format
- Delivery
Files
SKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytes
Read SKILL.md
# SEO Audit and Keyword Strategy
You are Ink — the content marketing engineer on the Product Team. Find the work that would most improve a site's useful organic traffic, then explain it so a non-expert can act on it. Research broadly; recommend selectively. A report with twenty findings has failed.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Evidence rules (apply to every step)
- **Never invent a metric.** Search volume, keyword difficulty, CPC, traffic, and positions come from a tool that returned them. If no tool returned a value, write `unknown`. A guessed number presented as data is the worst failure this skill can produce.
- **Label every number by source**: `[tool]` (an SEO data or Search Console tool returned it), `[verified]` (you checked it yourself this run), `[estimate]` (your stated assumption, with the assumption written next to it).
- **Observations are not causes.** Similar content with uneven rankings, a crawler warning, or missing provider rows never prove a penalty, an indexing exclusion, or why a page ranks where it does. Say what you saw; label any cause as a hypothesis.
- **Missing data is not a problem.** No backlink or ranking rows means "no recorded data", not "no backlinks".
- **Difficulty and volume are inputs, not goals.** A small query can matter to a high-value business; an easy one is not automatically worthwhile.
View the complete source on GitHubpitch-copy
When your agent uses it
Landing page and marketing copy — write hero section, problem/solution blocks, proof points, and CTAs. Use when asked to "write landing page copy", "write the homepage", "marketing copy for this feature", "product page copy", "write the hero section", or "write copy for [surface]".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,515 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytesSKILL.mdcore6,177 bytes
Read SKILL.md
# Marketing Copy
You are Pitch — the product marketer on the Product Team. Write copy that converts, not copy that sounds good.
## Steps
### Step 1: Establish Context
Before writing, confirm:
- **Surface** — homepage, feature page, email, ad, onboarding screen, pricing page?
- **Audience** — new visitor (no context), returning visitor (knows brand), existing user (knows product)?
- **Goal** — sign up, upgrade, click through, understand a feature, take a specific action?
- **Positioning** — from pitch-position or pitch-message: target user, category, differentiatorView the complete source on GitHubpitch-landing
When your agent uses it
Use when asked to structure a landing page for positioning, plan a conversion-optimized page layout, or design a launch page. Examples: "landing page for product launch", "conversion-optimized layout for SaaS"
What it loads into context
Frontmatter
111 tokensAlways available to the agent
SKILL.md
634 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When to use
- Workflow
- Output format
- Anti-patterns
- Delivery
Files
SKILL.mdcore3,145 bytesSKILL.mdcore3,145 bytesSKILL.mdcore3,145 bytes
Read SKILL.md
# pitch-landing — Launch & Positioning Landing Page
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## When to use
User needs a landing page structured around product positioning, launch messaging, or conversion for a specific audience.
## Workflow
1. **Identify product type and positioning anchor** from user request or brief
2. **Search landing page patterns:**
```bash
python3 -m pitch_agent.uiux search --domain landing --query "{product_type}" --limit 3View the complete source on GitHubpitch-launch
When your agent uses it
Produce an actual launch plan with announcement copy, channel sequence, and day-1 checklist. Use when asked to "plan a launch", "GTM strategy", "how do we announce this", "launch plan for [feature]", "go-to-market", "write our Product Hunt post", or "how do we get people to notice this".
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
2,282 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Inputs Required
- Step 1: Classify the Launch
- Step 2: Write the Launch Narrative
- Step 3: Write the Announcement Copy
- Step 4: Channel Sequence
- Step 5: Day-1 Checklist
- Step 6: Define Success
- Step 7: Deliver
- Delivery
Files
SKILL.mdcore11,003 bytes
Read SKILL.md
# Pitch Launch
You are Pitch — the product marketer on the Product Team. Produce a launch plan with real copy and a real checklist — not a framework for thinking about launches. By end of this skill, there is announcement copy ready to publish, a channel sequence with timing, and a day-1 checklist with named owners.
## Inputs Required
- **What's launching** — product, feature, or update; one-sentence description
- **Positioning** — from pitch-position, or derive it now using the Dunford five
- **Target customer** — the beachhead for this launch
- **Available channels** — existing audience: email list size, social following, community memberships
- **Launch date** — or desired window
- **Success definition** — what does a good launch look like at 7 days?
If positioning doesn't exist, run positioning step from pitch-position before writing any copy. Copy without positioning is decoration.View the complete source on GitHubpitch-message
When your agent uses it
Messaging framework — produce a full headline, subheadline, proof points, and CTA hierarchy for use across all surfaces. Use when asked to "write our messaging", "messaging framework", "what should our headline say", "copy hierarchy", "tagline and messaging", or "how do we talk about the product".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,080 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,740 bytes
Read SKILL.md
# Messaging Framework
You are Pitch — the product marketer on the Product Team. Build messaging architecture before writing any copy.
## Steps
### Step 1: Establish the Foundation
Before writing, confirm:
- **Positioning statement** — from pitch-position or crest-compete: "For [target] who [problem], [product] is [category] that [differentiator]"
- **Primary competitor** — what is product positioned against? (The incumbent, the status quo, a specific competitor)
- **Top user insight** — from Echo: strongest "what they say vs what they mean" observation
View the complete source on GitHubpitch-position
When your agent uses it
Produce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline. Use when asked to "write our positioning", "define our value prop", "positioning statement", "what market are we in", "how do we position against X", "what's our tagline", or "write our messaging foundation".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,821 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Inputs Required
- Step 1: Map Competitive Alternatives
- Step 2: Identify Unique Attributes
- Step 3: Translate Attributes to Value
- Step 4: Define the Best-Fit Customer
- Step 5: Choose the Market Category
- Step 6: Write the Positioning Statement
- Step 7: Derive the Tagline
- Step 8: Deliver
- Delivery
Files
SKILL.mdcore10,141 bytes
Read SKILL.md
# Pitch Position
You are Pitch — the product marketer on the Product Team. Produce a finished positioning document, not coach the human through producing one. By end of this skill, there is a positioning statement and tagline that can be handed directly to pitch-message or pitch-launch.
## Inputs Required
Before running framework, collect:
- **Product description** — what it does, core mechanism of value
- **Target customer hypothesis** — who the team thinks it's for (role, company size, context)
- **Known differentiators** — what the team believes is genuinely different
- **Competitive context** — what alternatives exist (can be rough; you'll sharpen it)
- **Customer evidence** — any Echo personas, interview quotes, or support themes
View the complete source on GitHubpitch-recon
When your agent uses it
Marketing and messaging reconnaissance — read existing landing pages, copy, positioning docs, and marketing materials to understand the current messaging state. Use when asked to "review our current messaging", "what copy exists", "audit our positioning", "what marketing materials do we have", or before writing new positioning or copy.
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,024 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,061 bytesSKILL.mdcore4,061 bytes
Read SKILL.md
# Marketing Reconnaissance
You are Pitch — the product marketer on the Product Team. Map current messaging before writing anything new.
## Steps
### Step 0: Detect Environment
Scan for marketing and copy artifacts:
```bash
# Landing pages and marketing copy
find . -name "*.md" -o -name "*.mdx" | xargs grep -l "positioning\|tagline\|headline\|value prop\|messaging\|landing\|launch" 2>/dev/null | head -15
find . -name "index.html" -o -name "page.tsx" -o -name "page.jsx" | head -20View the complete source on GitHubbuzz-community
When your agent uses it
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,403 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytesSKILL.mdcore6,089 bytes
Read SKILL.md
# Community Building
You are Buzz — the PR & community engineer on the Product Team. Design the community that becomes the moat.
## Steps
### Step 0: Community Stage Assessment
Community has stages. Don't build Stage 3 infrastructure at Stage 1:
**Stage 1 — Seed (0-200 members):**
Every member is VIP. Founder in every conversation. Goal: find the 10 most engaged members. They become the nucleus.
**Stage 2 — Momentum (200-2,000 members):**View the complete source on GitHubbuzz-launch
When your agent uses it
Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,436 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytesSKILL.mdcore5,981 bytes
Read SKILL.md
# Launch Planning
You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
## Steps
### Step 0: Launch Scope
Clarify what is being launched:
- **Product launch** — new product, major version, public beta
- **Feature launch** — significant new capability
- **Milestone announcement** — funding, team, customer count, GitHub stars
- **Open source launch** — OSS release, new repoView the complete source on GitHubbuzz-pitch
When your agent uses it
Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,580 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Scripts executed separately
../../lib/copy-gate/gate.py
Files
../../lib/copy-gate/gate.pyruns19,447 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytesSKILL.mdcore6,598 bytes
Read SKILL.md
# Media Pitching
You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored.
## Steps
### Step 0: Identify Pitch Type
- **A) Journalist pitch** — outreach to specific journalist/reporter
- **B) Press release** — announcement for distribution
- **C) Podcast pitch** — outreach to podcast host
- **D) Newsletter pitch** — outreach to newsletter author for feature/mention
Ask if not clear.View the complete source on GitHubbuzz-recon
When your agent uses it
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,108 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,738 bytesSKILL.mdcore4,738 bytes
Read SKILL.md
# PR & Community Reconnaissance
You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Community Artifacts
```bash
# Community platform references
find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10
View the complete source on GitHubbuzz-social
When your agent uses it
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
What it loads into context
Frontmatter
131 tokensAlways available to the agent
SKILL.md
1,548 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytesSKILL.mdcore6,660 bytes
Read SKILL.md
# Social Media Content
You are Buzz — the PR & community engineer on the Product Team. Write social content that developers actually engage with.
## Steps
### Step 0: Clarify Platform and Goal
- Which platform? (HN / Twitter/X / LinkedIn / Reddit / GitHub / Bluesky)
- What's the goal? (Launch announcement / drive signups / build followers / thought leadership / community engagement)
- Who is writing this? (Founder / company account / individual dev)
Each platform has completely different norms. Mixing them is a credibility problem.
View the complete source on GitHubcrest-compete
When your agent uses it
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,669 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore7,769 bytes
Read SKILL.md
# Competitive Analysis
You are Crest — the product strategist on the Product Team. A competitive analysis is not a feature comparison spreadsheet. It ends with a call: where we play, how we win, and what we stop worrying about. One page. A decision the team can act on.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Frame the Decision
Before mapping any competitor, name what decision this analysis must inform. The scope of research follows from the decision.
```
Decision: [What are we trying to decide? e.g., "Should we move upmarket or go deeper with SMBs?"View the complete source on GitHubcrest-narrative
When your agent uses it
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,029 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,317 bytes
Read SKILL.md
# Strategic Narrative
You are Crest — the product strategist on the Product Team. Write the strategy memo that creates alignment across the team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Gather Strategic Inputs
Before writing, collect:
- **Planning horizon** — Q? Half? Year?
- **Current traction** — what is working? (from Lumen)View the complete source on GitHubcrest-okr
When your agent uses it
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
1,247 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,006 bytes
Read SKILL.md
# OKR Design
You are Crest — the product strategist on the Product Team. Design OKRs that drive decisions, not just reporting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Establish the Strategic Context
Before writing OKRs, confirm:
- **Planning horizon** — quarterly OKRs? Half-year? Annual?
- **Company stage** — 0→1 (find PMF), growth (scale what works), or efficiency (optimize unit economics)?View the complete source on GitHubcrest-recon
When your agent uses it
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
903 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,681 bytesSKILL.mdcore3,681 bytes
Read SKILL.md
# Strategic Reconnaissance
You are Crest — the product strategist on the Product Team. Map the strategic context before you plan or prioritize anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for strategic artifacts:
```bash
find . -name "*.md" | xargs grep -l "roadmap\|OKR\|strategy\|competitive\|vision\|north star\|RICE\|priorit" 2>/dev/null | head -20View the complete source on GitHubcrest-roadmap
When your agent uses it
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore6,198 bytes
Read SKILL.md
# Crest Roadmap
You are Crest — the product strategist on the Product Team. Produce a roadmap that sequences real bets against a real company-level problem. Not a backlog ranking exercise. Not a feature wish list. A prioritized, time-bounded plan with explicit tradeoffs that the team can execute and reassess.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Set the Strategic Anchor
Before touching any backlog item, name the company-level problem this roadmap is solving. One sentence. This is the anchor — every roadmap item either serves it or gets deprioritized.
```
Strategic anchor: [The company's primary challenge or opportunity right now — the one problemView the complete source on GitHubdeal-close
When your agent uses it
Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answer this objection".
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
1,832 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore8,207 bytes
Read SKILL.md
# Deal Closing
You are Deal — the revenue & sales engineer on the Product Team. Diagnose the stuck deal and produce the artifact to unstick it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Map the Deal
Gather the deal state before prescribing anything:
- What is the deal value (ACV)?
- Who is the economic buyer? Have we spoken with them directly?View the complete source on GitHubdeal-pipeline
When your agent uses it
Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
894 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,717 bytes
Read SKILL.md
# Pipeline Design
You are Deal — the revenue & sales engineer on the Product Team. Design a sales pipeline that matches the company's stage and motion.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Context
Ask for any missing context:
- What ARR stage is the company at? ($0-$1M, $1M-$10M, $10M+)
- What is the primary motion? (inbound, outbound, PLG/product-led, or mixed)View the complete source on GitHubdeal-playbook
When your agent uses it
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
1,197 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,912 bytes
Read SKILL.md
# Sales Playbook
You are Deal — the revenue & sales engineer on the Product Team. Write the specific playbook artifact requested.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Identify Playbook Type
Determine which playbook artifact is needed:
- **A) Outbound sequence** — Cold email or LinkedIn sequence to generate meetings
- **B) Discovery call guide** — Questions and flow for first sales conversationView the complete source on GitHubdeal-pricing
When your agent uses it
Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,202 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,064 bytes
Read SKILL.md
# Pricing Strategy
You are Deal — the revenue & sales engineer on the Product Team. Design pricing that matches product value, customer segment, and growth stage.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Pricing Context
Capture before designing anything:
- What is the primary value the product delivers? (time saved, risk reduced, revenue generated)
- Who is the buyer? (individual, team, enterprise)View the complete source on GitHubdeal-recon
When your agent uses it
Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,317 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,865 bytesSKILL.mdcore4,865 bytes
Read SKILL.md
# Revenue Reconnaissance
You are Deal — the revenue & sales engineer on the Product Team. Map the current revenue state before building any playbook or pipeline.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Revenue Artifacts
Scan for sales and revenue artifacts:
```bash
# CRM or deal trackingView the complete source on GitHubdeal-signals
When your agent uses it
Signal-based prospecting — read target companies' public websites for buying signals (ads running, incumbent agency, tech stack, hiring, stale content, missing booking) with evidence URLs, then build a cohort you can explain. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", "build a target list from these domains", or "what changed at these accounts".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,919 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
- Delivery
Files
SKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytesSKILL.mdcore8,239 bytes
Read SKILL.md
# Signal-Based Prospecting
You are Deal — the revenue & sales engineer on the Product Team. Turn a list of company domains into facts with proof behind them, and a target list where every account is on it for a stated reason.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
The work runs on `lib/site-signals/`: a free, stdlib-only profiler (a few plain HTTP requests per company, no browser, no model call, no API keys) and a cohort query over its log. Python does the collecting; you do the judgment.
## Steps
### Step 0: Gather Context and Locate the Profiler
Ask for anything missing:
View the complete source on GitHubdraft-flow
When your agent uses it
Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this".
What it loads into context
Frontmatter
151 tokensAlways available to the agent
SKILL.md
869 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytesSKILL.mdcore3,675 bytes
Read SKILL.md
# Draft Flow
You are Draft — the UX designer on the Product Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Understand the Job
Read the input — a product brief from Helm, a feature description, or a user task. Identify:
- **Primary task:** What is the user trying to accomplish?
- **Starting state:** Where is the user when this task begins? (logged out? empty state? mid-session?)View the complete source on GitHubdraft-ia
When your agent uses it
Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
2,006 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- When IA Work Is Actually Necessary
- Phase 1: Identify the Jobs
- Phase 2: Content Inventory
- Phase 3: Group by User Mental Model
- Phase 4: Sitemap
- Phase 5: Navigation Pattern Decision
- Phase 6: IA Issues
- Phase 7: Migration Path (if restructuring)
- "Done Enough to Build" Gate
- Anti-Patterns
- Delivery
Files
SKILL.mdcore9,386 bytes
Read SKILL.md
# Information Architecture
You are Draft — the UX designer on the Product Team. Structure information around what users are trying to do — not around how the product was built.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Default to executing. With a product description or existing nav, you have enough to produce a sitemap and nav recommendation. Ask only when permission/access logic or multi-tenant complexity would materially change the output.
---
## When IA Work Is Actually Necessary
IA is a tool, not a ritual. Before starting, make the call:
View the complete source on GitHubdraft-recon
When your agent uses it
UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wireframe work.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,009 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,780 bytesSKILL.mdcore3,780 bytes
Read SKILL.md
# UX Reconnaissance
You are Draft — the UX designer on the Product Team. Map the current UX before you redesign anything.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for frontend indicators:
```bash
# Routes / pagesView the complete source on GitHubdraft-review
When your agent uses it
Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,287 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,594 bytesSKILL.mdcore5,594 bytes
Read SKILL.md
# Usability Review
You are Draft — the UX designer on the Product Team. Evaluate the experience as a user, not as the team that built it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Run draft-recon first if you haven't already — understand the current screens before reviewing them.
### Step 1: Define the Review Scope
View the complete source on GitHubdraft-wireframe
When your agent uses it
Wireframe a screen — text/ASCII by default, or hand-drawn HTML when the user says "sketch", "hand-drawn", "lo-fi HTML", "whiteboard", "graph paper", or "visual wireframe". Text mode produces a buildable ASCII spec Form and Prism can act on. HTML mode produces a single self-contained file with graph-paper background, marker headlines, sticky-note annotations, and hatched chart placeholders — looks like a designer's whiteboard, commits to nothing.
What it loads into context
Frontmatter
191 tokensAlways available to the agent
SKILL.md
2,476 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Mode selection
- Phase 1: Extract What You Need
- Phase 2: Pattern Audit
- Phase 3: Content Hierarchy
- Phase 4: Wireframe
- Phase 5: Interaction Annotations
- Phase 6: Responsive Behavior
- Phase 7: "Done Enough to Build" Gate
- Anti-Patterns
- Delivery
- HTML Hand-Drawn Mode
Files
SKILL.mdcore12,409 bytes
Read SKILL.md
# Wireframe
You are Draft — the UX designer on the Product Team. Produce a buildable wireframe spec. Not a list of questions — a real artifact Form and Prism can act on.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Default to executing. You know the conventions. Ask only when you're blocked on a hard constraint that changes the output.
---
## Mode selection
**Choose mode from the request language:**
View the complete source on GitHubecho-feedback
When your agent uses it
Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,123 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,821 bytes
Read SKILL.md
# Feedback Synthesis
You are Echo — the user researcher on the Product Team. Turn raw feedback into decisions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Collect the Raw Feedback
Accept any of the following as input:
- Support ticket export (CSV, text dump, or summary)
- NPS survey verbatims (with scores)View the complete source on GitHubecho-interview
When your agent uses it
Run a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,914 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Mode A: Build the Interview Guide
- Mode B: Synthesize Interview Notes
- Delivery
Files
SKILL.mdcore9,320 bytes
Read SKILL.md
# Echo Interview
You are Echo — the user researcher on the Product Team. Produce two things: the interview guide before the conversation, and the synthesis after it. Not a list of questions — a conversation instrument. Not a report — a decision.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**Past behavior. Specific situations. No compliments, no hypotheticals.**
Every question must be answerable with a story from the user's past. If a question could be answered with "yes, probably" — rewrite it. Goal is not to validate a hypothesis; it is to hear what actually happened.
---
View the complete source on GitHubecho-jobs
When your agent uses it
Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,914 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Step 1: Accept the Input
- Step 2: Extract the Primary Job
- Step 3: Map the Switching Forces
- Step 4: Build the Job Map
- Step 5: Score and Rank
- Step 6: Deliver the JTBD Map
- Done When
- Delivery
Files
SKILL.mdcore8,882 bytes
Read SKILL.md
# Jobs-to-Be-Done Analysis
You are Echo — the user researcher on the Product Team. Find the job before you design the solution.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**A JTBD map is a decision instrument, not a consulting deliverable.**
Output: one primary job story, switching forces that explain why people act (or don't), and a ranked list of underserved jobs the product could own. No 10-level hierarchy. No opportunity matrix with 40 rows. Map exists to answer: _what job should we double down on, and what job are we failing to serve?_
---
View the complete source on GitHubecho-panel
When your agent uses it
Synthetic stakeholder panel — build a mixed panel of grounded personas, run independent and cross-reaction rounds against a launch, pricing change, PRD, or message, and return ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", "how will people react to this pricing change", or "pressure-test this message".
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
1,900 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Operating Principle
- Steps
- Key Rules
- Output Format
- Delivery
Files
SKILL.mdcore8,686 bytesSKILL.mdcore8,686 bytes
Read SKILL.md
# Echo Panel
You are Echo — the user researcher on the Product Team. Run a synthetic stakeholder panel: a small, deliberately mixed cast of personas reacts to a stimulus, reacts to each other, and is interviewed on the points that would change the decision. The output is a ranked list of hypotheses, never evidence.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Operating Principle
**A panel generates hypotheses cheaply. Real users confirm them.**
A synthetic panel is useful before a launch for one reason: it surfaces objections and misreadings you have not thought of, while they are still cheap to fix. It cannot tell you how many people will react a certain way, and it cannot replace talking to customers. Every artifact this skill produces says so.
## Steps
View the complete source on GitHubecho-recon
When your agent uses it
User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
962 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore3,919 bytesSKILL.mdcore3,919 bytes
Read SKILL.md
# Research Reconnaissance
You are Echo — the user researcher on the Product Team. Map what is already known about users before generating new research.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Detect Environment
Scan for research artifacts:
```bash
find . -name "*.md" | xargs grep -l "persona\|JTBD\|interview\|user research\|NPS\|churn\|feedback\|segment" 2>/dev/null | head -20View the complete source on GitHubecho-segment
When your agent uses it
User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
992 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,660 bytes
Read SKILL.md
# User Segmentation and Personas
You are Echo — the user researcher on the Product Team. Build personas from evidence, not assumptions.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Collect Raw Signals
Identify available data sources:
| Source | What to look for |
| ---------------------- | -------------------------------------------------------------------- |View the complete source on GitHubform-audit
When your agent uses it
Use when asked to audit UI for visual quality, check design consistency, review brand alignment, evaluate design system compliance, or find visual issues before a launch. Examples: "audit our UI", "check visual consistency", "review the design for issues", "is our UI on-brand", "find visual bugs", "design QA before launch".
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
2,704 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Scope
- Phase 2: Audit Framework
- Phase 3: Audit Execution
- Phase 4: Report
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,424 bytes
Read SKILL.md
# Form Audit
You are Form — the visual designer on the Product Team. A visual audit finds what's broken, inconsistent, or off-brand before users or stakeholders notice it.
This skill has 4 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Scope
Before auditing anything, you need to know what you're auditing against. An audit without a reference is opinion.
View the complete source on GitHubform-brand
When your agent uses it
Use when asked to create a brand identity, define visual design direction, generate a color palette or type system, build a style guide, or establish the look and feel for a product. Examples: "create a brand for X", "define the visual identity", "what colors should we use", "build a style guide", "design system foundations".
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
2,069 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Positioning Anchor
- Phase 2: Competitive Audit
- Phase 3: Brand Adjectives + Visual Language
- Design Intelligence (via uiux)
- Phase 4: Design Tokens + Brand Brief
- Delivery
Files
SKILL.mdcore8,618 bytesSKILL.mdcore8,618 bytes
Read SKILL.md
# Form Brand
You are Form — the visual designer on the Product Team.
Brand identity flows in one direction: strategy → visual. You do not touch color or type until you understand what makes this product different and who it's for. A beautiful identity on an unclear position is decoration. A simple identity on a clear position is a brand.
This skill has 4 phases. Move through them in order.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Positioning Anchor
View the complete source on GitHubform-component
When your agent uses it
Use when asked to design a UI component, specify a button, input, card, modal, badge, or any interactive element. Examples: "design a button component", "spec out the input field", "define the card component states", "create a component spec for Prism", "what should the dropdown look like".
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
3,795 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Verify Token Layer
- Phase 3: State Matrix
- Phase 4: Component Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore17,584 bytesSKILL.mdcore17,584 bytes
Read SKILL.md
# Form Component
You are Form — the visual designer on the Product Team. Your output here is the spec that Prism implements — be precise.
Component design is a multi-phase process. You do not write a single pixel value until you know which component, which context, and which token layer you are building against. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, establish what is being specified and where it lives. Ask these questions. Do not ask them all at once — lead with the most critical blockers and follow up.
View the complete source on GitHubform-deck
When your agent uses it
Use when asked to design a pitch deck, presentation, or slide set. Examples: "design a pitch deck", "create a sales deck", "make a conference presentation", "build an investor deck", "help me present this to the board", "create slides for X".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
2,792 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Narrative Structure
- Phase 4: Slide Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,535 bytes
Read SKILL.md
# Form Deck
You are Form — the visual designer on the Product Team.
Presentation design is a multi-phase process. You do not touch slide layout or visual treatment until the narrative arc is locked. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual or structural work, you need to understand the deck's purpose and constraints. Ask these questions. You do not need to ask all at once — lead with deck type and audience, follow up for the rest.
View the complete source on GitHubform-email
When your agent uses it
Use when asked to design an email template, newsletter, drip campaign email, transactional email, or any HTML email asset. Examples: "design a welcome email", "create a newsletter template", "make an onboarding email sequence", "design a password reset email", "build an email campaign".
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
3,285 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Technical Constraints
- Phase 4: Layout Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore15,313 bytes
Read SKILL.md
# Form Email
You are Form — the visual designer on the Product Team.
Email design is constrained design. The medium is hostile: fragmented rendering engines, aggressive image blocking, dark mode inversions, and no JavaScript. Good email design works beautifully in spite of all of that — not by ignoring it. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any layout work, you need to understand the purpose and context. Ask these questions. Lead with the most critical and follow up if needed.
View the complete source on GitHubform-logo
When your agent uses it
Use when asked to create a logo, design a brand mark, generate a logo concept, or produce any logo asset. Examples: "create a logo for X", "design a brand mark", "make me a logo", "generate logo concepts", "logo for our product".
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,292 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Brief Extraction
- Phase 2: Written Brief + Competitive Audit
- Phase 3: Concept Development
- Phase 4: Mockup + Ship Decision
- Reference: What Real Logos Teach
- Anti-Patterns
- Delivery
Files
SKILL.mdcore10,160 bytes
Read SKILL.md
# Form Logo
You are Form — the visual designer on the Product Team.
A logo is not decoration — it's the sharpest compression of what a brand is. One mark. Works at 16px. Works in monochrome. Carries meaning without explanation.
Logo design is a multi-phase process. You do not produce visual work until you understand the brand. This skill has 4 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Brief Extraction
View the complete source on GitHubform-mobile
When your agent uses it
Use when asked to design iOS or Android mobile app screens, create mobile UI, spec mobile flows, or produce screen designs for a native app. Examples: "design the onboarding screens", "spec the checkout flow for iOS", "design a home screen for Android", "create mobile UI for this feature".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
3,495 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Platform Conventions
- Phase 4: Screen Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore15,716 bytes
Read SKILL.md
# Form Mobile
You are Form — the visual designer on the Product Team.
Mobile screen design is a multi-phase process. You do not produce screen specs until you understand the platform, the user, and the flows. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the context. Ask these questions. Lead with the most critical ones and follow up if needed. You do not need to ask everything in one message.
View the complete source on GitHubform-social
When your agent uses it
Use when asked to design social media graphics, ad creatives, or marketing assets. Examples: "design a LinkedIn post for our launch", "create ad creatives for our campaign", "make an Instagram story", "design a Twitter card", "create a banner ad", "social assets for the product announcement".
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
2,985 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Brief
- Phase 3: Format Constraints
- Phase 4: Visual Spec
- Phase 5: Deliverable
- Key Rules
- Anti-Patterns
- Delivery
Files
SKILL.mdcore12,928 bytesSKILL.mdcore12,928 bytes
Read SKILL.md
# Form Social
You are Form — the visual designer on the Product Team.
Social media graphics fail for one reason: they try to say too much. One asset, one message, one action. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the platform, format, goal, and message. Ask these questions. Lead with the most critical ones.
View the complete source on GitHubform-tokens
When your agent uses it
Use when asked to define a design token system, create tokens, document tokens, set up CSS custom properties, build a Tailwind token config, establish a spacing scale, define color semantics, or bridge design decisions to code. Examples: "set up design tokens", "define our token system", "create CSS variables for the design system", "document our color tokens", "establish a spacing scale".
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
7,297 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Token Architecture
- Design Intelligence (via uiux)
- Phase 3: Token Categories
- Phase 4: Output Format
- Phase 5: Dark Mode
- Anti-Patterns
- Delivery Checklist
- Delivery
Files
SKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytesSKILL.mdcore29,030 bytes
Read SKILL.md
# Form Tokens
You are Form — the visual designer on the Product Team.
Design tokens are the contract between design and code. They are not a deliverable — they are infrastructure. Every color, spacing value, and type size in the product should reference a token. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before producing any tokens, you need to understand what already exists and what constraints apply. Ask these questions. Group them naturally — do not fire them as a list.
View the complete source on GitHubform-web
When your agent uses it
Use when asked to design a landing page, marketing website, or any web presence intended to convert or inform. Examples: "design a landing page for X", "create a marketing site", "we need a homepage", "design our website", "build a page for our launch".
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
2,937 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Phase 1: Discovery
- Phase 2: Written Brief
- Phase 3: Page Architecture
- Phase 4: Visual Spec
- Phase 5: Deliverable
- Anti-Patterns
- Delivery
Files
SKILL.mdcore13,158 bytes
Read SKILL.md
# Form Web
You are Form — the visual designer on the Product Team.
Web and landing page design is a multi-phase process. You do not produce layouts until you understand what the page must accomplish. This skill has 5 phases. Move through them in order. Do not skip phases.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
---
## Phase 1: Discovery
Before any visual work, you need to understand the page's job. Ask these questions. You do not need to ask all of them in one message — lead with the most critical ones and follow up. Group them naturally.
View the complete source on GitHubhelm-arbiter
When your agent uses it
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
What it loads into context
Frontmatter
151 tokensAlways available to the agent
SKILL.md
1,740 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Files
SKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytesSKILL.mdcore7,624 bytes
Read SKILL.md
# Scope Arbitration
You are Helm — the head of product on the Product Team. When product and engineering disagree on scope, you arbitrate.
## Steps
### Step 1: Establish the Disagreement
Clarify the exact nature of the scope dispute. Ask or identify:
- **The contested item** — what specific feature, behavior, or requirement is in dispute?
- **Product's position** — why does product want this in scope?
- **Engineering's position** — why does engineering want this out of scope (cost, complexity, risk, timeline)?
- **The original brief** — what did the Helm brief say? Is this item in or out?View the complete source on GitHubhelm-brief
When your agent uses it
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
1,234 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,292 bytes
Read SKILL.md
# Helm Brief
You are Helm — the Head of Product on the Product Team.
Produce a complete product brief in one pass. Infer what can be reasonably inferred, ask only for what materially changes scope, deliver a brief Apex can act on without a follow-up meeting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Read the Input
Accept what's given. Don't demand a perfectly framed problem before starting.
View the complete source on GitHubhelm-handoff
When your agent uses it
Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
974 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,284 bytes
Read SKILL.md
# Helm Handoff
You are Helm — the Head of Product on the Product Team.
Produce complete Helm→Apex handoff package and dispatch it. Apex reads this and knows what to build, why, and what success looks like — without a follow-up meeting.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 1: Validate the Brief
Check all required fields are present, filled, and internally consistent:
View the complete source on GitHubhelm-plan
When your agent uses it
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
1,892 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Key Rules
- Output Format
Files
SKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytes
Read SKILL.md
# Helm Plan
You are Helm — the Head of Product on the Product Team.
## Steps
### Step 0: Choose Depth
Before gathering input, present depth tiers so the user picks how much product-team involvement this needs — fast gut-check vs. full cross-functional rigor. Only show tiers that make sense for the request.
**Optional tier proposal.** The pick is a position on a 6-level ordered rubric, which is a `score` question. Run it as an assist that proposes; the user still chooses.
```bash
JEV="${CLAUDE_PLUGIN_ROOT:-.}/lib/jev/cli.js"View the complete source on GitHubhelm-recon
When your agent uses it
Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,018 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,264 bytesSKILL.mdcore4,264 bytes
Read SKILL.md
# Product Reconnaissance
You are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists.
## Steps
### Step 0: Detect Environment
Scan for product and research artifacts:
```bash
find . -name "*.md" | xargs grep -l "brief\|persona\|OKR\|roadmap\|strategy\|positioning" 2>/dev/null | head -20
ls docs/ research/ product/ briefs/ strategy/ 2>/dev/null
```View the complete source on GitHubink-calendar
When your agent uses it
Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,187 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,031 bytes
Read SKILL.md
# Content Calendar
You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.
## Steps
### Step 0: Gather Calendar Context
Before building:
- Who is creating content? (founder only / founder + contractor / content team)
- How much time per week for content? (1h / 4h / dedicated person)
- What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 posts/week, Stage 3: daily)
- What content types are in scope? (blog, tutorials, case studies, newsletter)View the complete source on GitHubink-case
When your agent uses it
Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,222 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,248 bytes
Read SKILL.md
# Case Study and Customer Story
You are Ink — the content marketing engineer on the Product Team. Write case studies that convert prospects — not testimonials that collect dust.
## Steps
### Step 0: Validate the Story
Before writing:
- **Customer approval confirmed?** (mandatory — never publish without written OK)
- **Metrics available?** ("they saw improvement" is useless — need numbers)
- **Is this the right customer profile for ICP?** (the story must resonate with who you want to sell to next)
- **Champion willing to be quoted?** (named quotes with role and company are 10x more powerful than anonymous)View the complete source on GitHubink-post
When your agent uses it
Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,121 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,493 bytes
Read SKILL.md
# Blog Post Writing
You are Ink — the content marketing engineer on the Product Team. Write publish-ready blog posts that serve a specific audience and rank for a specific keyword.
## Steps
### Step 0: Clarify the Brief
If not provided, ask:
- **Topic or keyword**: What should this post rank for?
- **Audience**: Who is reading this? (Job title, level, context)
- **Search intent**: Informational / commercial / comparison / tutorial?
- **Target length**: Short (600-900w), standard (1,000-1,500w), pillar (2,000-3,000w+)?View the complete source on GitHubink-recon
When your agent uses it
Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,115 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore4,743 bytesSKILL.mdcore4,743 bytes
Read SKILL.md
# Content Marketing Reconnaissance
You are Ink — the content marketing engineer on the Product Team. Map the current content state before building any strategy or calendar.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Find Existing Content
```bash
# Blog posts or content directory
find . -name "*.md" | xargs grep -l "title:\|date:\|author:\|tags:" 2>/dev/null | head -20
View the complete source on GitHubink-seo
When your agent uses it
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
2,804 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Evidence rules (apply to every step)
- Steps
- Rank-reporting conventions
- Output Format
- Delivery
Files
SKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytesSKILL.mdcore13,544 bytes
Read SKILL.md
# SEO Audit and Keyword Strategy
You are Ink — the content marketing engineer on the Product Team. Find the work that would most improve a site's useful organic traffic, then explain it so a non-expert can act on it. Research broadly; recommend selectively. A report with twenty findings has failed.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Evidence rules (apply to every step)
- **Never invent a metric.** Search volume, keyword difficulty, CPC, traffic, and positions come from a tool that returned them. If no tool returned a value, write `unknown`. A guessed number presented as data is the worst failure this skill can produce.
- **Label every number by source**: `[tool]` (an SEO data or Search Console tool returned it), `[verified]` (you checked it yourself this run), `[estimate]` (your stated assumption, with the assumption written next to it).
- **Observations are not causes.** Similar content with uneven rankings, a crawler warning, or missing provider rows never prove a penalty, an indexing exclusion, or why a page ranks where it does. Say what you saw; label any cause as a hypothesis.
- **Missing data is not a problem.** No backlink or ranking rows means "no recorded data", not "no backlinks".
- **Difficulty and volume are inputs, not goals.** A small query can matter to a high-value business; an easy one is not automatically worthwhile.
View the complete source on GitHubkeep-expand
When your agent uses it
Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".
What it loads into context
Frontmatter
119 tokensAlways available to the agent
SKILL.md
1,153 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,543 bytes
Read SKILL.md
# Expansion Revenue
You are Keep — the customer success engineer on the Product Team. Design the expansion motion that grows NRR above 120%.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Expansion Prerequisites Check
Expansion only works on healthy customers. Verify:
- [ ] Customer health score is Green (80+)
- [ ] Onboarding completion rate >80%View the complete source on GitHubkeep-health
When your agent uses it
Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,155 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Steps
- Delivery
Files
SKILL.mdcore5,011 bytes
Read SKILL.md
# Customer Health Scoring
You are Keep — the customer success engineer on the Product Team. Design a health scoring model that predicts churn and identifies expansion opportunities.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
### Step 0: Gather Instrumentation Context
Before designing the model, understand what data exists:
- What product usage events are tracked? (logins, feature usage, API calls, etc.)
- Is there NPS/CSAT data? How often collected?View the complete source on GitHubSkills included
- apex-plan
- apex-recon
- apex-review
- apex-status
- apex-takeover
- atlas-adr
- atlas-changelog
- atlas-map
- atlas-onboard
- atlas-present
- atlas-recon
- atlas-report
- cortex-eval
- cortex-integrate
- cortex-model
- cortex-prompt
- cortex-recon
- flux-health
- flux-migrate
- flux-pipeline
- flux-query
- flux-recon
- flux-schema
- forge-audit
- forge-cost
- forge-diagnose
- forge-infra
- forge-network
- forge-recon
- lens-audit
- lens-dashboard
- lens-metrics
- lens-recon
- lens-report
- pave-audit
- pave-catalog
- pave-env
- pave-golden
- pave-recon
- prism-audit
- prism-component
- prism-dashboard
- prism-recon
- prism-ui
- proof-api
- proof-audit
- proof-e2e
- proof-recon
- proof-strategy
- relay-audit
- relay-deploy
- relay-docker
- relay-pipeline
- relay-recon
- spine-api
- spine-design
- spine-perf
- spine-recon
- spine-review
- spine-service
- touch-app
- touch-audit
- touch-feature
- touch-recon
- touch-release
- vigil-alert
- vigil-check
- vigil-incident
- vigil-instrument
- vigil-recon
- volt-driver
- volt-firmware
- volt-ota
- volt-power
- volt-recon
- warden-audit
- warden-harden
- warden-iam
- warden-recon
- warden-threat
- apex-plan
- apex-recon
- apex-review
- apex-status
- apex-takeover
- atlas-adr
- atlas-changelog
- atlas-map
- atlas-onboard
- atlas-present
- atlas-recon
- atlas-report
- buzz-community
- buzz-launch
- buzz-pitch
- buzz-recon
- buzz-social
- cortex-eval
- cortex-integrate
- cortex-model
- cortex-prompt
- cortex-recon
- crest-compete
- crest-narrative
- crest-okr
- crest-recon
- crest-roadmap
- deal-close
- deal-pipeline
- deal-playbook
- deal-pricing
- deal-recon
- deal-signals
- draft-flow
- draft-ia
- draft-recon
- draft-review
- draft-wireframe
- echo-feedback
- echo-interview
- echo-jobs
- echo-panel
- echo-recon
- echo-segment
- flux-health
- flux-migrate
- flux-pipeline
- flux-query
- flux-recon
- flux-schema
- forge-audit
- forge-cost
- forge-diagnose
- forge-infra
- forge-network
- forge-recon
- form-audit
- form-brand
- form-component
- form-deck
- form-email
- form-logo
- form-mobile
- form-social
- form-tokens
- form-web
- helm-arbiter
- helm-brief
- helm-handoff
- helm-plan
- helm-recon
- ink-calendar
- ink-case
- ink-post
- ink-recon
- ink-seo
- keep-expand
- keep-health
- keep-onboard
- keep-playbook
- keep-recon
- lens-audit
- lens-dashboard
- lens-metrics
- lens-recon
- lens-report
- lumen-abtest
- lumen-funnel
- lumen-instrument
- lumen-metrics
- lumen-recon
- pave-audit
- pave-catalog
- pave-env
- pave-golden
- pave-recon
- pitch-copy
- pitch-launch
- pitch-message
- pitch-position
- pitch-recon
- prism-audit
- prism-component
- prism-dashboard
- prism-recon
- prism-ui
- proof-api
- proof-audit
- proof-e2e
- proof-recon
- proof-strategy
- relay-audit
- relay-deploy
- relay-docker
- relay-pipeline
- relay-recon
- spine-api
- spine-design
- spine-perf
- spine-recon
- spine-review
- spine-service
- surge-activation
- surge-experiment
- surge-plg
- surge-recon
- surge-retention
- touch-app
- touch-audit
- touch-feature
- touch-recon
- touch-release
- vigil-alert
- vigil-check
- vigil-incident
- vigil-instrument
- vigil-recon
- volt-driver
- volt-firmware
- volt-ota
- volt-power
- volt-recon
- warden-audit
- warden-harden
- warden-iam
- warden-recon
- warden-threat
- buzz-community
- buzz-devrel
- buzz-hn
- buzz-launch
- buzz-outreach
- buzz-pitch
- buzz-recon
- buzz-social
- ink-brief
- ink-calendar
- ink-case
- ink-cluster
- ink-distribute
- ink-links
- ink-local
- ink-post
- ink-recon
- ink-seo
- pitch-copy
- pitch-landing
- pitch-launch
- pitch-message
- pitch-position
- pitch-recon
- buzz-community
- buzz-launch
- buzz-pitch
- buzz-recon
- buzz-social
- crest-compete
- crest-narrative
- crest-okr
- crest-recon
- crest-roadmap
- deal-close
- deal-pipeline
- deal-playbook
- deal-pricing
- deal-recon
- deal-signals
- draft-flow
- draft-ia
- draft-recon
- draft-review
- draft-wireframe
- echo-feedback
- echo-interview
- echo-jobs
- echo-panel
- echo-recon
- echo-segment
- form-audit
- form-brand
- form-component
- form-deck
- form-email
- form-logo
- form-mobile
- form-social
- form-tokens
- form-web
- helm-arbiter
- helm-brief
- helm-handoff
- helm-plan
- helm-recon
- ink-calendar
- ink-case
- ink-post
- ink-recon
- ink-seo
- keep-expand
- keep-health
Showing 300 of 1,312 skills. See GitHub for the complete repository.
Repository facts
- License
- MIT
- Created
- Mar 16, 2026
- Last pushed
- Oct 14, 2026
- Forks
- 11
- Open issues
- 1
- Project activity
- Active
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 5, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 1,942 notes
.claude-plugin/marketplace.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedbundle/engineering-team/skills/apex-plan/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedbundle/engineering-team/skills/apex-plan/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedhooks/hooks.json:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/apex/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/apex/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/apex/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/atlas/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/atlas/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzedteam/atlas/scripts/setup.sh:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- 1,232 broad permissionsin 1,231 files: team/pave/skills/pave-contribute/SKILL.md:1 apex-plan/SKILL.md:1 apex-recon/SKILL.md:1 and 1,228 more
- 10 dangerous shell commandsin 4 files: team/pave/skills/pave-contribute/SKILL.md:119 pave-contribute/SKILL.md:119 pave-lsp/SKILL.md:91 and 1 more
- 1,093 network referencesin 209 files: .claude-plugin/marketplace.json:4 team/pave/skills/pave-contribute/SKILL.md:83 vigil-alert/SKILL.md:100 and 206 more
- No hidden or obfuscated text
- No instruction overrides
- 178 executable scriptsin 42 files: hooks/tonone-skill-gate.js:1 lib/compact/transcript-select.js:1 lib/copy-gate/gate.py:1 and 39 more
- 61 references to secretsin 39 files: hooks/tonone-skill-gate.js:621 lib/signals/project-shape.js:40 pave-golden/SKILL.md:91 and 36 more
- No requests to vote in Hot
Show all 2,574 signals by file
.claude-plugin/marketplace.json
- Network accessline 4
"owner": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 5
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 6
"url": "https://tonone.ai" - Network accessline 14
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 15
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 16
"url": "https://tonone.ai" - Network accessline 25
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 26
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 27
"url": "https://tonone.ai" - Network accessline 36
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 37
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 38
"url": "https://tonone.ai" - Network accessline 47
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 48
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 49
"url": "https://tonone.ai" - Network accessline 58
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 59
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 60
"url": "https://tonone.ai" - Network accessline 69
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 70
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 71
"url": "https://tonone.ai" - Network accessline 80
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 81
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 82
"url": "https://tonone.ai" - Network accessline 92
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 93
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 94
"url": "https://tonone.ai" - Network accessline 104
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 105
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 106
"url": "https://tonone.ai" - Network accessline 116
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 117
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 118
"url": "https://tonone.ai" - Network accessline 128
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 129
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 130
"url": "https://tonone.ai" - Network accessline 140
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 141
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 142
"url": "https://tonone.ai" - Network accessline 152
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 153
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 154
"url": "https://tonone.ai" - Network accessline 164
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 165
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 166
"url": "https://tonone.ai" - Network accessline 176
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 177
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 178
"url": "https://tonone.ai" - Network accessline 188
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 189
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 190
"url": "https://tonone.ai" - Network accessline 200
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 201
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 202
"url": "https://tonone.ai" - Network accessline 212
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 213
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 214
"url": "https://tonone.ai" - Network accessline 224
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 225
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 226
"url": "https://tonone.ai" - Network accessline 236
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 237
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 238
"url": "https://tonone.ai" - Network accessline 248
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 249
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 250
"url": "https://tonone.ai" - Network accessline 260
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 261
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 262
"url": "https://tonone.ai" - Network accessline 272
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 273
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 274
"url": "https://tonone.ai" - Network accessline 284
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 285
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 286
"url": "https://tonone.ai" - Network accessline 303
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 304
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 305
"url": "https://tonone.ai" - Network accessline 322
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 323
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 324
"url": "https://tonone.ai" - Network accessline 341
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 342
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 343
"url": "https://tonone.ai" - Network accessline 360
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 361
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 362
"url": "https://tonone.ai" - Network accessline 378
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 379
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 380
"url": "https://tonone.ai" - Network accessline 397
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 398
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 399
"url": "https://tonone.ai" - Network accessline 416
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 417
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 418
"url": "https://tonone.ai" - Network accessline 435
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 436
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 437
"url": "https://tonone.ai" - Network accessline 454
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 455
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 456
"url": "https://tonone.ai" - Network accessline 466
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 467
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 468
"url": "https://tonone.ai" - Network accessline 485
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 486
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 487
"url": "https://tonone.ai" - Network accessline 505
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 506
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 507
"url": "https://tonone.ai" - Network accessline 525
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 526
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 527
"url": "https://tonone.ai" - Network accessline 545
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 546
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 547
"url": "https://tonone.ai" - Network accessline 556
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 557
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 558
"url": "https://tonone.ai" - Network accessline 567
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 568
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 569
"url": "https://tonone.ai" - Network accessline 578
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 579
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 580
"url": "https://tonone.ai" - Network accessline 589
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 590
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 591
"url": "https://tonone.ai" - Network accessline 600
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 601
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 602
"url": "https://tonone.ai" - Network accessline 611
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 612
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 613
"url": "https://tonone.ai" - Network accessline 622
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 623
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 624
"url": "https://tonone.ai" - Network accessline 633
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 634
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 635
"url": "https://tonone.ai" - Network accessline 644
"author": { "name": "ai", "url": "https://tonone.ai" - Network accessline 645
"name": "ai", "url": "https://tonone.ai" }, - Network accessline 646
"url": "https://tonone.ai"
.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/ai-ops-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/data-science-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/design-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/devx-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/engineering-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/engineering-team/skills/apex-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/apex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/apex-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/apex-status/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/apex-takeover/SKILL.md
bundle/engineering-team/skills/atlas-adr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/atlas-changelog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/atlas-map/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/atlas-onboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/atlas-present/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/atlas-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/atlas-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 84
- Collapsible `<details><summary>` for verbose data sections - Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying - Mermaid JS CDN (`http - Network accessline 86
- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
bundle/engineering-team/skills/cortex-eval/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/cortex-integrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/cortex-model/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/cortex-prompt/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/cortex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/flux-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/flux-migrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/flux-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/flux-query/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/flux-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/flux-schema/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/forge-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/forge-cost/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/forge-diagnose/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/forge-infra/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/forge-network/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/forge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/lens-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/lens-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/lens-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/lens-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/lens-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/pave-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/pave-catalog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 51
owner: platform-team # team name, not individual oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api - Network accessline 52
oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api docs: https://notion.so/org/user-api-runbook - Network accessline 53
repo: https://github.com/org/user-api - Network accessline 54
docs: https://notion.so/org/user-api-runbook - Network accessline 55
dashboard: https://grafana.org/d/user-api
bundle/engineering-team/skills/pave-env/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/pave-golden/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 53
(or: cookiecutter gh:org/service-template) 2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 - Network accessline 54
2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 4. make test → test suite passes - Network accessline 55
3. make dev → app running at http://localhost:8000 - Access to secretsline 91
[Credential-related source omitted] - Network accessline 104
1. `make setup` 2. `make dev` → http://localhost:8000 - Network accessline 105
2. `make dev` → http://localhost:8000 - Access to secretsline 117
[Credential-related source omitted]
bundle/engineering-team/skills/pave-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/prism-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/prism-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 171
<svg className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" - Network accessline 172
className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" fill="none" - Network accessline 173
xmlns="http://www.w3.org/2000/svg"
bundle/engineering-team/skills/prism-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/prism-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/prism-ui/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/proof-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/proof-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/proof-e2e/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 90
reporter: [["html"], ["list"]], use: { baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 91
use: { baseURL: process.env.BASE_URL || "http://localhost:3000", trace: "on-first-retry", - Network accessline 92
baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 101
webServer: { command: "npm run dev", url: "http://localhost:3000", - Network accessline 102
command: "npm run dev", url: "http://localhost:3000", reuseExistingServer: !process.env.CI, - Network accessline 103
url: "http://localhost:3000", - Network accessline 257
- run: npx playwright test env: BASE_URL: http://localhost:3000 - Network accessline 258
env: BASE_URL: http://localhost:3000 TEST_EMAIL: ${{ secrets.TEST_EMAIL }} - Network accessline 259
BASE_URL: http://localhost:3000
bundle/engineering-team/skills/proof-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/proof-strategy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/relay-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/relay-deploy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 121
[Credential-related source omitted] - Network accessline 350
BASE_URL="${1:-https://your-service.example.com}" - Network accessline 355
# Health check STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 356
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 359
# Latency check LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 360
LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 364
# Version check (optional — requires /version or X-Version header) # VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 365
# VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 396
│ □ [any others] │ │ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ - Network accessline 397
│ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ └──────────────────────────────────────────────────────────────┘ - Network accessline 398
│ Smoke test: bash scripts/smoke-test.sh https://your-url │
bundle/engineering-team/skills/relay-docker/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/relay-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/relay-recon/SKILL.md
bundle/engineering-team/skills/spine-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 73
"message": "Human-readable explanation of what went wrong.", "param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 74
"param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" } - Network accessline 75
"doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 180
Then: full request/response spec for each endpoint, error codes, curl examples for each. End with what was explicitly ruled out and why (e.g., "GraphQL not used — access patterns are uniform and REST caching is needed").
bundle/engineering-team/skills/spine-design/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/spine-perf/SKILL.md
bundle/engineering-team/skills/spine-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/spine-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/spine-service/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/touch-app/SKILL.md
bundle/engineering-team/skills/touch-audit/SKILL.md
bundle/engineering-team/skills/touch-feature/SKILL.md
bundle/engineering-team/skills/touch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/touch-release/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/vigil-alert/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 100
summary: "{{ $labels.service }} burning SLO budget 14x fast" description: "Error rate is {{ $value | humanizePercentage }}. At this rate, the 30-day error budget is exhausted in ~2 hours." runbook: "https://docs.internal - Network accessline 102
runbook: "https://docs.internal/runbooks/[service-name]-high-burn-rate" - Network accessline 120
annotations: summary: "{{ $labels.service }} burning SLO budget 3x — budget will exhaust in ~10 days" runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 122
runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 134
annotations: summary: "{{ $labels.service }} P99 latency {{ $value | humanizeDuration }} exceeds SLO" runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 136
runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 148
message = <<-EOT SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 149
SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate @pagerduty-[service]-critical - Network accessline 150
Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 205
1. Check the error rate dashboard: [link] 2. Check recent deployments: `git log --oneline -10` or CI/CD dashboard link 3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz` - Network accessline 207
3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz`
bundle/engineering-team/skills/vigil-check/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/vigil-incident/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/vigil-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 96
[Credential-related source omitted] - Network accessline 270
# Grafana Cloud OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 271
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 274
# Datadog OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 275
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 278
# Honeycomb OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 279
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 282
# Self-hosted OTel Collector OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 - Network accessline 283
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
bundle/engineering-team/skills/vigil-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/volt-driver/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/volt-firmware/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/volt-ota/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/volt-power/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/volt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/warden-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/warden-harden/SKILL.md
bundle/engineering-team/skills/warden-iam/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/engineering-team/skills/warden-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/engineering-team/skills/warden-threat/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/full-team/lib/copy-gate/gate.py
bundle/full-team/skills/apex-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/apex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/apex-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/apex-status/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/apex-takeover/SKILL.md
bundle/full-team/skills/atlas-adr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/atlas-changelog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/atlas-map/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/atlas-onboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/atlas-present/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/atlas-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/atlas-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 84
- Collapsible `<details><summary>` for verbose data sections - Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying - Mermaid JS CDN (`http - Network accessline 86
- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
bundle/full-team/skills/buzz-community/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/buzz-launch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/buzz-pitch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/buzz-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/buzz-social/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/cortex-eval/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/cortex-integrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/cortex-model/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/cortex-prompt/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/cortex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/crest-compete/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/crest-narrative/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/crest-okr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/crest-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/crest-roadmap/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/deal-close/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/deal-pipeline/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/deal-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/deal-pricing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/deal-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/deal-signals/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/draft-flow/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/draft-ia/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/draft-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/draft-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/draft-wireframe/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/echo-feedback/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/echo-interview/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/echo-jobs/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/echo-panel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/echo-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/echo-segment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/flux-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/flux-migrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/flux-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/flux-query/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/flux-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/flux-schema/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/forge-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/forge-cost/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/forge-diagnose/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/forge-infra/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/forge-network/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/forge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/form-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/form-brand/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-deck/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-email/SKILL.md
bundle/full-team/skills/form-logo/SKILL.md
bundle/full-team/skills/form-mobile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-social/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-tokens/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/form-web/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/helm-arbiter/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/helm-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/helm-handoff/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/helm-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/helm-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/ink-calendar/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/ink-case/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/ink-post/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/ink-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/ink-seo/SKILL.md
bundle/full-team/skills/keep-expand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/keep-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/keep-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
bundle/full-team/skills/keep-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/full-team/skills/keep-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/lens-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/lens-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lens-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lens-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/lens-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lumen-abtest/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lumen-funnel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lumen-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lumen-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/lumen-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/pave-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/pave-catalog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 51
owner: platform-team # team name, not individual oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api - Network accessline 52
oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api docs: https://notion.so/org/user-api-runbook - Network accessline 53
repo: https://github.com/org/user-api - Network accessline 54
docs: https://notion.so/org/user-api-runbook - Network accessline 55
dashboard: https://grafana.org/d/user-api
bundle/full-team/skills/pave-env/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/pave-golden/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 53
(or: cookiecutter gh:org/service-template) 2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 - Network accessline 54
2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 4. make test → test suite passes - Network accessline 55
3. make dev → app running at http://localhost:8000 - Access to secretsline 91
[Credential-related source omitted] - Network accessline 104
1. `make setup` 2. `make dev` → http://localhost:8000 - Network accessline 105
2. `make dev` → http://localhost:8000 - Access to secretsline 117
[Credential-related source omitted]
bundle/full-team/skills/pave-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/pitch-copy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/pitch-launch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/pitch-message/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/pitch-position/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/pitch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/prism-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/prism-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 171
<svg className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" - Network accessline 172
className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" fill="none" - Network accessline 173
xmlns="http://www.w3.org/2000/svg"
bundle/full-team/skills/prism-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/prism-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/prism-ui/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/proof-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/proof-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/proof-e2e/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 90
reporter: [["html"], ["list"]], use: { baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 91
use: { baseURL: process.env.BASE_URL || "http://localhost:3000", trace: "on-first-retry", - Network accessline 92
baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 101
webServer: { command: "npm run dev", url: "http://localhost:3000", - Network accessline 102
command: "npm run dev", url: "http://localhost:3000", reuseExistingServer: !process.env.CI, - Network accessline 103
url: "http://localhost:3000", - Network accessline 257
- run: npx playwright test env: BASE_URL: http://localhost:3000 - Network accessline 258
env: BASE_URL: http://localhost:3000 TEST_EMAIL: ${{ secrets.TEST_EMAIL }} - Network accessline 259
BASE_URL: http://localhost:3000
bundle/full-team/skills/proof-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/proof-strategy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/relay-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/relay-deploy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 121
[Credential-related source omitted] - Network accessline 350
BASE_URL="${1:-https://your-service.example.com}" - Network accessline 355
# Health check STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 356
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 359
# Latency check LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 360
LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 364
# Version check (optional — requires /version or X-Version header) # VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 365
# VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 396
│ □ [any others] │ │ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ - Network accessline 397
│ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ └──────────────────────────────────────────────────────────────┘ - Network accessline 398
│ Smoke test: bash scripts/smoke-test.sh https://your-url │
bundle/full-team/skills/relay-docker/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/relay-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/relay-recon/SKILL.md
bundle/full-team/skills/spine-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 73
"message": "Human-readable explanation of what went wrong.", "param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 74
"param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" } - Network accessline 75
"doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 180
Then: full request/response spec for each endpoint, error codes, curl examples for each. End with what was explicitly ruled out and why (e.g., "GraphQL not used — access patterns are uniform and REST caching is needed").
bundle/full-team/skills/spine-design/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/spine-perf/SKILL.md
bundle/full-team/skills/spine-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/spine-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/spine-service/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/surge-activation/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/surge-experiment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/surge-plg/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/surge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/surge-retention/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/touch-app/SKILL.md
bundle/full-team/skills/touch-audit/SKILL.md
bundle/full-team/skills/touch-feature/SKILL.md
bundle/full-team/skills/touch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/touch-release/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/vigil-alert/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 100
summary: "{{ $labels.service }} burning SLO budget 14x fast" description: "Error rate is {{ $value | humanizePercentage }}. At this rate, the 30-day error budget is exhausted in ~2 hours." runbook: "https://docs.internal - Network accessline 102
runbook: "https://docs.internal/runbooks/[service-name]-high-burn-rate" - Network accessline 120
annotations: summary: "{{ $labels.service }} burning SLO budget 3x — budget will exhaust in ~10 days" runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 122
runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 134
annotations: summary: "{{ $labels.service }} P99 latency {{ $value | humanizeDuration }} exceeds SLO" runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 136
runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 148
message = <<-EOT SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 149
SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate @pagerduty-[service]-critical - Network accessline 150
Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 205
1. Check the error rate dashboard: [link] 2. Check recent deployments: `git log --oneline -10` or CI/CD dashboard link 3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz` - Network accessline 207
3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz`
bundle/full-team/skills/vigil-check/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/vigil-incident/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/vigil-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 96
[Credential-related source omitted] - Network accessline 270
# Grafana Cloud OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 271
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 274
# Datadog OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 275
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 278
# Honeycomb OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 279
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 282
# Self-hosted OTel Collector OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 - Network accessline 283
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
bundle/full-team/skills/vigil-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/volt-driver/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/volt-firmware/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/volt-ota/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/volt-power/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/volt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/warden-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/warden-harden/SKILL.md
bundle/full-team/skills/warden-iam/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/full-team/skills/warden-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/full-team/skills/warden-threat/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/infra-specialist-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/legal-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/marketing-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/marketing-team/lib/copy-gate/gate.py
bundle/marketing-team/skills/buzz-community/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/buzz-devrel/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/buzz-hn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/buzz-launch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/buzz-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/buzz-pitch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/buzz-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/buzz-social/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/ink-brief/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/ink-calendar/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/ink-case/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/ink-cluster/SKILL.md
bundle/marketing-team/skills/ink-distribute/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/marketing-team/skills/ink-links/SKILL.md
bundle/marketing-team/skills/ink-local/SKILL.md
bundle/marketing-team/skills/ink-post/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/ink-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/marketing-team/skills/ink-seo/SKILL.md
bundle/marketing-team/skills/pitch-copy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/marketing-team/skills/pitch-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
bundle/marketing-team/skills/pitch-launch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/marketing-team/skills/pitch-message/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/marketing-team/skills/pitch-position/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/marketing-team/skills/pitch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/operations-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/product-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/product-team/lib/copy-gate/gate.py
bundle/product-team/skills/buzz-community/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/buzz-launch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/buzz-pitch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/buzz-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/buzz-social/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/crest-compete/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/crest-narrative/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/crest-okr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/crest-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/crest-roadmap/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/deal-close/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/deal-pipeline/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/deal-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/deal-pricing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/deal-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/deal-signals/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/draft-flow/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/draft-ia/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/draft-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/draft-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/draft-wireframe/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/echo-feedback/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/echo-interview/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/echo-jobs/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/echo-panel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/echo-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/echo-segment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/form-brand/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-deck/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-email/SKILL.md
bundle/product-team/skills/form-logo/SKILL.md
bundle/product-team/skills/form-mobile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-social/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-tokens/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/form-web/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/helm-arbiter/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/helm-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/helm-handoff/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/helm-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/helm-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/ink-calendar/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/ink-case/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/ink-post/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/ink-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/ink-seo/SKILL.md
bundle/product-team/skills/keep-expand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/keep-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/keep-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
bundle/product-team/skills/keep-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/product-team/skills/keep-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/lumen-abtest/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/lumen-funnel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/lumen-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/lumen-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/lumen-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/pitch-copy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/pitch-launch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/pitch-message/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/pitch-position/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/pitch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/surge-activation/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/surge-experiment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/surge-plg/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/product-team/skills/surge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/product-team/skills/surge-retention/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/revenue-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/revenue-team/lib/copy-gate/gate.py
- Executable scriptline 1
#!/usr/bin/env python3
bundle/revenue-team/skills/deal-close/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/deal-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/deal-pipeline/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/deal-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/revenue-team/skills/deal-pricing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/revenue-team/skills/deal-proposal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/deal-qualify/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/deal-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/revenue-team/skills/deal-signals/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-churn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-expand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
bundle/revenue-team/skills/keep-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-qbr/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/keep-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/revenue-team/skills/keep-segment/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
bundle/revenue-team/skills/surge-activation/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/revenue-team/skills/surge-experiment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/revenue-team/skills/surge-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
bundle/revenue-team/skills/surge-plg/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/revenue-team/skills/surge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
bundle/revenue-team/skills/surge-retention/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
bundle/secops-team/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
bundle/tonone-core/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "homepage": "https://github.com/tonone-ai/tonone", "repository": "https://github.com/tonone-ai/tonone", - Network accessline 9
"homepage": "https://github.com/tonone-ai/tonone", - Network accessline 10
"repository": "https://github.com/tonone-ai/tonone",
bundle/tonone-core/skills/apex-takeover/SKILL.md
- Access to secretsline 25
[Credential-related source omitted]
bundle/tonone-core/skills/atlas-report/SKILL.md
- Network accessline 83
- Collapsible `<details><summary>` for verbose data sections - Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying - Mermaid JS CDN (`http - Network accessline 85
- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
bundle/tonone-core/skills/pave-catalog/SKILL.md
- Network accessline 50
owner: platform-team # team name, not individual oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api - Network accessline 51
oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api docs: https://notion.so/org/user-api-runbook - Network accessline 52
repo: https://github.com/org/user-api - Network accessline 53
docs: https://notion.so/org/user-api-runbook - Network accessline 54
dashboard: https://grafana.org/d/user-api
bundle/tonone-core/skills/pave-golden/SKILL.md
- Network accessline 52
(or: cookiecutter gh:org/service-template) 2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 - Network accessline 53
2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 4. make test → test suite passes - Network accessline 54
3. make dev → app running at http://localhost:8000 - Access to secretsline 90
[Credential-related source omitted] - Network accessline 103
1. `make setup` 2. `make dev` → http://localhost:8000 - Network accessline 104
2. `make dev` → http://localhost:8000 - Access to secretsline 116
[Credential-related source omitted]
bundle/tonone-core/skills/prism-component/SKILL.md
bundle/tonone-core/skills/proof-e2e/SKILL.md
- Network accessline 89
reporter: [["html"], ["list"]], use: { baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 90
use: { baseURL: process.env.BASE_URL || "http://localhost:3000", trace: "on-first-retry", - Network accessline 91
baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 100
webServer: { command: "npm run dev", url: "http://localhost:3000", - Network accessline 101
command: "npm run dev", url: "http://localhost:3000", reuseExistingServer: !process.env.CI, - Network accessline 102
url: "http://localhost:3000", - Network accessline 256
- run: npx playwright test env: BASE_URL: http://localhost:3000 - Network accessline 257
env: BASE_URL: http://localhost:3000 TEST_EMAIL: ${{ secrets.TEST_EMAIL }} - Network accessline 258
BASE_URL: http://localhost:3000
bundle/tonone-core/skills/relay-deploy/SKILL.md
- Access to secretsline 120
[Credential-related source omitted] - Network accessline 349
BASE_URL="${1:-https://your-service.example.com}" - Network accessline 354
# Health check STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 355
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 358
# Latency check LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 359
LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 363
# Version check (optional — requires /version or X-Version header) # VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 364
# VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 395
│ □ [any others] │ │ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ - Network accessline 396
│ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ └──────────────────────────────────────────────────────────────┘ - Network accessline 397
│ Smoke test: bash scripts/smoke-test.sh https://your-url │
bundle/tonone-core/skills/relay-recon/SKILL.md
- Access to secretsline 96
[Credential-related source omitted]
bundle/tonone-core/skills/spine-api/SKILL.md
- Network accessline 72
"message": "Human-readable explanation of what went wrong.", "param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 73
"param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" } - Network accessline 74
"doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 179
Then: full request/response spec for each endpoint, error codes, curl examples for each. End with what was explicitly ruled out and why (e.g., "GraphQL not used — access patterns are uniform and REST caching is needed").
bundle/tonone-core/skills/spine-perf/SKILL.md
- Network accessline 22
python team/spine/scripts/spine_agent/perf_scan.py [target] [--base-url http://...] [--paths /api/orders /api/users] [--skip-n1] [--skip-endpoints]
bundle/tonone-core/skills/touch-app/SKILL.md
bundle/tonone-core/skills/touch-audit/SKILL.md
- Network accessline 125
- **URL scheme registered?** — custom scheme (myapp://) and universal links (https://...)
bundle/tonone-core/skills/touch-feature/SKILL.md
- Access to secretsline 137
[Credential-related source omitted]
bundle/tonone-core/skills/vigil-alert/SKILL.md
- Network accessline 99
summary: "{{ $labels.service }} burning SLO budget 14x fast" description: "Error rate is {{ $value | humanizePercentage }}. At this rate, the 30-day error budget is exhausted in ~2 hours." runbook: "https://docs.internal - Network accessline 101
runbook: "https://docs.internal/runbooks/[service-name]-high-burn-rate" - Network accessline 119
annotations: summary: "{{ $labels.service }} burning SLO budget 3x — budget will exhaust in ~10 days" runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 121
runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 133
annotations: summary: "{{ $labels.service }} P99 latency {{ $value | humanizeDuration }} exceeds SLO" runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 135
runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 147
message = <<-EOT SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 148
SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate @pagerduty-[service]-critical - Network accessline 149
Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 204
1. Check the error rate dashboard: [link] 2. Check recent deployments: `git log --oneline -10` or CI/CD dashboard link 3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz` - Network accessline 206
3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz`
bundle/tonone-core/skills/vigil-instrument/SKILL.md
- Access to secretsline 95
[Credential-related source omitted] - Network accessline 269
# Grafana Cloud OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 270
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 273
# Datadog OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 274
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 277
# Honeycomb OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 278
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 281
# Self-hosted OTel Collector OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 - Network accessline 282
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
bundle/tonone-core/skills/warden-harden/SKILL.md
- Network accessline 166
Access-Control-Allow-Origin: https://yourdomain.com (exact origin, not *)
hooks/tonone-skill-gate.js
- Executable scriptline 1
#!/usr/bin/env node - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
#!/usr/bin/env node - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Access to secretsline 621
[Credential-related source omitted] - Access to secretsline 621
[Credential-related source omitted] - Access to secretsline 622
[Credential-related source omitted] - Access to secretsline 622
[Credential-related source omitted] - Access to secretsline 637
[Credential-related source omitted] - Access to secretsline 637
[Credential-related source omitted] - Access to secretsline 638
[Credential-related source omitted] - Access to secretsline 638
[Credential-related source omitted] - Access to secretsline 639
[Credential-related source omitted] - Access to secretsline 639
[Credential-related source omitted]
lib/compact/transcript-select.js
- Executable scriptline 1
Executable file - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable - Executable scriptline 1
Executable file; content unavailable
lib/copy-gate/gate.py
lib/jev/cli.js
lib/signals/project-shape.js
- Executable scriptline 1
Executable file - Executable scriptline 1
Executable file - Access to secretsline 40
[Credential-related source omitted] - Access to secretsline 40
[Credential-related source omitted] - Access to secretsline 620
[Credential-related source omitted] - Access to secretsline 620
[Credential-related source omitted]
scripts/gen-agent-index.py
skills/apex-diagnose/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep
skills/apex-gate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/apex-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/apex-profile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
skills/apex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/apex-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/apex-route/SKILL.md
skills/apex-stats/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob
skills/apex-status/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/apex-takeover/SKILL.md
skills/apex/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-adr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-changelog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-map/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-onboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-present/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/atlas-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/atlas-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 84
- Collapsible `<details><summary>` for verbose data sections - Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying - Mermaid JS CDN (`http - Network accessline 86
- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
skills/atlas/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/audit-controls/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/audit-legal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/audit-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/axe-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/axe-fix/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/axe-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bench-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bench-profile/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bench-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bind-gap/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bind-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/bind-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/blue-detect/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/blue-harden/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/blue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/brace-escalate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-kb/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-metrics/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-sla/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brace-triage/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/brief-draft/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/brief-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/brief-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/budget-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/budget-optimize/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/budget-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/buzz-community/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/buzz-devrel/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/buzz-hn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/buzz-launch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/buzz-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/buzz-pitch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/buzz-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/buzz-social/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/buzz/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cache-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cache-evict/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cache-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cast-forecast/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cast-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cast-validate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chain-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chain-sbom/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chain-scan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/change-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/change-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/change-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chaos-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chaos-game/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/chaos-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cite-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cite-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cite-research/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clause-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clause-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clause-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clean-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clean-transform/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/clean-validate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/compat-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/compat-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/compat-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/copy-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/copy-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/copy-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cortex-eval/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cortex-integrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cortex-model/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cortex-prompt/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cortex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/cortex/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/crest-compete/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/crest-narrative/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/crest-okr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/crest-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/crest-roadmap/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/crest/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/cut-icon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cut-illustrate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/cut-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/deal-close/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/deal-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/deal-pipeline/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/deal-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/deal-pricing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/deal-proposal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/deal-qualify/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/deal-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/deal-signals/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep, AskUserQuestion
skills/deal/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/deploy-canary/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/deploy-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/deploy-serve/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/draft-flow/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/draft-ia/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/draft-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/draft-patterns/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/draft-proto/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 98
<script src="https://unpkg.com/react@18/umd/react.development.js"></script> - Network accessline 99
<script src="https://unpkg.com/react-dom@18/umd/react-dom.development.js"></script> - Network accessline 100
<script src="https://unpkg.com/@babel/standalone/babel.min.js"></script>
skills/draft-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/draft-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/draft-wireframe/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/draft/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/drift-alert/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/drift-monitor/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/drift-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/echo-feedback/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/echo-interview/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/echo-jobs/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/echo-panel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/echo-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/echo-segment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/echo/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/edge-cdn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/edge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/edge-route/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/embed-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/embed-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/embed-search/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/eval-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/eval-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/eval-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/evals-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/evals-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/evals-harness/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/evals-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/evals-regress/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/feat-engineer/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/feat-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/feat-store/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/finop-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/finop-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/finop-reserve/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/fit-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/fit-train/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/fit-tune/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/flux-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/flux-migrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/flux-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/flux-query/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/flux-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/flux-schema/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/flux/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/folk-comp/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/folk-culture/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-hire/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-migrate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-org/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-perf/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/folk-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/forge-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/forge-cost/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/forge-diagnose/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/forge-infra/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/forge-network/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/forge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/forge/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-animate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/form-brand/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-critique/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-deck/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-direction/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-email/SKILL.md
skills/form-exam/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/form-logo/SKILL.md
skills/form-mobile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-palette/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/form-social/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-style/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/form-tokens/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form-web/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/form/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/frame-board/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/frame-equity/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/frame-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/gate-ci/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/gate-lint/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/gate-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/glyph-pair/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/glyph-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/glyph-scale/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/grid-layout/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/grid-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/grid-responsive/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guard-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guard-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guard-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guide-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guide-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/guide-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/helm-arbiter/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/helm-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/helm-handoff/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/helm-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/helm-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/helm/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/hue-palette/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/hue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/hue-token/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/hunt-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/hunt-ioc/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/hunt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/ink-brief/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/ink-calendar/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/ink-case/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/ink-cluster/SKILL.md
skills/ink-distribute/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/ink-links/SKILL.md
skills/ink-local/SKILL.md
skills/ink-post/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/ink-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/ink-seo/SKILL.md
skills/ink/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/keel-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keel-cadence/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keel-comply/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/keel-legal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keel-okr/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keel-process/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keel-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/keel-vendor/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/keep-churn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep-expand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
skills/keep-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep-qbr/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/keep-segment/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/keep/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/kube-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/kube-rbac/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/kube-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/lens-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/lens-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/lens-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lens-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lens-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/lens-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lens/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lodge-dmca/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/lodge-filing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/lodge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/lumen-abtest/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lumen-funnel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lumen-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lumen-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/lumen-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/lumen/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/mark-asset/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mark-brand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mark-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mesh-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mesh-observe/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mesh-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mint-board/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-budget/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-model/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-raise/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/mint-report/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-runway/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mint-unit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
skills/mock-contract/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mock-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/mock-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/move-animate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/move-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/move-system/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/multi-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/multi-port/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/multi-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/onboard-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/onboard-quickstart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/onboard-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/patch-plan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/patch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/patch-triage/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/pave-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/pave-catalog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 51
owner: platform-team # team name, not individual oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api - Network accessline 52
oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api docs: https://notion.so/org/user-api-runbook - Network accessline 53
repo: https://github.com/org/user-api - Network accessline 54
docs: https://notion.so/org/user-api-runbook - Network accessline 55
dashboard: https://grafana.org/d/user-api
skills/pave-contribute/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, AskUserQuestion - Network accessline 83
TONONE_TMP=$(mktemp -d) git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 84
git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 87
gh repo fork --remote-name=fork --clone=false 2>/dev/null || true GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 88
GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Network accessline 89
git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 90
git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Dangerous shell operationline 119
rm -rf "$TONONE_TMP" - Dangerous shell operationline 140
- Push fails → print error, `rm -rf "$TONONE_TMP"`, exit.
skills/pave-env/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/pave-golden/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 53
(or: cookiecutter gh:org/service-template) 2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 - Network accessline 54
2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 4. make test → test suite passes - Network accessline 55
3. make dev → app running at http://localhost:8000 - Access to secretsline 91
[Credential-related source omitted] - Network accessline 104
1. `make setup` 2. `make dev` → http://localhost:8000 - Network accessline 105
2. `make dev` → http://localhost:8000 - Access to secretsline 117
[Credential-related source omitted]
skills/pave-lsp/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Dangerous shell operationline 91
| `clangd` | `brew install llvm` / `sudo apt install clangd` | - Dangerous shell operationline 118
Unlike the LSP plugins, this one is not a thin wrapper over a binary you install first. It ships its own `.mcp.json`, which starts the server with `uvx --from git+https://github.com/oraios/serena serena start-mcp-server`. The only prerequis - Network accessline 118
Unlike the LSP plugins, this one is not a thin wrapper over a binary you install first. It ships its own `.mcp.json`, which starts the server with `uvx --from git+https://github.com/oraios/serena serena start-mcp-server`. The only prerequis
skills/pave-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/pave/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/phish-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/phish-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/phish-train/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/pitch-copy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/pitch-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/pitch-launch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/pitch-message/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/pitch-position/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/pitch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/pitch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/plot-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/plot-eda/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/plot-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/port-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/port-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/port-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/prism-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/prism-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/prism-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 171
<svg className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" - Network accessline 172
className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" fill="none" - Network accessline 173
xmlns="http://www.w3.org/2000/svg"
skills/prism-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/prism-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/prism-stack/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/prism-ui/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/prism/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/prompt-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/prompt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/prompt-version/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/proof-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/proof-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/proof-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/proof-e2e/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 90
reporter: [["html"], ["list"]], use: { baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 91
use: { baseURL: process.env.BASE_URL || "http://localhost:3000", trace: "on-first-retry", - Network accessline 92
baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 101
webServer: { command: "npm run dev", url: "http://localhost:3000", - Network accessline 102
command: "npm run dev", url: "http://localhost:3000", reuseExistingServer: !process.env.CI, - Network accessline 103
url: "http://localhost:3000", - Network accessline 257
- run: npx playwright test env: BASE_URL: http://localhost:3000 - Network accessline 258
env: BASE_URL: http://localhost:3000 TEST_EMAIL: ${{ secrets.TEST_EMAIL }} - Network accessline 259
BASE_URL: http://localhost:3000
skills/proof-explore/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 76
python3 lib/jev-ultrafast/cli.py explore \ --url http://localhost:3000/signup \ - Network accessline 77
--url http://localhost:3000/signup \ - Network accessline 109
┌─ Flow Exploration ───────────────────────────────────────┐ │ Driver jev-ultrafast | /browse | source-only │ │ Target http://localhost:3000 │ - Network accessline 110
│ Driver jev-ultrafast | /browse | source-only │ │ Target http://localhost:3000 │ │ Flows N run, M reached their final goal │ - Network accessline 111
│ Target http://localhost:3000 │
skills/proof-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/proof-strategy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/proof/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/queue-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/queue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/queue-scale/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/rank-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/rank-eval/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/rank-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/red-pentest/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/red-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/red-report/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/relay-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/relay-deploy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 121
[Credential-related source omitted] - Network accessline 350
BASE_URL="${1:-https://your-service.example.com}" - Network accessline 355
# Health check STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 356
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 359
# Latency check LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 360
LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 364
# Version check (optional — requires /version or X-Version header) # VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 365
# VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 396
│ □ [any others] │ │ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ - Network accessline 397
│ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ └──────────────────────────────────────────────────────────────┘ - Network accessline 398
│ Smoke test: bash scripts/smoke-test.sh https://your-url │
skills/relay-docker/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/relay-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/relay-recon/SKILL.md
skills/relay-ship/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 214
🤖 **This PR was prepared by [Tonone](https://tonone.ai) AI agents** — an autonomous engineering team of 23 specialized agents that plan, build, review, and ship software end-to-end.
skills/relay/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/resp-contain/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/resp-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/resp-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sample-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sample-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sample-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sast-fix/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sast-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/sast-scan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/schema-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/schema-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/schema-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/scope-oss/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/scope-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/scope-trademark/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/score-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/score-eval/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/score-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/serv-cold/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/serv-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/serv-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/shield-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/shield-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/shield-respond/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/siem-alert/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/siem-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/siem-rule/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/spine-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 73
"message": "Human-readable explanation of what went wrong.", "param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 74
"param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" } - Network accessline 75
"doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 180
Then: full request/response spec for each endpoint, error codes, curl examples for each. End with what was explicitly ruled out and why (e.g., "GraphQL not used — access patterns are uniform and REST caching is needed").
skills/spine-design/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/spine-perf/SKILL.md
skills/spine-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/spine-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/spine-service/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/spine-simplify/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/spine/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/surge-activation/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/surge-experiment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/surge-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/surge-plg/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/surge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/surge-retention/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/surge/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/terms-privacy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/terms-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/terms-tos/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/terra-drift/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/terra-module/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/terra-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/token-budget/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/token-chunk/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/token-compact/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write
skills/token-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tone-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tone-theme/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tone-token/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tonone-onboard/SKILL.md
- Broad permissionsline 1
Bash, Read, AskUserQuestion
skills/touch-app/SKILL.md
skills/touch-audit/SKILL.md
skills/touch-feature/SKILL.md
skills/touch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/touch-release/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/touch-ui/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
skills/touch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/trace-debug/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/trace-instrument/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/trace-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tune-finetune/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tune-prompt/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/tune-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/vect-embed/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/vect-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/vect-search/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/vigil-alert/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 100
summary: "{{ $labels.service }} burning SLO budget 14x fast" description: "Error rate is {{ $value | humanizePercentage }}. At this rate, the 30-day error budget is exhausted in ~2 hours." runbook: "https://docs.internal - Network accessline 102
runbook: "https://docs.internal/runbooks/[service-name]-high-burn-rate" - Network accessline 120
annotations: summary: "{{ $labels.service }} burning SLO budget 3x — budget will exhaust in ~10 days" runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 122
runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 134
annotations: summary: "{{ $labels.service }} P99 latency {{ $value | humanizeDuration }} exceeds SLO" runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 136
runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 148
message = <<-EOT SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 149
SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate @pagerduty-[service]-critical - Network accessline 150
Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 205
1. Check the error rate dashboard: [link] 2. Check recent deployments: `git log --oneline -10` or CI/CD dashboard link 3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz` - Network accessline 207
3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz`
skills/vigil-check/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/vigil-incident/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/vigil-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 96
[Credential-related source omitted] - Network accessline 270
# Grafana Cloud OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 271
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 274
# Datadog OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 275
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 278
# Honeycomb OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 279
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 282
# Self-hosted OTel Collector OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 - Network accessline 283
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
skills/vigil-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/vigil/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/volt-driver/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/volt-firmware/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/volt-ota/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/volt-power/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/volt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/volt/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/warden-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/warden-harden/SKILL.md
skills/warden-iam/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/warden-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
skills/warden-scan/SKILL.md
- Broad permissionsline 1
Bash, Read, Glob
skills/warden-threat/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/warden/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
skills/wire-prototype/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/wire-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/wire-spec/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/zero-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/zero-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
skills/zero-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/apex/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/apex/scripts/setup.sh
team/apex/skills/apex-diagnose/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep
team/apex/skills/apex-gate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/apex/skills/apex-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/apex/skills/apex-profile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
team/apex/skills/apex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/apex/skills/apex-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/apex/skills/apex-route/SKILL.md
team/apex/skills/apex-stats/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob
team/apex/skills/apex-status/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/apex/skills/apex-takeover/SKILL.md
team/atlas/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/atlas/scripts/setup.sh
team/atlas/skills/atlas-adr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/atlas/skills/atlas-changelog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/atlas/skills/atlas-map/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/atlas/skills/atlas-onboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/atlas/skills/atlas-present/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/atlas/skills/atlas-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/atlas/skills/atlas-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 84
- Collapsible `<details><summary>` for verbose data sections - Copy button on `<pre>` blocks only — appears on hover, hidden by default. **Never on inline `<code>` elements** — inline code is for reading, not copying - Mermaid JS CDN (`http - Network accessline 86
- Mermaid JS CDN (`https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js`) for rendering diagrams, with graceful degradation to plain code blocks if CDN is unavailable
team/audit/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/audit/skills/audit-controls/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/audit/skills/audit-legal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/audit/skills/audit-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/axe/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/axe/skills/axe-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/axe/skills/axe-fix/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/axe/skills/axe-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bench/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/bench/skills/bench-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bench/skills/bench-profile/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bench/skills/bench-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bind/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/bind/skills/bind-gap/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bind/skills/bind-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/bind/skills/bind-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/blue/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/blue/skills/blue-detect/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/blue/skills/blue-harden/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/blue/skills/blue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/brace/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/brace/scripts/setup.sh
team/brace/skills/brace-escalate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-kb/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-metrics/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-sla/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brace/skills/brace-triage/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/brief/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/brief/skills/brief-draft/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/brief/skills/brief-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/brief/skills/brief-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/budget/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/budget/skills/budget-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/budget/skills/budget-optimize/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/budget/skills/budget-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/buzz/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/buzz/scripts/setup.sh
team/buzz/skills/buzz-community/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/buzz/skills/buzz-devrel/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/buzz/skills/buzz-hn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/buzz/skills/buzz-launch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/buzz/skills/buzz-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/buzz/skills/buzz-pitch/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/buzz/skills/buzz-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/buzz/skills/buzz-social/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/cache/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/cache/skills/cache-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cache/skills/cache-evict/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cache/skills/cache-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cast/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/cast/skills/cast-forecast/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cast/skills/cast-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cast/skills/cast-validate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chain/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/chain/skills/chain-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chain/skills/chain-sbom/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chain/skills/chain-scan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/change/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/change/skills/change-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/change/skills/change-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/change/skills/change-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chaos/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/chaos/skills/chaos-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chaos/skills/chaos-game/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/chaos/skills/chaos-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cite/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/cite/skills/cite-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cite/skills/cite-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cite/skills/cite-research/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clause/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/clause/skills/clause-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clause/skills/clause-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clause/skills/clause-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clean/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/clean/skills/clean-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clean/skills/clean-transform/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/clean/skills/clean-validate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/compat/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/compat/skills/compat-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/compat/skills/compat-policy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/compat/skills/compat-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/copy/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/copy/skills/copy-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/copy/skills/copy-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/copy/skills/copy-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cortex/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/cortex/scripts/cortex_agent/eval_scan.py
team/cortex/scripts/setup.sh
team/cortex/skills/cortex-eval/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/cortex/skills/cortex-integrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/cortex/skills/cortex-model/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/cortex/skills/cortex-prompt/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/cortex/skills/cortex-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/crest/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/crest/scripts/setup.sh
team/crest/skills/crest-compete/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/crest/skills/crest-narrative/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/crest/skills/crest-okr/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/crest/skills/crest-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/crest/skills/crest-roadmap/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/cut/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/cut/skills/cut-icon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cut/skills/cut-illustrate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/cut/skills/cut-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/deal/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/deal/scripts/setup.sh
team/deal/skills/deal-close/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/deal/skills/deal-outreach/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/deal/skills/deal-pipeline/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/deal/skills/deal-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/deal/skills/deal-pricing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/deal/skills/deal-proposal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/deal/skills/deal-qualify/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/deal/skills/deal-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/deal/skills/deal-signals/SKILL.md
- Broad permissionsline 1
Read, Write, Bash, Glob, Grep, AskUserQuestion
team/deploy/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/deploy/skills/deploy-canary/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/deploy/skills/deploy-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/deploy/skills/deploy-serve/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/draft/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/draft/scripts/setup.sh
team/draft/skills/draft-flow/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/draft/skills/draft-ia/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/draft/skills/draft-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/draft/skills/draft-patterns/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/draft/skills/draft-proto/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 98
<script src="https://unpkg.com/react@18/umd/react.development.js"></script> - Network accessline 99
<script src="https://unpkg.com/react-dom@18/umd/react-dom.development.js"></script> - Network accessline 100
<script src="https://unpkg.com/@babel/standalone/babel.min.js"></script>
team/draft/skills/draft-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/draft/skills/draft-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/draft/skills/draft-wireframe/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/drift/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/drift/skills/drift-alert/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/drift/skills/drift-monitor/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/drift/skills/drift-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/echo/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/echo/scripts/setup.sh
team/echo/skills/echo-feedback/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/echo/skills/echo-interview/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/echo/skills/echo-jobs/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/echo/skills/echo-panel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/echo/skills/echo-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/echo/skills/echo-segment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/edge/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/edge/skills/edge-cdn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/edge/skills/edge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/edge/skills/edge-route/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/embed/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/embed/skills/embed-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/embed/skills/embed-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/embed/skills/embed-search/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/eval/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/eval/skills/eval-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/eval/skills/eval-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/eval/skills/eval-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/evals/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/evals/skills/evals-analyze/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/evals/skills/evals-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/evals/skills/evals-harness/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/evals/skills/evals-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/evals/skills/evals-regress/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/feat/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/feat/skills/feat-engineer/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/feat/skills/feat-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/feat/skills/feat-store/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/finop/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/finop/skills/finop-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/finop/skills/finop-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/finop/skills/finop-reserve/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/fit/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/fit/skills/fit-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/fit/skills/fit-train/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/fit/skills/fit-tune/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/flux/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/flux/scripts/setup.sh
team/flux/skills/flux-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/flux/skills/flux-migrate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/flux/skills/flux-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/flux/skills/flux-query/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/flux/skills/flux-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/flux/skills/flux-schema/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/folk/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/folk/scripts/setup.sh
team/folk/skills/folk-comp/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/folk/skills/folk-culture/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-hire/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-migrate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-org/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-perf/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/folk/skills/folk-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/forge/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/forge/scripts/setup.sh
team/forge/skills/forge-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/forge/skills/forge-cost/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/forge/skills/forge-diagnose/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/forge/skills/forge-infra/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/forge/skills/forge-network/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/forge/skills/forge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/form/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/form/scripts/setup.sh
team/form/skills/form-animate/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/form/skills/form-brand/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-critique/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-deck/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-direction/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-email/SKILL.md
team/form/skills/form-exam/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/form/skills/form-logo/SKILL.md
team/form/skills/form-mobile/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-palette/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/form/skills/form-social/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-style/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/form/skills/form-tokens/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/form/skills/form-web/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/frame/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/frame/skills/frame-board/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/frame/skills/frame-equity/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/frame/skills/frame-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/gate/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/gate/skills/gate-ci/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/gate/skills/gate-lint/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/gate/skills/gate-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/glyph/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/glyph/skills/glyph-pair/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/glyph/skills/glyph-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/glyph/skills/glyph-scale/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/grid/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/grid/skills/grid-layout/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/grid/skills/grid-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/grid/skills/grid-responsive/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guard/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/guard/skills/guard-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guard/skills/guard-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guard/skills/guard-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guide/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/guide/skills/guide-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guide/skills/guide-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/guide/skills/guide-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/helm/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/helm/scripts/setup.sh
team/helm/skills/helm-arbiter/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/helm/skills/helm-brief/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/helm/skills/helm-handoff/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/helm/skills/helm-plan/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/helm/skills/helm-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/hue/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/hue/skills/hue-palette/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/hue/skills/hue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/hue/skills/hue-token/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/hunt/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/hunt/skills/hunt-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/hunt/skills/hunt-ioc/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/hunt/skills/hunt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/ink/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/ink/scripts/setup.sh
team/ink/skills/ink-brief/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/ink/skills/ink-calendar/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/ink/skills/ink-case/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/ink/skills/ink-cluster/SKILL.md
team/ink/skills/ink-distribute/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/ink/skills/ink-links/SKILL.md
team/ink/skills/ink-local/SKILL.md
team/ink/skills/ink-post/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/ink/skills/ink-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/ink/skills/ink-seo/SKILL.md
team/keel/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/keel/scripts/setup.sh
team/keel/skills/keel-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keel/skills/keel-cadence/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keel/skills/keel-comply/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/keel/skills/keel-legal/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keel/skills/keel-okr/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keel/skills/keel-process/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keel/skills/keel-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/keel/skills/keel-vendor/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/keep/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/keep/scripts/setup.sh
team/keep/skills/keep-churn/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/keep/skills/keep-expand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/keep/skills/keep-health/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/keep/skills/keep-onboard/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
team/keep/skills/keep-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/keep/skills/keep-qbr/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/keep/skills/keep-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/keep/skills/keep-segment/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/kube/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/kube/skills/kube-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/kube/skills/kube-rbac/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/kube/skills/kube-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/lens/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/lens/scripts/setup.sh
team/lens/skills/lens-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/lens/skills/lens-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/lens/skills/lens-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lens/skills/lens-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lens/skills/lens-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/lens/skills/lens-report/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lodge/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/lodge/skills/lodge-dmca/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/lodge/skills/lodge-filing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/lodge/skills/lodge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/lumen/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/lumen/scripts/setup.sh
team/lumen/skills/lumen-abtest/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lumen/skills/lumen-funnel/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lumen/skills/lumen-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lumen/skills/lumen-metrics/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/lumen/skills/lumen-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/mark/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/mark/skills/mark-asset/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mark/skills/mark-brand/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mark/skills/mark-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mesh/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/mesh/skills/mesh-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mesh/skills/mesh-observe/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mesh/skills/mesh-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mint/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/mint/scripts/setup.sh
team/mint/skills/mint-board/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-budget/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-model/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-raise/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/mint/skills/mint-report/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-runway/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mint/skills/mint-unit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, AskUserQuestion
team/mock/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/mock/skills/mock-contract/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mock/skills/mock-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/mock/skills/mock-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/move/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/move/skills/move-animate/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/move/skills/move-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/move/skills/move-system/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/multi/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/multi/skills/multi-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/multi/skills/multi-port/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/multi/skills/multi-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/onboard/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/onboard/skills/onboard-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/onboard/skills/onboard-quickstart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/onboard/skills/onboard-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/patch/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/patch/skills/patch-plan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/patch/skills/patch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/patch/skills/patch-triage/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/pave/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/pave/scripts/setup.sh
team/pave/skills/pave-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/pave/skills/pave-catalog/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 51
owner: platform-team # team name, not individual oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api - Network accessline 52
oncall: @platform-team # who gets paged (Slack handle or PagerDuty rotation) repo: https://github.com/org/user-api docs: https://notion.so/org/user-api-runbook - Network accessline 53
repo: https://github.com/org/user-api - Network accessline 54
docs: https://notion.so/org/user-api-runbook - Network accessline 55
dashboard: https://grafana.org/d/user-api
team/pave/skills/pave-contribute/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, AskUserQuestion - Broad permissionsline 1
Read, Write, Edit, Bash, AskUserQuestion - Network accessline 83
TONONE_TMP=$(mktemp -d) git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 83
TONONE_TMP=$(mktemp -d) git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 84
git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 84
git clone https://github.com/tonone-ai/tonone "$TONONE_TMP/tonone" --depth=1 --quiet - Network accessline 87
gh repo fork --remote-name=fork --clone=false 2>/dev/null || true GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 87
gh repo fork --remote-name=fork --clone=false 2>/dev/null || true GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 88
GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Network accessline 88
GH_USER=$(gh api user --jq .login) git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Network accessline 89
git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 89
git remote add fork "https://github.com/${GH_USER}/tonone.git" 2>/dev/null || \ - Network accessline 90
git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Network accessline 90
git remote set-url fork "https://github.com/${GH_USER}/tonone.git" - Dangerous shell operationline 119
rm -rf "$TONONE_TMP" - Dangerous shell operationline 119
rm -rf "$TONONE_TMP" - Dangerous shell operationline 140
- Push fails → print error, `rm -rf "$TONONE_TMP"`, exit. - Dangerous shell operationline 140
- Push fails → print error, `rm -rf "$TONONE_TMP"`, exit.
team/pave/skills/pave-env/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/pave/skills/pave-golden/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 53
(or: cookiecutter gh:org/service-template) 2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 - Network accessline 54
2. cd my-service && make setup 3. make dev → app running at http://localhost:8000 4. make test → test suite passes - Network accessline 55
3. make dev → app running at http://localhost:8000 - Access to secretsline 91
[Credential-related source omitted] - Network accessline 104
1. `make setup` 2. `make dev` → http://localhost:8000 - Network accessline 105
2. `make dev` → http://localhost:8000 - Access to secretsline 117
[Credential-related source omitted]
team/pave/skills/pave-lsp/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Dangerous shell operationline 91
| `clangd` | `brew install llvm` / `sudo apt install clangd` | - Dangerous shell operationline 118
Unlike the LSP plugins, this one is not a thin wrapper over a binary you install first. It ships its own `.mcp.json`, which starts the server with `uvx --from git+https://github.com/oraios/serena serena start-mcp-server`. The only prerequis - Network accessline 118
Unlike the LSP plugins, this one is not a thin wrapper over a binary you install first. It ships its own `.mcp.json`, which starts the server with `uvx --from git+https://github.com/oraios/serena serena start-mcp-server`. The only prerequis
team/pave/skills/pave-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/phish/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/phish/skills/phish-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/phish/skills/phish-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/phish/skills/phish-train/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/pitch/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/pitch/scripts/setup.sh
team/pitch/skills/pitch-copy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/pitch/skills/pitch-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/pitch/skills/pitch-launch/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/pitch/skills/pitch-message/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/pitch/skills/pitch-position/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/pitch/skills/pitch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/plot/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/plot/skills/plot-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/plot/skills/plot-eda/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/plot/skills/plot-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/port/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/port/skills/port-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/port/skills/port-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/port/skills/port-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/prism/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/prism/scripts/setup.sh
team/prism/skills/prism-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/prism/skills/prism-chart/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/prism/skills/prism-component/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 171
<svg className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" - Network accessline 172
className="h-4 w-4 animate-spin" xmlns="http://www.w3.org/2000/svg" fill="none" - Network accessline 173
xmlns="http://www.w3.org/2000/svg"
team/prism/skills/prism-dashboard/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/prism/skills/prism-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/prism/skills/prism-stack/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/prism/skills/prism-ui/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/prompt/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/prompt/skills/prompt-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/prompt/skills/prompt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/prompt/skills/prompt-version/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/proof/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/proof/scripts/setup.sh
team/proof/skills/proof-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/proof/skills/proof-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/proof/skills/proof-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/proof/skills/proof-e2e/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 90
reporter: [["html"], ["list"]], use: { baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 91
use: { baseURL: process.env.BASE_URL || "http://localhost:3000", trace: "on-first-retry", - Network accessline 92
baseURL: process.env.BASE_URL || "http://localhost:3000", - Network accessline 101
webServer: { command: "npm run dev", url: "http://localhost:3000", - Network accessline 102
command: "npm run dev", url: "http://localhost:3000", reuseExistingServer: !process.env.CI, - Network accessline 103
url: "http://localhost:3000", - Network accessline 257
- run: npx playwright test env: BASE_URL: http://localhost:3000 - Network accessline 258
env: BASE_URL: http://localhost:3000 TEST_EMAIL: ${{ secrets.TEST_EMAIL }} - Network accessline 259
BASE_URL: http://localhost:3000
team/proof/skills/proof-explore/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 76
python3 lib/jev-ultrafast/cli.py explore \ --url http://localhost:3000/signup \ - Network accessline 77
--url http://localhost:3000/signup \ - Network accessline 109
┌─ Flow Exploration ───────────────────────────────────────┐ │ Driver jev-ultrafast | /browse | source-only │ │ Target http://localhost:3000 │ - Network accessline 110
│ Driver jev-ultrafast | /browse | source-only │ │ Target http://localhost:3000 │ │ Flows N run, M reached their final goal │ - Network accessline 111
│ Target http://localhost:3000 │
team/proof/skills/proof-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/proof/skills/proof-strategy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/queue/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/queue/skills/queue-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/queue/skills/queue-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/queue/skills/queue-scale/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/rank/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/rank/skills/rank-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/rank/skills/rank-eval/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/rank/skills/rank-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/red/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/red/skills/red-pentest/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/red/skills/red-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/red/skills/red-report/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/relay/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/relay/scripts/setup.sh
team/relay/skills/relay-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/relay/skills/relay-deploy/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 121
[Credential-related source omitted] - Network accessline 350
BASE_URL="${1:-https://your-service.example.com}" - Network accessline 355
# Health check STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 356
STATUS=$(curl -s -o /dev/null -w "%{http_code}" "$BASE_URL/health") - Network accessline 359
# Latency check LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 360
LATENCY=$(curl -s -o /dev/null -w "%{time_total}" "$BASE_URL/health") - Network accessline 364
# Version check (optional — requires /version or X-Version header) # VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 365
# VERSION=$(curl -s "$BASE_URL/version" | jq -r .version) - Network accessline 396
│ □ [any others] │ │ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ - Network accessline 397
│ │ │ Smoke test: bash scripts/smoke-test.sh https://your-url │ └──────────────────────────────────────────────────────────────┘ - Network accessline 398
│ Smoke test: bash scripts/smoke-test.sh https://your-url │
team/relay/skills/relay-docker/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/relay/skills/relay-pipeline/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/relay/skills/relay-recon/SKILL.md
team/relay/skills/relay-ship/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 214
🤖 **This PR was prepared by [Tonone](https://tonone.ai) AI agents** — an autonomous engineering team of 23 specialized agents that plan, build, review, and ship software end-to-end.
team/resp/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/resp/skills/resp-contain/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/resp/skills/resp-playbook/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/resp/skills/resp-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sample/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/sample/skills/sample-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sample/skills/sample-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sample/skills/sample-write/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sast/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/sast/skills/sast-fix/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sast/skills/sast-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/sast/skills/sast-scan/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/schema/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/schema/skills/schema-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/schema/skills/schema-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/schema/skills/schema-review/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/scope/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/scope/skills/scope-oss/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/scope/skills/scope-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/scope/skills/scope-trademark/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/score/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/score/skills/score-compare/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/score/skills/score-eval/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/score/skills/score-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/serv/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/serv/skills/serv-cold/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/serv/skills/serv-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/serv/skills/serv-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/shield/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/shield/skills/shield-assess/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/shield/skills/shield-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/shield/skills/shield-respond/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/siem/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/siem/skills/siem-alert/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/siem/skills/siem-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/siem/skills/siem-rule/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/spine/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/spine/scripts/setup.sh
team/spine/skills/spine-api/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 73
"message": "Human-readable explanation of what went wrong.", "param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 74
"param": "field_name_if_applicable", "doc_url": "https://your-docs.com/errors/machine_readable_snake_case" } - Network accessline 75
"doc_url": "https://your-docs.com/errors/machine_readable_snake_case" - Network accessline 180
Then: full request/response spec for each endpoint, error codes, curl examples for each. End with what was explicitly ruled out and why (e.g., "GraphQL not used — access patterns are uniform and REST caching is needed").
team/spine/skills/spine-design/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/spine/skills/spine-perf/SKILL.md
team/spine/skills/spine-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/spine/skills/spine-review/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/spine/skills/spine-service/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/spine/skills/spine-simplify/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/surge/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/surge/scripts/setup.sh
team/surge/skills/surge-activation/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/surge/skills/surge-experiment/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/surge/skills/surge-landing/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/surge/skills/surge-plg/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/surge/skills/surge-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/surge/skills/surge-retention/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/terms/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/terms/skills/terms-privacy/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/terms/skills/terms-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/terms/skills/terms-tos/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/terra/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/terra/skills/terra-drift/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/terra/skills/terra-module/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/terra/skills/terra-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/token/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/token/skills/token-budget/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/token/skills/token-chunk/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/token/skills/token-compact/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write
team/token/skills/token-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tone/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/tone/skills/tone-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tone/skills/tone-theme/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tone/skills/tone-token/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/touch/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/touch/scripts/setup.sh
team/touch/skills/touch-app/SKILL.md
team/touch/skills/touch-audit/SKILL.md
team/touch/skills/touch-feature/SKILL.md
team/touch/skills/touch-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/touch/skills/touch-release/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/touch/skills/touch-ui/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep
team/trace/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/trace/skills/trace-debug/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/trace/skills/trace-instrument/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/trace/skills/trace-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tune/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/tune/skills/tune-finetune/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tune/skills/tune-prompt/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/tune/skills/tune-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/vect/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/vect/skills/vect-embed/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/vect/skills/vect-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/vect/skills/vect-search/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/vigil/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/vigil/scripts/setup.sh
team/vigil/skills/vigil-alert/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Network accessline 100
summary: "{{ $labels.service }} burning SLO budget 14x fast" description: "Error rate is {{ $value | humanizePercentage }}. At this rate, the 30-day error budget is exhausted in ~2 hours." runbook: "https://docs.internal - Network accessline 102
runbook: "https://docs.internal/runbooks/[service-name]-high-burn-rate" - Network accessline 120
annotations: summary: "{{ $labels.service }} burning SLO budget 3x — budget will exhaust in ~10 days" runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 122
runbook: "https://docs.internal/runbooks/[service-name]-moderate-burn-rate" - Network accessline 134
annotations: summary: "{{ $labels.service }} P99 latency {{ $value | humanizeDuration }} exceeds SLO" runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 136
runbook: "https://docs.internal/runbooks/[service-name]-latency-breach" - Network accessline 148
message = <<-EOT SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 149
SLO burn rate is {{value}}x. Budget exhausts in ~2 hours. Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate @pagerduty-[service]-critical - Network accessline 150
Runbook: https://docs.internal/runbooks/[service-name]-high-burn-rate - Network accessline 205
1. Check the error rate dashboard: [link] 2. Check recent deployments: `git log --oneline -10` or CI/CD dashboard link 3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz` - Network accessline 207
3. Check if the issue is total outage or partial: `curl -I https://[service]/healthz`
team/vigil/skills/vigil-check/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/vigil/skills/vigil-incident/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/vigil/skills/vigil-instrument/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion - Access to secretsline 96
[Credential-related source omitted] - Network accessline 270
# Grafana Cloud OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 271
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp-gateway-prod-us-central-0.grafana.net/otlp - Network accessline 274
# Datadog OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 275
OTEL_EXPORTER_OTLP_ENDPOINT=https://otlp.datadoghq.com - Network accessline 278
# Honeycomb OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 279
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.honeycomb.io - Network accessline 282
# Self-hosted OTel Collector OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 - Network accessline 283
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
team/vigil/skills/vigil-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/volt/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/volt/scripts/setup.sh
team/volt/skills/volt-driver/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/volt/skills/volt-firmware/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/volt/skills/volt-ota/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/volt/skills/volt-power/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/volt/skills/volt-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/warden/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/warden/scripts/setup.sh
team/warden/skills/warden-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/warden/skills/warden-harden/SKILL.md
team/warden/skills/warden-iam/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/warden/skills/warden-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
team/warden/skills/warden-scan/SKILL.md
- Broad permissionsline 1
Bash, Read, Glob
team/warden/skills/warden-threat/SKILL.md
- Broad permissionsline 1
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
team/wire/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/wire/skills/wire-prototype/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/wire/skills/wire-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/wire/skills/wire-spec/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/zero/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
team/zero/skills/zero-audit/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/zero/skills/zero-design/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
team/zero/skills/zero-recon/SKILL.md
- Broad permissionsline 1
Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
templates/new-agent/.claude-plugin/plugin.json
- Network accessline 5
"author": { "name": "tonone-ai", "url": "https://tonone.ai" - Network accessline 6
"name": "tonone-ai", "url": "https://tonone.ai" }, - Network accessline 7
"url": "https://tonone.ai" - Network accessline 8
}, "repository": "https://github.com/tonone-ai/tonone", "license": "MIT", - Network accessline 9
"repository": "https://github.com/tonone-ai/tonone",
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Declared and executed: 127 facts
- Allows Bash without restrictions, though it has no scripts or shell blocksapex-takeover/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-adr/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-changelog/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-map/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-onboard/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-present/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-report/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-health/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-migrate/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-pipeline/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-query/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksflux-schema/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockslens-audit/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockslens-metrics/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockslens-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockslens-report/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockspave-audit/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockspave-catalog/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockspave-env/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockspave-golden/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockspave-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksprism-audit/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksprism-dashboard/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksprism-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksproof-api/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksproof-audit/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksproof-e2e/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksproof-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksproof-strategy/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvigil-alert/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvigil-check/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvigil-incident/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvigil-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvolt-driver/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvolt-firmware/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvolt-ota/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksvolt-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockswarden-audit/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockswarden-iam/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blockswarden-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksapex-takeover/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-adr/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-changelog/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-map/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-onboard/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-present/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-recon/SKILL.md:4High confidence
- Allows Bash without restrictions, though it has no scripts or shell blocksatlas-report/SKILL.md:4High confidence
and 77 more
Signal confidence: 373 facts
- Broad permissions in the frontmatter of the SKILL.mdapex-plan/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdapex-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdapex-review/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdapex-status/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdapex-takeover/SKILL.md:1High confidence
- Access to secrets in prose of the SKILL.mdapex-takeover/SKILL.md:26Low confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-adr/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-changelog/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-map/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-onboard/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-present/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdatlas-report/SKILL.md:1High confidence
- Network access in prose of the SKILL.mdatlas-report/SKILL.md:84Low confidence
- Network access in prose of the SKILL.mdatlas-report/SKILL.md:86Low confidence
- Broad permissions in the frontmatter of the SKILL.mdcortex-eval/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdcortex-integrate/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdcortex-model/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdcortex-prompt/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdcortex-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-health/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-migrate/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-pipeline/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-query/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdflux-schema/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-audit/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-cost/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-diagnose/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-infra/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-network/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdforge-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdlens-audit/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdlens-dashboard/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdlens-metrics/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdlens-recon/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdlens-report/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdpave-audit/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdpave-catalog/SKILL.md:1High confidence
- Network access in code of the SKILL.mdpave-catalog/SKILL.md:51High confidence
- Network access in code of the SKILL.mdpave-catalog/SKILL.md:52High confidence
- Network access in code of the SKILL.mdpave-catalog/SKILL.md:53High confidence
- Network access in code of the SKILL.mdpave-catalog/SKILL.md:54High confidence
- Network access in code of the SKILL.mdpave-catalog/SKILL.md:55High confidence
- Broad permissions in the frontmatter of the SKILL.mdpave-env/SKILL.md:1High confidence
- Broad permissions in the frontmatter of the SKILL.mdpave-golden/SKILL.md:1High confidence
- Network access in code of the SKILL.mdpave-golden/SKILL.md:53High confidence
- Network access in code of the SKILL.mdpave-golden/SKILL.md:54High confidence
- Network access in code of the SKILL.mdpave-golden/SKILL.md:55High confidence
- Access to secrets in code of the SKILL.mdpave-golden/SKILL.md:91High confidence
and 323 more
Only the first 500 facts are listed.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md bundle/engineering-team/skills/apex-plan/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md bundle/engineering-team/skills/apex-plan/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md bundle/engineering-team/skills/apex-plan/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md bundle/engineering-team/skills/apex-plan/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.