local-e2e-testing
Use when building the egg OCI image locally, testing changes end-to-end, verifying the image boots, or running any BuildStream commands against the project
83
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.opencode/skills/local-e2e-testing/SKILL.mdQuality
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.
This description functions primarily as a trigger clause without explaining what the skill actually does. While it has excellent distinctiveness due to specific technical terms (egg OCI image, BuildStream), it inverts the typical structure by only providing 'when' without 'what'. The description would benefit from leading with concrete capabilities before the usage triggers.
Suggestions
Add a 'what' clause before the 'Use when' that describes concrete actions, e.g., 'Builds and tests egg OCI images using BuildStream, verifies boot sequences, and runs build pipelines.'
Include common user phrasings as trigger terms, such as 'container build', 'local image testing', 'build pipeline', or 'OCI container'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (egg OCI image, BuildStream) and some actions (building, testing, verifying boot, running commands), but lacks comprehensive detail about what specific operations or outputs are involved. | 2 / 3 |
Completeness | The description is structured as a 'Use when...' clause answering when to use it, but lacks a clear 'what does this do' statement. It only describes triggers without explaining the skill's capabilities or outputs. | 2 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'egg OCI image', 'BuildStream', 'image boots', but these are fairly specialized. Missing common variations users might say like 'container image', 'build locally', or 'end-to-end test'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with distinct triggers: 'egg OCI image' and 'BuildStream' are highly specific terms unlikely to conflict with other skills. Clear domain boundaries. | 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 exemplary skill document that efficiently communicates a complex local development workflow. It excels at providing actionable, copy-paste-ready commands while maintaining excellent organization through tables and clear section hierarchy. The hard gate requirement and troubleshooting table demonstrate thoughtful workflow design with appropriate validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for structured data, avoiding explanations of concepts Claude already knows (like what podman or QEMU are), and every section serves a clear purpose. No padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable commands throughout - from the one-liner `just show-me-the-future` to specific `just bst` invocations. The troubleshooting table maps symptoms directly to fixes with concrete commands. The OTA dev loop is a numbered, copy-paste-ready workflow. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps (OTA dev loop), explicit validation points (the hard gate for commits), and clear feedback loops. The individual steps table shows composable commands with clear dependencies. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, quick reference tables, and detailed sections. References to related skills and external docs (plans/2026-02-15-local-ota-registry.md) are one level deep and clearly signaled. Content is appropriately split between quick reference and detailed explanations. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- projectbluefin/dakota
- Commit
f062bf8
- 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.