Menu
SkillsMP has collected 11 skills from decodingai-magazine/building-a-coding-agent-from-scratch-course. Open a skill to review its source and details.
Showing 11 of 11 collected skills.
Demo skill that web-fetches two Decoding AI knowledge-graph articles, has the agent itself distill them into a typed entity/relation graph, and renders an interactive dark-themed force-directed KG into one self-contained kg.html — no graph library, no CDN.
Manual end-to-end QA playbook for decode against a real provider — what to type at each surface (chat, gated read/write, bash, todo, web_fetch, ask_user, lsp, agent subagents, docker/modal sandboxing, headless `decode run`, HITL, model override, replay,…
Demo skill for the meta "decode improves decode" flow — launch decode in a sandboxed clone of the course repo, plan and build one small feature inside the Workspace, let Hand-back push the Session Branch, then open a draft PR against the course repo.
Demo skill that builds a colorful, playable terminal Snake game in a single pure-stdlib Python curses file — score HUD, speed ramp, eat/death animations, and a game-over screen.
Demo skill that hunts two seeded bugs in a tiny stats package until its tests go green, then files a detective-style CASE_FILE.md with the evidence.
Demo skill that pulls live GitHub API data for a repo, analyses a full year of weekly commit activity and top contributors, and renders a single-file dashboard.html with stat tiles and inline SVG charts — no chart library.
Demo skill that fans out three parallel read-only Explore subagents to review three decode modules, then merges their findings into one severity-ranked verdict with health scores and a diagram per module, written to review-verdict.md.
decode's Kitaru operator surface for headless replay and what-if — three-runs (observed / baseline-rerun / fork), CLI replay with --args/--overrides, checkpoint overrides, diffing execution records, cohort scaling, wait re-ask behavior,…
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Stage the appropriate changes and commit them with a Conventional Commits message.
Review the working-tree diff for bugs and over-engineering.