Skip to content

oliver-kriska/claude-elixir-phoenix / targets/dsh/skills/phx-deps-audit

phx-deps-audit

Flagged

Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.

references/skill-checklist.md

View on GitHub
# Skill Checklist — Phase 1 lessons baked in

Pre-flight for any new skill or agent added to `claude-elixir-phoenix`.
Captures the concrete gotchas that cost Phase 1 implementation ~15 minutes
each. Apply this list **before** running `make eval`.

## Frontmatter

- `name:` — kebab-case, namespaced when surfaced as a command
  (`phx:deps-audit`). Plain `deps-audit` works for internal skills.
- `description:` — **≤200 characters** and **≥3 keywords** from the
  scorer's Elixir/Phoenix domain list (see `lab/eval/matchers.py:198`).
  Vague descriptions like "Audit deps" score zero on triggering.
  Effective pattern: `"<action> <domain> for <risk surface> —
  <specifics>. Use <when>."` Example:
  `"Audit Hex dep updates for supply-chain security risk — bidi chars,
  compile-time exec, maintainer changes. Use after mix deps.update."`
- `argument-hint:` — quote the value if it contains `[...]`. Unquoted
  square brackets get parsed as YAML flow sequences.
  Wrong: `argument-hint: [--base <ref>] [--json]`
  Right: `argument-hint: "[--base <ref>] [--json]"`

## Headings

- The Iron Laws heading must be literally `## Iron Laws` — no em-dash,
  no parenthetical. The eval scorer's `section_exists` check does a
  literal string match. Variants like `## Iron Laws — Never Violate`
  fail completeness.

## Body

- Keep SKILL.md under ~150 lines. Command skills get ~185.
- Reference paths use `references/<file>.md`. Bare
  `references/<file>.md` paths break in subagents because the cwd is
  the project, not the plugin install.
- Iron Laws section: numbered list with concrete prohibitions and a
  one-sentence rationale per law. Aim for 4-6 laws.

## Markdown lint

- Lists need a blank line above and below (MD032).
- No hard tabs in code fences. Use 2-space indent. Even one tab in a
  Makefile snippet trips MD010 and fails CI.
- Code fences must declare a language (` ```bash ` not just ` ``` `).

## Eval scorer

- `make eval` runs `git diff` to find changed files. **Untracked files
  are invisible.** `git add` the new skill/agent before running, or
  `make eval-all` for the full pass.
- Trigger-accuracy is cached per skill description hash. After tuning
  the description, the cache invalidates on its own.
- Use `make eval-fix` to see exact failures and get auto-fix
  suggestions.
- **Agents use a different scorer than skills.** `make eval` routes
  correctly. Manual scoring during development must pick the right one:
  - Skills → `python3 -m lab.eval.scorer <path>`
  - Agents → `python3 -m lab.eval.agent_scorer <path>`
  - Running `scorer.py` against an agent over-restricts (skill-shaped
    thresholds applied to agent content) and fails on dimensions the
    agent scorer skips. If a manual run reports completeness-0 on an
    obviously-complete agent, you used the wrong scorer.

## Agent-specific

- No `permissionMode` on any agent. Claude Code ignores it on plugin
  agents, and the plugin directory's security scan fails
  `bypassPermissions`.
- Read-only agents (no Write): set `disallowedTools: Edit,
  NotebookEdit` (NOT Write — agents need Write to save their own
  findings file). Set `omitClaudeMd: true`.
- `effort:` must match model: `low` for haiku, `medium` for sonnet
  and opus. Mismatch fails the consistency check.

## Description keyword reference

The fixed Elixir/Phoenix domain list is in `lab/eval/matchers.py`.
Effective single-word triggers include: `audit`, `security`, `review`,
`hex`, `mix`, `liveview`, `ecto`, `oban`, `phoenix`, `elixir`,
`migration`, `changeset`, `genserver`, `supervisor`, `compile`, `test`,
`debug`, `performance`. Aim for ≥3 of these in the description.

## Quick verification flow

```bash
git add plugins/elixir-phoenix/skills/<new-skill>/
make eval-fix          # see failures, get fix suggestions
# Apply fixes, then:
make eval              # confirm pass
```

If only one skill or agent changed, `make eval` runs in <30 s. The
full `make eval-all` over 51 skills + 26 agents takes ~5 min.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall