Official agent skill

Scaffold Workshop

by aws-samples in aws-samples/sample-amazon-bedrock-agentcore-onboarding

Scaffold and draft a new AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.

OfficialMIT-0Auto-check: notesDevelopment

Install Scaffold Workshop

skills CLI
$ npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill scaffold-workshop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aws-samples/sample-amazon-bedrock-agentcore-onboarding scaffold-workshop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aws-samples/sample-amazon-bedrock-agentcore-onboarding.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/scaffold-workshop .claude/skills/scaffold-workshop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scaffold-workshop
GitHub stars
133
Token cost
~1.5k tokens
SKILL.md length
692 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT-0

At a glance

Scaffold and draft a new AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.

  • Works in 7 steps: Resolve parameters → Run the scaffold script → Research the feature → …
  • Someone wants to create
  • SKILL.md covers Usage, Arguments, Steps and Reference: Existing Workshop…, plus 1 more section
  • Calls uv

What it does

Scaffold Workshop is an agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding, published by the product's own GitHub organization. Scaffold and draft a new AgentCore workshop. Use when someone wants to create, scaffold, or start a new workshop directory with boilerplate and initial content.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Project scaffolding. It works with Amazon Web Services. The licence is MIT-0.

When your agent uses it

  • Someone wants to create
  • Start a new workshop directory with boilerplate and initial content

Example prompts

  • “/scaffold-workshop”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, AskUserQuestion, WebSearch, WebFetch

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Resolve parameters
  2. Run the scaffold script
  3. Research the feature
  4. Draft README content
  5. Draft README_ja.md content
  6. Draft clean_resources.py
  7. Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 376ee7c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Task
    • TaskCreate
    • TaskUpdate
    • TaskList

    …and 3 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scaffold Workshop loads about 1.5k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 692 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, AskUserQuestion, WebSea

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aws-samples/sample-amazon-bedrock-agentcore-onboarding at commit 376ee7c, republished under its MIT-0 licence (© aws-samples). 692 words, ~1,500 tokens.

