skillshare-devcontainer
Run CLI commands, tests, and debugging inside the skillshare devcontainer. Use this skill whenever you need to: execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI, or perform any operation that requires a Linux environment. All CLI execution MUST happen inside the devcontainer — never run skillshare commands on the host. If you are about to use Bash to run `ss`, `skillshare`, `go test`, or `make test`, stop and use this skill first to ensure correct container execution.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that clearly defines its scope (skillshare devcontainer operations), lists specific actions and commands, and provides explicit trigger guidance including a helpful 'stop and use this skill' clause. The description is comprehensive yet focused, with strong distinctiveness through specific tool and command references.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'execute skillshare CLI commands for verification, run Go tests (unit or integration), reproduce bugs, test new features, start the web UI'. Also specifies exact commands like 'ss', 'skillshare', 'go test', 'make test'. | 3 / 3 |
Completeness | Clearly answers both what ('Run CLI commands, tests, and debugging inside the skillshare devcontainer') and when ('Use this skill whenever you need to: execute skillshare CLI commands...'). Includes explicit trigger guidance with the 'If you are about to use Bash to run...' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CLI commands', 'tests', 'debugging', 'devcontainer', 'Go tests', 'unit or integration', 'bugs', 'web UI', 'Linux environment', 'Bash', plus specific command names 'ss', 'skillshare', 'go test', 'make test'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets 'skillshare devcontainer' operations with explicit command names. The warning 'never run skillshare commands on the host' and specific tool names ('ss', 'skillshare') make it unlikely to conflict with generic bash or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent executable examples and clear workflows for devcontainer CLI execution. The main weakness is length - it tries to be comprehensive which leads to some verbosity and could benefit from splitting advanced topics (ssenv details, test patterns) into separate referenced files. The 'Common Mistakes to Avoid' section is particularly valuable for preventing errors.
Suggestions
Trim the Architecture section - Claude doesn't need the full explanation of what devcontainer/ssenv are; focus on the practical implications (Linux binary, bind-mount, auto-build)
Move the detailed ssenv quick reference and advanced ssenv workflows to a separate SSENV.md file, keeping only the essential create/enter/delete pattern inline
Remove explanatory phrases like 'Good for:' lists - the 'When to Use' section already covers this
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundant explanations (e.g., explaining what devcontainer and ssenv are when Claude can infer from context). The architecture diagram and some explanatory text could be trimmed while preserving clarity. | 2 / 3 |
Actionability | Excellent executable examples throughout - copy-paste ready commands for container access, running tests, ssenv workflows, and web UI. Every section provides concrete, working commands with proper syntax. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation (verify container running, check binary). The 'Common Mistakes to Avoid' section serves as validation checkpoints. Sequences like ssenv create → enter → cleanup are well-documented with proper ordering. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a long monolithic document (~200 lines). The ssenv quick reference table and ports table are good, but detailed ssenv workflows and test patterns could be split into referenced files for better navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- runkids/skillshare
- Commit
053ecb4
- 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.