SKILLEMALL.ai

AF devcontainer-setup

Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes. Use when adding devcontainer support to a project, setting up isolated development environments, or configuring sandboxed Claude Code workspaces.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 1 959 tokens Open the sourcegithub.com analyzed 2 d ago

Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes.

As a process F 59/100 · Will not run — References files that are not bundled: references/dockerfile-best-practices.md, references/features-vs-dockerfile.md

GeneratorVS CodeDockerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
F
59/100
Will not run
References files that are not bundled: references/dockerfile-best-practices.md, references/features-vs-dockerfile.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: devcontainer-setup (sickn33/agentic-awesome-skills)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/dockerfile-best-practices.md
  • warning missing-ref reference to a missing file: references/features-vs-dockerfile.md
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "date_added"

Process rating: all ten parameters 59/100

Will not run. References files that are not bundled: references/dockerfile-best-practices.md, references/features-vs-dockerfile.md
  • 0Tools and files. 2 referenced file(s) missing: references/dockerfile-best-practices.md, references/features-vs-dockerfile.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 47 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1959 tokens
  • low 13 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 258: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 47 items
  • +3Output format is stated explicitly
  • +4Has examples (18 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.