SKILLEMALL.ai
GitHub ↗ RU Sign in

AC local-dev-setup

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service dependencies, database seeding, running the service, running tests, common gotchas, IDE recommendations, and first-contribution checklist. Use when asked to write a dev setup guide, create onboarding documentation for engineers, document local environment setup, or write a getting-started guide for a codebase. Produces a complete setup guide that a new engineer can follow from zero to running tests in under 30 minutes, with a troubleshooting section for the most common setup failures.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 1 file body ≈ 4 345 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Write a local development environment setup guide for a service or project — covering prerequisites, repository setup, environment variables, local service…

As a process C 58/100 · Has gaps — weak spots: when it triggers, failures and branches, progress reporting

GeneratorGitHubVS CodeDockerPostgreSQLSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
97
Quality 40%
85
Run on models
none yet
Process rating
C
58/100
Has gaps
Failures and branches w 10
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: local-dev-setup (mohitagw15856/pm-claude-skills)

How to improve

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

    ✓ No critical or high findings

    Medium and low: 3
    • low Exfiltration read-dotenv SKILL.md:97
      Reads a .env file
      cp .env.example .env.local
    • low Exfiltration read-dotenv SKILL.md:403
      Reads a .env file
      # If not: source .env.local && make test-integration
    • low Exfiltration read-dotenv SKILL.md:434
      Reads a .env file
      cat .env.local | grep "^[A-Z]" | awk -F= '{print $1}'

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 58/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4345 tokens
    • 85Steps. 48 steps, 3 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • low 15 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)
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 645: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 48 items
    • +3Output format is stated explicitly
    • +4Has examples (20 code blocks)

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