Name: magpie-setup
Rating: 57.599999999999994 (1 reviews)
Author: apache

magpie-setup

Adopt and maintain the apache-magpie framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo; every other skill is a symlink the adopt sub-action wires up. Sub-actions: `/magpie-setup` - first-time adoption (default; main-checkout only) `/magpie-setup upgrade` - refresh the gitignored snapshot per the committed lock (main-checkout only) `/magpie-setup worktree-init` - symlink a worktree's snapshot to the main's `/magpie-setup verify` - health check + drift detection `/magpie-setup skill-sources` - fetch/pin/symlink skills from trusted external sources listed in the adopter trust list (main-checkout only) `/magpie-setup override <skill>` - open or scaffold an agentic override in `.apache-magpie-overrides/` `/magpie-setup unadopt` - reverse the adoption (snapshot, locks, symlinks, hook, doc sections); preserves `.apache-magpie-overrides/` by default (main-checkout only)

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/magpie-setup/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured overview that dispatches cleanly to one-level-deep detail files and supplies concrete lock-file formats and detection commands. Its weaknesses are moderate verbosity from restating the adoption model across the intro and golden rules, and a long inlined ruleset that keeps progressive disclosure just short of a clean overview.

Suggestions

Collapse the overlap between the opening 'setup' section and Golden rules 1, 4, 5, and 6 (which restate the snapshot/gitignore/canonical-symlink model) to recover token budget.

Move the verbatim lock-file format blocks and possibly the golden-rules contract into a dedicated detail file, leaving the body a leaner overview that links to it.

Surface the key validation checkpoints (drift check before upgrade, verify after install) as a short inline checklist so the workflow's safety nets are visible without opening the detail files.

Dimension	Reasoning	Score
Conciseness	The content is dense and domain-specific (apache-magpie is a custom framework Claude does not already know, so explanation is warranted), but the nine golden rules restate points already made in the opening 'setup' section and the lock-file prose, so it could be tightened without losing information.	3 / 5
Actionability	Concrete, copy-paste-ready artefacts are provided — verbatim lock-file formats, the `git rev-parse --git-dir` vs `--git-common-dir` worktree-detection command, and an explicit sub-action dispatch table — with only minor gaps because the actual execution steps are deferred to the detail files.	4 / 5
Workflow Clarity	The upgrade flow is laid out as a numbered five-step sequence (delete snapshot, re-install per committed lock, refresh symlinks, reconcile overrides, update local lock) with drift detection as the trigger and a verify sub-action, and unadopt surfaces its removal plan before writing; minor validation detail lives in the referenced detail files rather than inline.	4 / 5
Progressive Disclosure	A 'Detail files in this directory' table gives clear one-level-deep navigation to adopt/upgrade/verify/skill-sources/agents/overrides/unadopt, and the body serves as an overview, but at roughly 400 lines it inlines the verbatim lock-file formats and nine golden rules that could arguably live in their own files.	4 / 5
	Total	15 / 20 Passed

Description

67%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and highly distinctive, clearly laying out seven concrete sub-actions for a well-scoped framework-adoption niche. Its main weakness is the absence of explicit 'when to use' trigger phrasing inside the description field itself, which caps completeness and leaves trigger-term quality at the mid-range.

Suggestions

Fold one explicit trigger sentence into the description field (e.g. 'Use when the user wants to adopt, upgrade, verify, or remove apache-magpie in a repo') so the 'when' is present without relying on the separate when_to_use field.

Add a few natural user-phrased trigger terms ('set up magpie', 'check magpie drift') alongside the command forms to lift trigger-term quality.

Keep the sub-action list but consider trimming the parenthetical main-checkout-only annotations to reduce length without losing specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across seven sub-actions — 'first-time adoption', 'refresh the gitignored snapshot per the committed lock', 'health check + drift detection', 'fetch/pin/symlink skills from trusted external sources', 'reverse the adoption' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clear and detailed, but the description field itself has no 'Use when...' clause or equivalent explicit trigger guidance — that guidance is in the separate when_to_use field — so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	Relevant domain verbs are present (adopt, upgrade, verify, unadopt, drift, snapshot) but they are framed as command syntax rather than the natural phrases a user would say; common variations like 'set up magpie' or 'check magpie drift' live in the separate when_to_use field, not the description.	3 / 5
Distinctiveness Conflict Risk	It carves a clear niche — apache-magpie snapshot-based adoption — with distinct `/magpie-setup` invocation triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 26 missing, 9 suspicious	Warning

	Total	14 / 16 Passed

Repository: apache/airflow
Path: .agents/skills/magpie-setup/SKILL.md
Commit: 1f529f3

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.