16 關免費主線已開放 · Skill 池內測期免費領取 從第一關開始
菜鸟skill
菜鸟skill
新手學AI
部署網站一條龍自媒體創作一條龍職場提效一條龍商業變現一條龍
Skills 定價
語言:
English 繁體中文 日本語 Español
真實產出 · 已記錄檢查 真實樣例 · Markdown
30 秒看完完整流程

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.

樣例內容原樣呈現，僅做閱讀排版 下載完整樣例
運行方式 Codex 由你的 Agent 執行，模型用量由服務商計費
實測環境：
Codex · Windows
Agent／模型費用依供應商而定；額外服務與依賴詳見完整包。
Node.js 18+

主線哪幾關用到它

Skill 是一把武器，配合新手主線實操，打通從「會玩」到「精通」的打怪升級全流程。

2-3 · 出问题了怎么办 →

帶著這次成果繼續: 把 skill 串成流程 →

✓ 適合誰 (Good Fit)
  • 沿主線動手學習的 AI 新手
  • 從對應關卡開始；頁面瀏覽不會被當成任務完成。
⊗ 不適合誰 (Not For)
  • 超出本次任務的無人值守操作或未核准的帳號存取
✦ 你會得到 (What You Get)
  • 掌握除錯三板斧，不再一出错就重开對話
  • agent 先给出至少两个假设再动手
  • 修复后跑了验证并展示结果

交付內容：完整 SKILL.md 規則文件 + 公開自測樣例。需要在你自己的 AI Agent 中運行。

怎麼開始？

Skill 是一份教 AI 完成任務的規則。

領取並安裝 ↑
1
提供手上的材料
故意制造一个错误（比如让程式碼引用不存在的檔案），引导 agent 定位并修复。
2
讓 Agent 按規則完成
掌握除錯三板斧，不再一出错就重开對話
3
打開並核對真實產出
agent 先给出至少两个假设再动手
發給你的 AI Agent

用 debugging 帶我完成這一關。缺少材料先問我，實際使用工具並儲存結果，再按關卡判據核對。

使用前了解 證據會標明實測範圍；模型與權限依你的 Agent 而異。解壓成功不等於已被 Agent 自動發現。 Agent／模型費用依供應商而定；額外服務與依賴詳見完整包。

從這裡開始使用

压缩包里是规则、参考库、脚本、真实产出和演示片，不只是一个提示词文件。

下載完整包（.zip） 下載 SKILL.md
  1. 打開 Codex 或 Claude Code，粘貼安裝提示詞。
  2. 讓 Agent 讀取並保存完整規則，確認安裝成功。
  3. 複製上方使用示例，換成你的素材開始運行。
手動安裝 · 查看完整 SKILL.md（54 行）

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)

有疑惑？先看看這裡，買前明明白白，用時順順利利。

怎麼開始？ +
下載完整 ZIP，把安裝提示交給 Agent，保留腳本與參考檔案。模型費用另計。
主線 Skill 免費嗎？ +
這些基礎主線 Skill 免費；進階工作室商品沿用各自定價。
菜鸟skill 會員

讓每一種重複，
都有解法。

一個訂閱，解鎖全部工作室 Skills。只需要這一款？也可以單獨獲取。

比較完整方案
免費 出问题了怎么办
免費獲取