Download SKILL.mdSave it as .claude/skills/scaffold-workshop/SKILL.md (or your agent's skills folder).
name
scaffold-workshop
description
Scaffold and draft a new AgentCore workshop. Use when someone wants to create, scaffold, or start a new workshop directory with boilerplate and initial content.
allowed-tools
Bash, Read, Write, Edit, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, AskUserQuestion, WebSearch, WebFetch

Scaffold Workshop

Generate boilerplate files for a new AgentCore workshop, then draft workshop-specific content by researching AWS documentation and following established patterns.

Usage

  • /scaffold-workshop 05_evaluation — Scaffold and draft content for step 05
  • /scaffold-workshop 08_policy --title "AgentCore Policy" — Scaffold with a custom title
  • /scaffold-workshop 09_browser_use --title "AgentCore Browser Use" --description "Web automation with persistent browser profiles" — Full custom scaffold

Arguments

$ARGUMENTS contains the workshop directory name and optional flags.

Parse $ARGUMENTS for:

  • Positional: directory name (required, e.g. 05_evaluation)
  • --title: Workshop title (optional, will be inferred from directory name if not given)
  • --description: One-line description (optional, will be drafted if not given)

Steps

1. Resolve parameters

Parse $ARGUMENTS to extract dir_name, --title, and --description.

If --title is missing, infer it from the directory name:

  • 05_evaluation → "AgentCore Evaluation"
  • 08_policy → "AgentCore Policy"
  • 09_browser_use → "AgentCore Browser Use"

If --description is missing, ask the user with AskUserQuestion what the workshop should cover, or let them provide a free-text description.

2. Run the scaffold script
bash
cd <project_root>
uv run python .claude/tools/scaffold_workshop.py <dir_name> --title "<title>" --description "<description>"

If files already exist, the script will SKIP them (safe to re-run). Inform the user which files were created vs skipped.

3. Research the feature

Search AWS documentation for the AgentCore feature covered by this workshop:

  • Use WebSearch to find relevant AWS docs, blog posts, and SDK references
  • Use WebFetch to read key documentation pages
  • Look at existing workshop implementations in the repo for patterns (Glob + Read)

Gather:

  • The main boto3 / SDK client and API calls involved
  • Key concepts and terminology
  • Typical setup → use → cleanup lifecycle
  • Prerequisites and IAM permissions needed
4. Draft README content

Edit the generated README.md to replace TODO markers with drafted content.

CRITICAL: Preserve all heading levels (#, ##, ###) and the overall section order exactly as generated by the scaffold template. Only replace the TODO placeholder text and code block contents — never remove, rename, or reorder headings.

Replace TODO content in each section:

  • Process Overview: Replace the TODO mermaid diagram with one showing actual service interactions
  • Prerequisites: Replace TODO items with real AWS permissions and prior workshop dependencies
  • File Structure: Update the tree with likely files the workshop will contain
  • Step 1/2 headings: Replace TODO: First Action etc. with real action names, fill in commands and explanations
  • Key Implementation Pattern subsections: Replace ### TODO: Setup Pattern etc. with named patterns (e.g., ### Policy Client Setup), add real code snippets based on SDK docs
  • Usage Example: Replace pass with a complete working code example
  • Benefits section: Replace TODO bullets with real benefits of the feature
  • References: Replace placeholder links with actual AWS documentation URLs

Mark any content that needs verification with <!-- DRAFT: verify this --> HTML comments.

Show full SKILL.md (273 more words)Show less
5. Draft README_ja.md content

Edit the generated README_ja.md to mirror the English README:

  • Preserve all heading levels (#, ##, ###) and section order exactly
  • Translate only the prose and TODO text to Japanese — keep heading structure intact
  • Keep code blocks, mermaid diagrams, and technical terms in English
  • Follow the same translation patterns as existing README_ja.md files (e.g., 01, 03, 06)
6. Draft clean_resources.py

Edit the generated clean_resources.py with realistic cleanup logic:

  • Identify what AWS resources the workshop will create
  • Add proper boto3 client setup and API calls for deletion
  • Follow the pattern from existing cleanup scripts (06_identity, 07_gateway)
  • Keep TODO markers for resource IDs that depend on runtime config
7. Summary

Print a summary of what was created and drafted:

  • List all files created/modified
  • Note which sections still need manual review (marked with <!-- DRAFT -->)
  • Suggest next steps (implement the main test script, verify API calls, etc.)

Reference: Existing Workshop Patterns

Directory → Feature mapping
DirectoryFeatureCategory
01-05Foundation capabilitiesFoundation
06-09Extension capabilitiesExtension
Section heading patterns (English / Japanese)
EnglishJapanese
Process Overviewプロセス概要
Prerequisites前提条件
How to use使用方法
File Structureファイル構成
Step N:ステップN:
Key Implementation Pattern主要な実装パターン
Usage Example使用例
References参考資料
Next Steps次のステップ
clean_resources.py pattern
  • Read config from JSON file (if applicable)
  • Create boto3 client: boto3.client("bedrock-agentcore-control", region_name=region)
  • Delete resources in reverse dependency order
  • Print status for each deletion
  • Remove config files at the end
  • Guard with if __name__ == "__main__":

Important Notes

  • Never overwrite files the user has already edited — check with AskUserQuestion first
  • All drafted content should use real AWS API names and SDK patterns
  • Follow CLAUDE.md: no dummy data, meaningful names, proper error handling
  • The scaffold script lives at .claude/tools/scaffold_workshop.py

© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/scaffold-workshop of aws-samples/sample-amazon-bedrock-agentcore-onboarding.

Open the folder on GitHubat commit 376ee7c

Compare with similar skills

Scaffold Workshop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scaffold Workshop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scaffold Workshop this skillaws-samples/sample-amazon-bedrock-agentcore-onboarding133—~1.5kAutomated safety check: NotesMIT-0
New Resourcemondoohq/mql411—~5.6kAutomated safety check: PassCustom licence
Codegens3s-project/s3s311—~726Automated safety check: PassApache-2.0
New Providergo-to-k/cdkd143—~1.4kAutomated safety check: PassApache-2.0
Nx Plugin For AWSawslabs/nx-plugin-for-aws151—~3.6kAutomated safety check: PassApache-2.0
Agents Get Startedaws/agent-toolkit-for-aws2.8k—~4.3kAutomated safety check: NotesApache-2.0

Similar skills

  • New Resource

    mondoohq/mql

    Add or change a resource in an existing mql provider — schema, codegen, implementation, tests, and verification against a real target.

    411 GitHub stars~5.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Codegen

    s3s-project/s3s

    Change generated code in this repository. An agent skill from s3s-project/s3s.

    311 GitHub stars~726 tokensUpdated today
    DevelopmentAuto-check passed
  • New Provider

    go-to-k/cdkd

    Scaffold a new SDK Provider for a given AWS resource type (e.g., AWS::SES::EmailIdentity).

    143 GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Nx Plugin For AWS

    awslabs/nx-plugin-for-aws

    Official

    Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators.

    151 GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Agents Get Started

    aws/agent-toolkit-for-aws

    Official

    A skill your agent uses when a developer wants to create a new agent project or get started with AgentCore.

    2.8k GitHub stars~4.3k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Architect For Startups

    aws/agent-toolkit-for-aws

    Official

    Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits.

    2.8k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

More from aws-samples/sample-amazon-bedrock-agentcore-onboarding

  • Clean Workshop

    aws-samples/sample-amazon-bedrock-agentcore-onboarding

    Official

    Clean up AWS resources created by the AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.

    133 GitHub stars~789 tokensUpdated 5 days ago
    Auto-check: notes
  • Run Workshop

    aws-samples/sample-amazon-bedrock-agentcore-onboarding

    Official

    Run the AgentCore workshop steps sequentially to test the full attendee experience.

    133 GitHub stars~1.2k tokensUpdated 5 days ago
    Auto-check: notes
  • Sync Ja

    aws-samples/sample-amazon-bedrock-agentcore-onboarding

    Official

    Sync Japanese README translations with English source. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding.

    133 GitHub stars~1.5k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Scaffold Workshop

What does Scaffold Workshop do?

Scaffold and draft a new AgentCore workshop. An agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding. Scaffold Workshop is an agent skill from aws-samples/sample-amazon-bedrock-agentcore-onboarding, published by the product's own GitHub organization. Scaffold and draft a new AgentCore workshop.

When should I use Scaffold Workshop?

Scaffold Workshop fits situations like: someone wants to create; start a new workshop directory with boilerplate and initial content.

How do I install Scaffold Workshop in Claude Code?

Run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill scaffold-workshop -a claude-code`. Or copy the skill folder (.claude/skills/scaffold-workshop in aws-samples/sample-amazon-bedrock-agentcore-onboarding) into .claude/skills/scaffold-workshop in your project. Claude Code loads it when a task matches its description.

How do I install Scaffold Workshop in Codex?

Run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill scaffold-workshop -a codex`. Or copy the skill folder (.claude/skills/scaffold-workshop in aws-samples/sample-amazon-bedrock-agentcore-onboarding) into .agents/skills/scaffold-workshop in your project. Codex loads it when a task matches its description.

Can I use Scaffold Workshop in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/sample-amazon-bedrock-agentcore-onboarding --skill scaffold-workshop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scaffold-workshop, .gemini/skills/scaffold-workshop, .github/skills/scaffold-workshop and .opencode/skills/scaffold-workshop in your project.

What does Scaffold Workshop need to run?

Going by SKILL.md and its folder, Scaffold Workshop needs the command-line tools its instructions call (uv). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, AskUserQuestion, WebSearch, WebFetch.

Does Scaffold Workshop access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scaffold Workshop safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Scaffold Workshop use?

Scaffold Workshop is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scaffold Workshop use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scaffold Workshop?

Skills that share tags, products or a category with Scaffold Workshop: New Resource (mondoohq/mql, 411 stars), Codegen (s3s-project/s3s, 311 stars), New Provider (go-to-k/cdkd, 143 stars) and Nx Plugin For AWS (awslabs/nx-plugin-for-aws, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scaffold Workshop?

aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-amazon-bedrock-agentcore-onboarding, which has 133 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 1, 2026.

Source: aws-samples/sample-amazon-bedrock-agentcore-onboarding on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.