gc-rigs

Managing rigs — add, list, status, suspend, resume

Quality

79%

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 ./internal/bootstrap/packs/core/skills/gc-rigs/SKILL.md

Quality

Content

87%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 lean and highly actionable with well-organized sections, but destructive operations like suspend and restart lack validation/confirmation steps.

Suggestions

Add a confirmation step before destructive ops, e.g. 'Confirm the rig name and warn the user that all agents will stop before running `gc rig suspend`.'

Add a post-op validation checkpoint, e.g. run `gc rig status <name>` after suspend/restart to verify the expected state.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned content with executable commands and no padding or explanations of concepts Claude already knows.	5 / 5
Actionability	Copy-paste ready `gc rig` and `bd` commands with inline comments cover all common cases concretely.	5 / 5
Workflow Clarity	Sequences are clear, but destructive/batch ops (suspend, restart) have no validation or confirmation checkpoints, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Under 50 lines, no external references needed, and well-organized into clear sections — the simple-skill exception applies.	5 / 5
	Total	18 / 20 Passed

Description

71%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 and specific with concrete actions and a clear niche, but it lacks an explicit 'Use when' trigger clause, which caps completeness.

Suggestions

Add a 'Use when' clause, e.g. 'Use when the user wants to add, list, check status, suspend, resume, or restart rigs.'

Include natural synonyms a user might say, such as 'project directories' alongside 'rigs', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists five concrete, distinct actions — 'add, list, status, suspend, resume' — covering the skill's capabilities comprehensively.	5 / 5
Completeness	A clear 'what' is stated but there is no 'when'/'Use when' trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Domain term 'rigs' and command verbs ('add', 'list', 'status', 'suspend', 'resume') are natural things users say, but no synonyms or extensions are present.	4 / 5
Distinctiveness Conflict Risk	'Managing rigs' is a clear niche with distinct triggers and minimal overlap risk, though closely related ops skills could share some verbs.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: crypt0nerd1/gascity
Path: internal/bootstrap/packs/core/skills/gc-rigs/SKILL.md
Commit: f530008

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.