SKILLEMALL.ai
GitHub ↗ RU Sign in

AF agents-get-started

Use when a developer wants to create a new agent project or get started with AgentCore. Handles framework selection, project scaffolding, first deploy, and first invocation. Triggers on: "build an agent", "create an agent", "get started", "new project", "agentcore create", "which framework", "Strands vs LangGraph", "hello world agent", "first agent", "create MCP server", "host MCP server", "agentcore dev", "dev server", "what port", "local development". Not for adding capabilities to existing projects — use agents-build or agents-connect. Strands vs LangGraph in a migration context routes to agents-build, not here. Connecting to an existing MCP server routes to agents-connect, not here.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 4 077 tokens Open the sourceclawhub.ai↗ analyzed 10 h ago

Handles framework selection, project scaffolding, first deploy, and first invocation.

As a process F 62/100 · Will not run — References files that are not bundled: ../agents-build/references/migrate.md, ../agents-debug/references/doctor.md, ../agents-build/references/memory.md

GeneratorAWSDockerAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
95
Quality 40%
84
Run on models
none yet
Process rating
F
62/100
Will not run
References files that are not bundled: ../agents-build/references/migrate.md, ../agents-debug/references/doctor.md, ../agents-build/references/memory.md
Tools and files w 18
0
Running it twice w 4
30
Result and completion w 14
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Grep Glob Bash

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: ../agents-build/references/migrate.md
  • warning missing-ref reference to a missing file: ../agents-debug/references/doctor.md
  • warning missing-ref reference to a missing file: ../agents-build/references/memory.md
  • warning missing-ref reference to a missing file: references/example-support-agent.md
  • warning missing-ref reference to a missing file: references/migrate.md
  • warning missing-ref reference to a missing file: references/doctor.md
  • warning missing-ref reference to a missing file: references/memory.md

Process rating: all ten parameters 62/100

Will not run. References files that are not bundled: ../agents-build/references/migrate.md, ../agents-debug/references/doctor.md, ../agents-build/references/memory.md
  • 0Tools and files. 7 referenced file(s) missing: ../agents-build/references/migrate.md, ../agents-debug/references/doctor.md, ../agents-build/references/memory.md
  • 30Running it twice. 41 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 60Failures and branches. 2 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4077 tokens
  • 85Steps. 51 steps, 3 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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

  • +1No license
  • +2Single-language instructions
  • +5Description quotes 15 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 695: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 51 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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