cross-repo-release-preflight

Fail fast when a release workflow depends on credentials or access to a second repository.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.squad/skills/cross-repo-release-preflight/SKILL.md

Quality

Content

72%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-organized, concise pattern catalog with concrete, actionable guidance and explicit validation checks, but it presents patterns as a list rather than a sequenced workflow with feedback loops for destructive publication operations. Progressive disclosure is excellent for a self-contained single-file skill.

Suggestions

Add a short numbered preflight sequence (e.g., 1. validate secret, 2. verify repo reachability, 3. run sync gate, 4. on failure: fix and re-run) to turn the pattern catalog into a clear ordered workflow.

Include an explicit validate-fix-retry feedback loop for the destructive published-surface overwrite step so failures have a documented recovery path.

Optionally add a minimal example workflow snippet (even a few YAML lines) to lift actionability from concrete guidance toward copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-list guidance that assumes Claude's competence and avoids explaining release/CI basics, with only minor phrases that could be trimmed; it does not pad with concepts Claude already knows.	4 / 5
Actionability	As an instruction-only skill it gives concrete, specific guidance — naming exact secrets (PLUGINS_REPO_TOKEN), repos, workflow files, and behaviors — though it lacks copy-paste code/commands, keeping it just short of fully executable.	4 / 5
Workflow Clarity	Validation checks are explicit (validate secret exists, verify repo reachability, version guards, reject downgrade syncs), but the content is a pattern catalog rather than a sequenced workflow, and there is no validate-fix-retry feedback loop for the destructive published-surface overwrites, capping this at 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed and is organized into clear, well-labeled sections (Context, Patterns, Examples, Anti-Patterns), meeting the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

62%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 concise, third-person, and pairs a clear action with an explicit trigger condition, but it describes only one action and leans on technical phrasing rather than the natural terms a user would say. It is distinct within the release-management niche with low conflict risk.

Suggestions

Add 1-2 more concrete actions (e.g., validate secrets exist, verify target repo reachability) so the capability set reads as comprehensive rather than a single 'fail fast' action.

Include natural trigger phrases and synonyms a user would actually say, such as 'cross-repo publication', 'publishing to a second repo', or 'release CI', alongside the current technical wording.

Consider an explicit 'Use when...' clause to make the trigger guidance unmistakable and push completeness toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain (release workflow, credentials, second repository) and one concrete action ("Fail fast"), but offers only that single preflight action rather than a comprehensive set, matching the 1-2-concrete-actions anchor.	3 / 5
Completeness	It states both what ("Fail fast") and when ("when a release workflow depends on credentials or access to a second repository"), giving an explicit trigger, though the when clause could be more specific about scenarios like cross-repo publication.	4 / 5
Trigger Term Quality	Relevant terms like "release workflow", "credentials", and "second repository" are present but somewhat technical; natural synonyms users might say ("cross-repo", "publishing", "CI release") are missing, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The cross-repo credential/release niche is fairly specific and unlikely to fire for unrelated skills, with only minor overlap risk against general release-management skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sbroenne/mcp-server-excel
Path: .squad/skills/cross-repo-release-preflight/SKILL.md
Commit: b2eab4c

Reviewed: 8 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.