upgrade-agent-native

Bring an older Agent-Native app or workspace current. Use when updating @agent-native/core, fixing a broken upgrade, or when tempted to patch or override core/dispatch packages to make an old branch run.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

A highly actionable, well-sequenced upgrade workflow with explicit validation and recovery loops — commands are copy-paste ready throughout. It loses points only on conciseness (repeated patch prohibitions and hardcoded version pins) and minor progressive-disclosure structure around the external runbook link.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence with no basic-concept padding, and the body is dense with commands. Held below 5 because the patch prohibition is stated three times (Rule, Why, Don't), step 2's versioned-CLI explanation is long-winded, and version pins (0.198.0, 0.196) are hardcoded throughout without a deprecated/old-patterns framing — the rubric penalizes unprefixed time-sensitive version numbers.	4 / 5
Actionability	Every step is a copy-paste-ready, versioned command: 'npx @agent-native/core@0.198.0 upgrade --codemods --dry-run', 'npx @agent-native doctor', 'agent-native template status/diff/sync/accept/baseline', plus the --skip-verify/--skip-install variants. Specific examples cover the common cases, matching anchor 5.	5 / 5
Workflow Clarity	Clear sequence (preview codemods → apply → doctor verify → optional template sync → failure recovery) with explicit validation checkpoints (--dry-run, doctor's migration-manifest and feature-dependencies checks, typecheck) and a feedback loop ('Read the concrete error → fix app source → re-run → Stop and ask the user if you cannot fix'). Validation is present, so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled, one-level-deep external reference (the Core 0.198.0 runbook link). Not 5: the runbook is a repo-relative path outside the skill with no in-bundle reference structure, and the detailed migration material (codemod limits, symbol path map) lives there rather than in a discoverable skill file; not 3 because all structure present is clean and navigable.	4 / 5
	Total	18 / 20 Passed

Description

87%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.

A strong description with an explicit 'Use when' clause anchored to concrete, natural trigger phrases and a clearly scoped niche. Its only weakness is that the capability description is one macro-action with scenario detail rather than comprehensive action coverage, and it misses synonyms like 'bump' or 'migrate'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Agent-Native app or workspace') and several concrete actions/scenarios — 'updating @agent-native/core, fixing a broken upgrade, or when tempted to patch or override core/dispatch packages'. Not 5 because the 'what' is one macro-action ('Bring... current') with scenario detail rather than comprehensive action coverage (e.g., no mention of codemods, template sync, or doctor).	4 / 5
Completeness	Explicitly answers both: what ('Bring an older Agent-Native app or workspace current') and when ('Use when updating @agent-native/core, fixing a broken upgrade, or when tempted to patch or override...') with concrete trigger phrases, matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	Natural terms a user would say — 'upgrade', 'updating', 'broken upgrade', 'patch', 'override', 'old branch', 'core/dispatch packages'. Missing common variations such as 'bump', 'migrate', or 'version', keeping it below the comprehensive-synonym anchor 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche limited to Agent-Native package upgrades, with distinctive triggers (@agent-native/core, core/dispatch packages) that would not fire for generic dependency-upgrade or migration skills. Third-person voice, no person penalty.	5 / 5
	Total	18 / 20 Passed

Validation

75%

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 — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	12 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/upgrade-agent-native/SKILL.md
Commit: a941a2e

Reviewed: 2 days 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.