Menu
Validates coach markdown files for required frontmatter fields, sections, and naming conventions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when designing prompts for LLMs, optimizing model performance, building evaluation frameworks, or implementing advanced prompting techniques like chain-of-thought, few-shot learning, or structured outputs.
How to deploy Dravr infrastructure and apply Cloud Run config changes. Use when editing infra/ terraform, when a merged code change is live but a Cloud Run setting (cpu, memory, min/max instances, env var, scaling) hasn't taken effect, or when asked to plan/apply infra. Explains the two-pipeline model (app binary auto-deploys on push; terraform infra config is a separate manual apply) plus the cpu/cpu_idle guardrails.
Enforces zero-tolerance code quality policy using Clippy with strict lints, all warnings treated as errors
Write well-formatted notes to the dravr-vault Obsidian knowledge base. Use this skill whenever creating or updating an ADR, runbook, plan, API doc, guide, session output, or any structured document that should land in the vault — even when the user doesn't say "Obsidian" explicitly. Delegates to obsidian:obsidian-cli to write to the live vault and applies Dravr frontmatter and formatting standards.
Bootstrap Pierre server with database, admin user, coaches, and test users for development and testing
Use when setting up the shared dravr-vault Obsidian vault on a new machine or for a new team member. Guides through cloning, symlinking claude_docs, and verifying obsidian-cli.
Based on SOC occupation classification
| name | validate-coaches |
| description | Validates coach markdown files for required frontmatter fields, sections, and naming conventions |
| user-invocable | true |
CLAUDE: When this skill is invoked with /validate-coaches, validate all coach files in the coaches/ directory.
Validates coach definition markdown files for schema compliance, required fields, section structure, and naming conventions.
/validate-coaches
find coaches -name "*-coach.md" -type f
CLAUDE: Read each coach file and verify:
name: Must be kebab-case, must match filename (without -coach.md)title: Must be present and non-emptycategory: Must be one of: training, nutrition, recovery, mobility, recipes, customtags: Must be an array if presentvisibility: Must be one of: tenant, public, private (defaults to tenant)prerequisites.providers: Array of provider names if presentprerequisites.min_activities: Number if presentprerequisites.activity_types: Array of activity types if present## Purpose - Must exist, must have content## Instructions - Must exist, must have content## When to Use## Example Inputs## Example Outputs## Success Criteria## Related Coaches# Each file should be in the correct category directory
# training/*.md should have category: training
# nutrition/*.md should have category: nutrition
# etc.
find coaches -name "*-coach.md" -type f | sort
# For each file, extract and validate YAML frontmatter
head -20 coaches/training/marathon-coach.md
# Filename should be: {name}-coach.md
# Frontmatter name should match
cargo run --bin pierre-cli -- seed coaches
This command will fail if any coach file is malformed.
For each coach file:
{name}-coach.md pattern--- markersname field matches filename (without .md)title field is presentcategory field is valid## Purpose section exists with content## Instructions section exists with contentcargo run --bin pierre-cli -- seed coaches completes without errors---
name: example-coach
title: Example Coach
category: training
tags: [example, demo]
visibility: tenant
---
## Purpose
Brief description of what this coach specializes in.
## Instructions
You are an expert coach specializing in [area].
test-intelligence-algorithms - Algorithm validation