SKILLEMALL.ai

BD senior-fullstack

Fullstack development toolkit with project scaffolding for Next.js/FastAPI/MERN/Django stacks and code quality analysis. Use when scaffolding new projects, analyzing codebase quality, or implementing fullstack architecture patterns.

borghei/Claude-Skills Agent Skills author: borghei 7 files · 2 scripts body ≈ 2 004 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Fullstack development toolkit with project scaffolding for Next.js/FastAPI/MERN/Django stacks and code quality analysis. Use when scaffolding new projects…

As a process D 44/100 · Unfinished process — References files that are not bundled: references/*.md

TemplateDockerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
98
Quality 40%
82
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: references/*.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Exfiltration read-dotenv references/tooling-workflows-and-quality.md:158
    Reads a .env file
    cp .env.example .env.local
  • low Exfiltration read-dotenv scripts/project_scaffolder.py:819
    Reads a .env file (quoted — discussed, not commanded)
    "nextjs": [f"cd {name}", "npm install", "cp .env.example .env.local", "npm run dev"],
    quoted

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/*.md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: references/*.md
  • 0Tools and files. 1 referenced file(s) missing: references/*.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 7 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 55Failures and branches. 1 branches
  • 100Steps. 27 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2004 tokens

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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 232: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 27 items
  • +4Reference files are cited in the instructions (4 of 4)
  • +3All 2 scripts are documented
  • +1License stated

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