CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-starbase

Syncs Starbase-managed project files by adding the canonical/starbase remote and merging starbase/main into the current branch. Use when updating common.mk and related shared Starcraft build/CI conventions.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent operational content: the multi-phase workflow is unambiguous, validation and feedback loops are explicit at every risky step, and all commands are executable as written. Detail is appropriately pushed to real, one-level-deep bundle files; only minor token tightening (commit template, Vale rationale) is possible.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive operational guidance with no explanations of concepts Claude already knows, matching anchor 4; minor instances could be trimmed (the ~20-line commit message template and the extended Vale/spelling disposition rationale).

4 / 5

Actionability

Fully executable throughout: the prepare_merge.sh invocation with documented args, the placeholder grep pipeline, the make validation suite, the complete copy-paste squash recipe (MERGE_HASH / reset --soft / amend / force-with-lease), and a fill-in commit template — matching anchor 5's copy-paste-ready standard with only inherent placeholders like <path-to-skill>.

5 / 5

Workflow Clarity

Four clearly sequenced phases with explicit validation checkpoints and error-recovery loops: the four-way STATUS block routing (clean/conflicted/already-up-to-date/failed with fix-and-re-run guidance), the mandatory deletion checklist, the required pre-PR make suite with "Do not create the PR until these commands complete successfully", and two precisely defined squash points — matching anchor 5.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that defers detail to six well-signaled, one-level-deep reference files (all verified present in references/) plus scripts/prepare_merge.sh, each loaded at its point of need with a description of what it contains — matching anchor 5's easy navigation standard.

5 / 5

Total

19

/

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: it states the core sync mechanism in two concrete git operations and pairs it with an explicit, well-triggered "Use when" clause anchored on distinctive project terms. Its only weakness is that it covers just the merge mechanics, omitting the skill's substantial validation, PR, and review phases.

Suggestions

Consider mentioning one or two downstream capabilities (e.g. conflict resolution rules or PR creation) so the description reflects the full workflow scope.

Add a natural trigger synonym such as "syncing shared build/CI conventions" to broaden the "when" clause beyond the specific file names.

DimensionReasoningScore

Specificity

Names the domain and two precisely specified concrete actions ("adding the canonical/starbase remote and merging starbase/main into the current branch") — more concrete than anchor 3's generic examples, but coverage gaps (no mention of conflict resolution, validation, or PR creation) keep it below anchor 5's comprehensiveness.

4 / 5

Completeness

Explicitly answers both questions: a clear "what" ("Syncs Starbase-managed project files by adding... and merging...") and an explicit "Use when..." clause with concrete trigger phrases ("updating common.mk and related shared Starcraft build/CI conventions"), matching the anchor 5 example's structure.

5 / 5

Trigger Term Quality

"updating common.mk", "Starbase", and "Starcraft build/CI conventions" are natural terms a user of this system would say, matching anchor 4's good-but-not-exhaustive coverage; a few natural variations (e.g. "sync shared build files") are missing.

4 / 5

Distinctiveness Conflict Risk

"Starbase", "common.mk", and "Starcraft" are highly distinctive niche terms that no other skill would share, giving a clear trigger niche with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

canonical/copilot-collections

Path

groups/starcraft/skills/update-starbase/SKILL.md

Reviewed

Table of Contents

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.