SkillAgentSearch skills...

plugin-dev-workflow

Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo

Install / Use

npx skills add oliver-kriska/claude-elixir-phoenix --skill plugin-dev-workflow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Category

Automation

Supported Platforms

Claude Code

Our assessment of plugin-dev-workflow

plugin-dev-workflow scores 82/100 on our quality scale, 2242nd of 2,771 Automation skills we index.

Its SKILL.md is 4.1 KB long, well organised into 16 sections with 3 code examples: a solid amount of guidance for an agent.

It has 574 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 13 days ago, so plugin-dev-workflow is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The Autoresearch section instructs the agent to run `claude -p 'Run autoresearch...' --allowedTools 'Edit,Read,Write,Bash,Glob,Grep'`, which pre-approves a broad set of tools for a sub-agent invocation, effectively bypassing per-tool permis.

AI review: risky

  • The Autoresearch section instructs the agent to run `claude -p 'Run autoresearch...' --allowedTools 'Edit,Read,Write,Bash,Glob,Grep'`, which pre-approves a broad set of tools for a sub-agent invocation, effectively bypassing per-tool permis
  • It directs the agent into a self-improvement loop where the sub-agent can autonomously edit files and execute Bash with reduced oversight.
  • Other commands (`make eval`, `python3 -m lab.eval.scorer`, `make lint`) are normal project-local development commands and not malicious by themselves.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

plugin-dev-workflow compared with similar skills

All 4 of these similar skills score higher than plugin-dev-workflow; compare them before choosing.

SkillScoreStarsUpdatedFormat
plugin-dev-workflow (this skill)by oliver-kriska8257413d agoSKILL.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
rufloby ruvnet10082.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.2k10d agoCLAUDE.md
Scraplingby D4Vinci100104.4k2d agoMCP Server

Frequently asked questions

How do I install plugin-dev-workflow?
Run npx skills add oliver-kriska/claude-elixir-phoenix --skill plugin-dev-workflow. The install tabs above show the steps for each supported agent.
Which AI agents does plugin-dev-workflow work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is plugin-dev-workflow safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The Autoresearch section instructs the agent to run claude -p 'Run autoresearch...' --allowedTools 'Edit,Read,Write,Bash,Glob,Grep', which pre-approves a broad set of tools for a sub-agent invocation, effectively bypassing per-tool permis. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is plugin-dev-workflow still maintained?
The repository was last updated 13 days ago, so plugin-dev-workflow is actively maintained.

name: plugin-dev-workflow description: "Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing." effort: medium

Plugin Development Workflow

This repo is the Elixir/Phoenix Claude Code plugin. When editing plugin files, follow this workflow to ensure quality.

Before You Start

Run make help to see all available commands:

make eval          # Quick: lint + score changed skills/agents
make eval-all      # Full: all 51 skills + 26 agents
make eval-fix      # Auto-fix + show failures
make test          # 220 pytest tests for eval framework and port tooling
make ci            # Full CI pipeline

Scoring Individual Files (CLI)

IMPORTANT: Always use -m module syntax, never run scorer.py directly.

# Score ONE skill (use -m, NOT direct file path)
python3 -m lab.eval.scorer plugins/elixir-phoenix/skills/verify/SKILL.md

# Score ONE skill with pretty output
python3 -m lab.eval.scorer plugins/elixir-phoenix/skills/verify/SKILL.md --pretty

# Score all skills
python3 -m lab.eval.scorer --all

# Score ONE agent
python3 -m lab.eval.agent_scorer plugins/elixir-phoenix/agents/verification-runner.md

# Score all agents
python3 -m lab.eval.agent_scorer --all
make ci            # Full CI pipeline

When Editing Skills (plugins/elixir-phoenix/skills/*/SKILL.md)

  1. Read CLAUDE.md conventions (size limits, frontmatter requirements)
  2. Make your changes
  3. Run make eval — it auto-detects changed skills and scores them
  4. If FAIL: check the dimension that failed, fix it
  5. Run make lint to verify markdown formatting
  6. Commit

Skill requirements (eval checks all of these):

  • Frontmatter: name, description, effort. Description must start with action verb + include "Use when..."
  • Iron Laws section with 1+ numbered items
  • Under 185 lines (command skills) or 150 lines (reference skills)
  • No section exceeds 45 lines
  • All /phx: references point to existing skills
  • All references/*.md paths exist
  • No dangerous code patterns outside Iron Laws sections
  • Code examples present (1+ fenced code blocks)
  • "Use when..." in description (for trigger accuracy)

When Editing Agents (plugins/elixir-phoenix/agents/*.md)

  1. Make your changes
  2. Run make eval-agents to score all agents
  3. Agent requirements:
    • no permissionMode (plugin agents ignore it; the plugin directory fails bypassPermissions)
    • disallowedTools: Write, Edit, NotebookEdit for review/analysis agents
    • model matches effort: haiku=low, sonnet=medium, opus=high
    • Under 300 lines (specialist) or 535 lines (orchestrator)

When Editing Eval Framework (lab/eval/*.py)

  1. Make your changes
  2. Run make test — all pytest tests must pass
  3. Run make eval-all — verify no skills/agents regressed
  4. If adding new matchers: add tests in lab/eval/tests/test_matchers.py

When Editing Hooks (plugins/elixir-phoenix/hooks/scripts/*.sh)

  1. Make your changes
  2. Run make lint (markdown in hook comments)
  3. Test the hook manually (hooks run on Edit/Write/Bash events)
  4. Check CLAUDE.md hook documentation is still accurate

Autoresearch (Self-Improvement Loop)

If make eval-fix shows failures, it suggests an autoresearch command:

# Copy-paste the suggested command from eval-fix output
claude -p 'Run autoresearch. Score all skills...' --allowedTools 'Edit,Read,Write,Bash,Glob,Grep'

This runs the autoresearch loop: find weakest skill → fix ONE issue → re-score → keep/revert.

Pre-Commit Checklist

Before committing any plugin changes:

  • [ ] make lint passes
  • [ ] make eval passes (changed files)
  • [ ] make test passes (if eval framework changed)
  • [ ] CHANGELOG.md updated (if user-visible change)
  • [ ] Version bumped in plugin.json (if releasing)

References

  • CLAUDE.md — full conventions, size limits, checklist
  • lab/eval/ — scoring framework (24 matchers, 8 dimensions)
  • lab/autoresearch/ — self-improvement loop
  • lab/findings/interesting.jsonl — log interesting discoveries here

Related Skills

View on GitHub
GitHub Stars574
CategoryAutomation
Updated13d ago
Forks45

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions