16 free chapters open · Free studio skills during beta Start from Level 1
newbieskill
newbieskill
Newbie AI
Website Deployment SuiteViral Content SuiteOffice Productivity SuiteIndie Monetization Suite
Skills Pricing
Language:
English 繁體中文 日本語 Español
Real output · checks recorded Real sample · Markdown
30-second walkthrough

Actual debugging observation

The original Node command exited 1 with ENOENT for inputs/missing-file/imput.json.

Before editing, compare two hypotheses:

1. The input was never supplied. Distinguishing observation: list the selected fixture folder and inspect the real filenames.

2. The program references the wrong spelling. Distinguishing observation: compare the readFile URL in run.mjs with the actual filename.

Observed: input.json exists and contains Public practice cards / 24; the code requests imput.json. This supports hypothesis 2. The narrow repair changes that one path. No source data needs to be invented or removed.

Rerun observations

Original input: Public practice cards: 24

Different input: 读书会书签: 17

The missing-input case failed visibly. Full commands and exit statuses are retained in qa.json.

Sample shown exactly as generated without alteration Download full sample
Runtime Codex Executed by your Agent; model tokens billed by provider
Test environment:
Codex · Windows
Agent/model charges depend on your provider. Extra services and requirements are listed in the package.
Node.js 18+

Used in which quest stages

Skills are gear on your AI journey. Connect with main quests for practice and mastery.

2-3 · What to Do When Things Go Wrong →

Continue with this result: Chaining Skills into Pipelines →

✓ Good fit
  • AI beginners following the main quest
  • Start from the matching lesson; no previous task completion is inferred from a page view.
⊗ Not for
  • Unattended work beyond the selected task or unreviewed account access
✦ What you get
  • A failed command, narrow repair and reruns
  • A saved result and its provenance
  • Task-specific checks and a useful next step

Deliverables: complete SKILL.md rule specification + verified sample. Runs locally in your AI Agent.

How to start?

A Skill is a set of rules teaching AI how to get tasks done.

Get & Install ↑
1
Bring your material
Intentionally create an error (e.g., referencing a missing file), and guide the agent to diagnose and fix it.
2
Let your Agent follow the Skill
Master the three rules of debugging instead of restarting sessions at the first error
3
Open and check the saved result
The agent proposed at least two hypotheses before touching code
Send to your AI Agent

Use debugging to help me complete this task. Ask for missing material, use actual tools, save the result, and check it against the learning criteria.

Before you start The evidence states its exact scope. Model output and permissions depend on your Agent. Automatic discovery is not established by extracted files. Agent/model charges depend on your provider. Extra services and requirements are listed in the package.

Get started here

The zip ships the rules, the reference library, the scripts, the real outputs and the demo — not just a prompt file.

Download full pack (.zip) Download SKILL.md
  1. Open Codex or Claude Code and paste the installation prompt.
  2. Let the Agent read and save the full rules, then confirm discovery.
  3. Copy the usage prompt above, insert your materials, and execute.
Manual installation · View complete SKILL.md (54 lines)

Codex：~/.agents/skills/debugging/SKILL.md
Claude Code：~/.claude/skills/debugging/SKILL.md

--- name: debugging description: Help a beginner reproduce a concrete error, compare at least two plausible causes, apply a narrow fix and rerun the original operation. Use when an Agent task or small script fails and the learner needs evidence rather than random retries. --- # Reproduce, explain, fix, check Main quest 2-3. Save the original error and a verified result. ## Start from an actual failure Ask for the exact command, selected folder, observed error and expected behavior. Read the relevant source and input before changing anything. Reproduce only within the authorized project and with harmless local inputs. Preserve the original error text and failing exit status. If reproducing would send messages, spend money or modify live data, first choose a read-only or isolated reproduction. ## Compare hypotheses before editing Write at least two plausible causes and one observation that could distinguish them. For a missing file, compare an incorrect relative path with a missing input file. For wrong values, compare parsing with incorrect source data. Check the discriminating observation; do not label a guess as the root cause. Prefer the smallest change that explains the actual failure. Do not reset repositories, delete user files or reinstall everything to hide an error. ## Fix and verify Save a narrow patch in the practice copy or the authorized existing file. Rerun the exact failed operation with the same original input. Then use a second different normal input to catch a hardcoded fix. Check the expected error when required input is genuinely absent. Save command, exit status, observed output and why the result resolves the failure. Separate a successful local reproduction from production compatibility. ## Practice files `inputs/missing-file/` contains an intentional path mistake and a harmless public JSON input. Run its `run.mjs` inside that folder to observe the error. Keep the original broken file as evidence; save the repair to a new practice output directory. Read `references/hypothesis-log.md` for the short evidence record format. ## Self-tests and failure criteria 1. Reproduce the missing-file error, record two hypotheses, confirm which path exists and repair the reference. Result must preserve the JSON title and quantity. 2. Replace the input with the separate Unicode fixture, rerun the repaired code and verify the different values. Do not copy test one's output. 3. Run without any input file. It must fail visibly; do not create a guessed input to report success. 4. If the fix changes unrelated files or only suppresses the exception, the task fails. ## Continue Return `/path/debugging/`. Next `/path/skill-chain/`: keep intermediate files and prove the next step consumes them. Original free workflow; personal and commercial use allowed, no complete-package resale.

FAQ for beginners

Clear answers before you start, smooth execution when you run.

How do I start? +
Download the complete ZIP and give the install prompt to your Agent. Keep its scripts and reference files together. Model charges are separate.
Is this main quest Skill free? +
Yes. The foundational main quest is free. Optional advanced Studio products keep their individual pricing.
newbieskill Membership

A solution for every repetition.

One subscription unlocks all Studio Skills. Only need this one? Grab it individually.

Compare full plans
Free What to Do When Things Go Wrong
Get Skill