lanej/dora
claude/skills/dora/SKILL.md
DORA engineering metrics project at ~/src/dora. Load when: querying DORA BigQuery views (deployment frequency, lead time, change failure rate, alerts, review time) from any project; joining against DORA.unified_identity or DORA_clean.* views from any project; running the data pipeline (just refresh, just download-*, just upload-*); making OpenTofu infrastructure changes to DORA tables or views; working with team attribution, team identity, or engineer roster data.
$ install --global
skillsauthnpx skillsauth add lanej/dotfiles doraInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 7:45 AM36.2s6 files scanned
SKILL.md
- name:
- dora
- description:
- DORA engineering metrics project at ~/src/dora. Load when: querying DORA BigQuery views (deployment frequency, lead time, change failure rate, alerts, review time) from any project; joining against DORA.unified_identity or DORA_clean.* views from any project; running the data pipeline (just refresh, just download-*, just upload-*); making OpenTofu infrastructure changes to DORA tables or views; working with team attribution, team identity, or engineer roster data.
DORA — EasyPost Engineering Metrics
Project: ~/src/dora | BQ project: easypost-platform
Dataset Layers
| Dataset | Purpose | When to query |
|---------|---------|---------------|
| DORA_raw | Append-only raw inputs — accumulate duplicates | Never query directly |
| DORA_clean | Deduplicated views — one authoritative row per entity | Direct entity access (bugs, deployments, revisions, ADO PRs) |
| DORA | Analytical views + curated tables | All reporting and metric computation |
Core Rules
- Never query
DORA_raw.*— always useDORA_cleanorDORAviews dora_team_namemust be canonical display names — e.g.'Platform','Carriers','USPS'; never HR cost-center codes like'236 - Enterprise'- Always
dry_runbefore executing BQ queries — usemcp__bigquery__dry_runorbigquery dry-run "..." - Staleness:
docs/bigquery-data-dictionary.mdis authoritative and kept in sync by commit policy; when a view name is uncertain, check there first
Auth / Environment
gcloud auth application-default login # BQ auth
Required CLIs: gh (GitHub), az (Azure DevOps), pd (PagerDuty), phab (Phabricator)
Domain References
Read the relevant file with the Read tool before working in that domain:
| Domain | File | Covers |
|--------|------|--------|
| Metrics / BQ queries | ~/.claude/skills/dora/references/metrics.md | Primary views per DORA pillar, secondary views, query patterns, team + date filters |
| Data pipeline | ~/.claude/skills/dora/references/pipeline.md | just commands, upload CLI taxonomy (3 CLIs), troubleshooting |
| Team attribution / identity | ~/.claude/skills/dora/references/identity.md | unified_identity, email_prefix join key, taxonomy anti-patterns, PHAB overrides |
| Infrastructure | ~/.claude/skills/dora/references/infra.md | Schema authoring (infra/schemas/*.yml), view/table workflow, column rename rules |
| Enterprise / Azure DevOps | ~/.claude/skills/dora/references/enterprise.md | Two ADO orgs, PR/commit/bug/task tables, email join pattern, CLS deployments |
Related Skills
lanej/data-pipeline
development
VerifiedTrustedCommunity
Data pipeline architecture patterns and best practices, including medallion/three-layer architecture (Raw/Staging/Enriched or Bronze/Silver/Gold), YAML-based schema management, and ETL workflow patterns. Use when designing or implementing data pipelines, working with data warehouse layers, or managing table schemas in YAML.
39SKILL.mdUpdated Jun 12, 2026
lanej/research
data-ai
VerifiedTrustedCommunity
Delegate research and context-gathering tasks to a sub-agent to protect the primary context window. Use when the user asks to "research X", "look into X", "find out about X", "gather context on X", or any investigative framing where answering requires 2+ searches or multiple sources. Also use proactively before starting substantive work when prior context is unknown. Never run research inline — always delegate.
39SKILL.mdUpdated May 31, 2026
lanej/claude/skills/qmd-math
documentation
VerifiedTrustedCommunity
--- name: qmd-math description: Math notation conventions for Quarto/EPQ documents rendered via lualatex. Use when: writing or adding a formula, equation, or mathematical expression to a .qmd file; asked about display math, inline math, or LaTeX notation in a QMD/Quarto context; defining a where-clause or variable definitions for an equation; converting prose variable descriptions into structured math notation; fixing math that renders badly in a PDF; using \lvert, \begin{aligned}, \tfrac, \text
39SKILL.mdUpdated May 26, 2026
lanej/trim
development
VerifiedTrustedCommunity
Trim a prose document (README, design doc, blog post, notes) for readability by cutting redundancy, filler, and dead weight in the author's own words. Invoke with /trim [file path], or /trim alone to be prompted for a file. Not for source code, data files, or summarization.
39SKILL.mdUpdated May 24, 2026