CtrlK
BlogDocsLog inGet started
Tessl Logo

removing-packages

Use when removing a software package from the Bluefin image, deleting a .bst element, or unwiring a package from the build

83

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.opencode/skills/removing-packages/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

57%

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 focuses entirely on trigger conditions without explaining what the skill actually does. While it has good distinctiveness due to specific technical terms (Bluefin, .bst), it lacks a clear capability statement and relies on jargon that may not match natural user language.

Suggestions

Add a capability statement before the 'Use when...' clause explaining what the skill does (e.g., 'Removes software packages from Bluefin OS images by modifying build configurations.')

Include more natural trigger terms users might say, such as 'uninstall', 'remove software', 'delete from image', alongside the technical terms

DimensionReasoningScore

Specificity

Names the domain (Bluefin image, .bst element) and some actions (removing, deleting, unwiring), but doesn't comprehensively list what specific operations or outcomes are involved beyond these three verbs.

2 / 3

Completeness

Has a 'Use when...' clause which addresses the 'when' question, but the 'what does this do' is only implied through the trigger conditions rather than explicitly stated. The description lacks a clear statement of capabilities.

2 / 3

Trigger Term Quality

Includes some relevant terms like 'removing', 'package', 'Bluefin image', '.bst element', 'unwiring', but uses technical jargon (.bst, unwiring) that users may not naturally say, and misses common variations like 'uninstall', 'delete package'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche targeting Bluefin image management and .bst elements - these are distinctive technical terms unlikely to conflict with general package management or other skills.

3 / 3

Total

9

/

12

Passed

Implementation

100%

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

This is an excellent skill document that provides a comprehensive, actionable checklist for package removal. It excels at conciseness while maintaining completeness, with every step including a verification command. The special cases section handles edge cases well, and the common mistakes table adds valuable guardrails.

DimensionReasoningScore

Conciseness

Every section serves a purpose with no unnecessary explanation of concepts Claude would know. The checklist format is efficient, and verification commands are inline without verbose justification.

3 / 3

Actionability

Provides concrete, executable bash commands for every step. Each verification command is copy-paste ready, and the checklist format makes it clear exactly what to do and in what order.

3 / 3

Workflow Clarity

Clear 10-step sequence with explicit verification commands at each step. Includes critical checkpoint at step 2 ('Do not proceed until all reverse dependencies are resolved') and final validation step. Feedback loop is implicit but clear.

3 / 3

Progressive Disclosure

Well-organized with clear sections: overview, main checklist, special cases, common mistakes, and cross-references. References to related skills are one level deep and clearly signaled at the end.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
projectbluefin/dakota
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.