demo-agent-scaffolder

Scaffolds a deliberately flawed toy agent with seeded bugs for eval-toolkit teaching.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill demo-agent-scaffolder-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: demo-agent-scaffolder
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/demo-agent-scaffolder
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill demo-agent-scaffolder-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teaching agent evaluation requires a realistic agent to test against, but building one by hand is slow and real production agents are too clean to demonstrate failure analysis. This Skill scaffolds a synthetic practice agent with intentionally seeded bugs so the failure-analyzer eval toolkit has genuine signal to work with. ## Core Features & Use Cases - Archetype-Based Scaffolding: Builds a demo agent under demo_agent/ for support, RAG, classifier, or tool-using archetypes, complete with synthetic data, 2-4 stubbed fake tools, and a starter system prompt. - Deliberate Bug Seeding: Plants 2-3 subtle, realistic bugs (unenforced policies, dropped multi-intent sub-requests, tool-call argument errors, vague deferral language) that only surface through an actual eval run. - Instructor Documentation: Logs each seeded bug, its code location, and its expected failure-analyzer category in eval/state.md under a clearly marked instructor-only section. - Use Case: An instructor teaching agent evaluation asks for a practice support agent; the Skill scaffolds one with a hidden refund-policy bug, and students then run failure-analyzer to discover and classify it. ## Quick Start Ask the agent to scaffold a demo support agent with seeded bugs under demo_agent/ so you can practice running the failure-analyzer eval toolkit on it.

Frequently Asked Questions about demo-agent-scaffolder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a practice agent to test an eval toolkit?▼

Ask for a demo agent and pick an archetype: support, RAG, classifier, or tool-using. The Skill scaffolds demo_agent/ with synthetic data, stubbed fake tools, a starter system prompt, and 2-3 seeded bugs for the eval toolkit to find.

What kinds of bugs are seeded into the demo agent?▼

Bugs mirror realistic failure patterns: unenforced system-prompt policies, dropped sub-requests in multi-intent scenarios, tool-call argument mapping errors, and vague deferral language. Each maps to a failure-analyzer category and requires an actual eval run to surface.

Does the demo agent make real API calls or use real data?▼

No. Everything is synthetic and local: fake datasets, stubbed tool functions returning canned responses, and no external service calls. This keeps the teaching environment safe and self-contained.

Where are the seeded bugs documented for instructors?▼

They are logged in eval/state.md under a clearly marked Seeded Bugs instructor-notes section, describing each bug, its code location, and its expected failure-analyzer category. This section is kept separate from anything a student would read as ground truth.

When should I not use a scaffolded demo agent?▼

Do not use it as a production agent or as a baseline for real system behavior; it is intentionally flawed for teaching. For production scaffolding, use a standard agent framework skill instead of this eval-training mode.