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

Workspace inspection: actual saved output

The Agent ran scripts/inspect-workspace.mjs on the public inputs/example/ folder.

Observed nameType
brief.mdfile
notes.txtfile

Scope: direct children only. File contents were not opened. No hidden, sensitive or linked items were present in this particular two-file input.

The report was saved to demo/output/agent-workspace-report.json and subsequently used by the preview and motion walkthrough. Separate fresh-script cases check filtering, a different Unicode input, missing material and refusal to overwrite an existing report.

This result describes an observed operation, not a promise that the Agent is restricted to this folder or automatically discovers every Skill.

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

主線哪幾關用到它

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

1-1 · 認識 Agent，裝好第一个工具 →

帶著這次成果繼續: 第一次派工：会說話就会用 →

✓ 適合誰 (Good Fit)
  • 沿主線動手學習的 AI 新手
  • 從對應關卡開始；頁面瀏覽不會被當成任務完成。
⊗ 不適合誰 (Not For)
  • 超出本次任務的無人值守操作或未核准的帳號存取
✦ 你會得到 (What You Get)
  • 理解 agent 和聊天机器人的区别，裝好并启动一个 agent
  • agent 正确列出了目錄内容
  • 你能区分本次实际读取的檔案夹与 Agent 获得的访问权限

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

怎麼開始？

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

領取並安裝 ↑
1
提供手上的材料
在任意檔案夹启动 agent，问它：「当前目錄里有什么檔案？」
2
讓 Agent 按規則完成
理解 agent 和聊天机器人的区别，裝好并启动一个 agent
3
打開並核對真實產出
agent 正确列出了目錄内容
發給你的 AI Agent

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

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

從這裡開始使用

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

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

Codex：~/.agents/skills/first-agent/SKILL.md
Claude Code：~/.claude/skills/first-agent/SKILL.md

--- name: first-agent description: Help an AI beginner complete their first real file inspection in an explicitly selected workspace, distinguish tool evidence from chat, and save a verifiable directory report. Use for the first level of the newbieskill learning path. --- # Meet your Agent: your first real action Turn “can this AI actually see my project?” into an answer backed by a real tool call. This is level 1 of the newbieskill main quest, not a general installation or system administration tool. ## What the learner receives - A list of the visible items directly inside the selected folder. - `workspace-report.json`, a machine-readable inventory of that folder. - A plain-language explanation of what was inspected, what was skipped, and what has not been tested. - The next task: create and revise a small file with `first-task`. ## Start from the learner's situation If no Agent is installed, direct the learner to the installation instructions on the learning page. Ask them to complete account login and open a folder in the Agent before continuing. Do not invent installation success or assume access to their desktop from an ordinary chat window. If they already opened an Agent in a folder, use that folder instead of repeating setup. ## The only required input An explicitly selected working folder is sufficient. Ask “Which folder should I inspect?” if the current workspace is unknown. Do not request an API key, email address, or the contents of private documents. Do not change the user's Agent settings or install another tool to complete this lesson. ## Workflow 1. Identify the current workspace with an available file or shell tool. 2. Tell the learner the folder you will inspect. Resolve an ambiguous path before continuing. 3. Read `references/inspection-boundaries.md` when deciding what may appear in the report. 4. Run the bundled script using Node.js 18 or newer: ```text node <installed-skill-directory>/scripts/inspect-workspace.mjs <selected-folder> <report-file> ``` 5. Put the report in a task output folder chosen by the learner, outside the folder being listed when practical. 6. Read the actual generated JSON. Summarize its items and skipped-item counts without pretending to have opened their contents. 7. Explain that this run inspected one selected folder, not the whole computer. Other locations require their own access and authorization. 8. Give the actual report path and continue to the next lesson if the learner wants to create a file. Paths containing spaces must be passed as separate, correctly quoted command arguments. Resolve the script relative to this installed Skill, not relative to the learner's project. If Node.js is unavailable, use the Agent's existing directory-listing tool and save the same report fields. Clearly identify that alternative; do not say the bundled script ran. ## Read the result correctly `items` contains names and types observed in this run. `skipped` reports hidden files, sensitive filenames and symbolic links without exposing their names. `scope` is always `direct-children-only`; nested folders have not been recursively inspected. An empty `items` array can be a correct result for an empty folder. The report does not prove the Agent can edit files, run every command, or access other folders. Those are separate tasks with separate evidence. ## Failure and recovery - Missing folder: explain the failed path and ask for a real folder; do not create it silently. - File supplied instead of a folder: ask for its containing folder. - Permission denied: ask for a folder already accessible to the Agent; do not elevate permissions automatically. - Existing report destination: choose a new filename or ask before replacing it; the script refuses overwrite. - Tool unavailable: explain what is missing and stop before claiming an inventory. - Only hidden or sensitive items: explain the omission policy, not “the directory contains no files”. ## Quality boundaries - Never infer a folder listing from the conversation or an example. - Never open `.env`, credentials, browser profiles or private documents for this lesson. - Do not follow symbolic links or recurse outside the selected folder. - Do not scan a home directory or a whole drive merely to find an example project. - Preserve all existing files. This lesson's sole write is its explicitly named new report. - Distinguish what a tool actually did from what the Agent might be able to do later. - Explain the result in familiar words; do not require the learner to understand JSON. ## Self-tests and failure criteria Run `node scripts/self-test.mjs` from this package. It executes the inspection script against fresh temporary folders rather than rechecking a saved report. 1. Normal material: two visible files and one folder produce exactly three named items; hidden and sensitive files are omitted. 2. Different material: a Unicode filename and an empty directory retain their exact names; counts match independently observed contents. 3. Missing material: a nonexistent folder fails, produces no report and explains the missing-folder error. 4. Existing output: a second write to the same destination fails and preserves the original bytes. Any mismatch, unexpected write, missing error or invented item is a failure. Keep outputs, executable commands and results in `demo/`; a test pass establishes these cases only. ## Learning route Main quest: `/path/first-agent/`. Next: `/path/first-task/` — create a file, then make a precise change in the same conversation. This Skill can also support later project-context and troubleshooting tasks. ## Rights Original newbieskill workflow and scripts. See `LICENSE` for reuse terms.

新手常問 (FAQ)

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

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

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

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

比較完整方案
免費 認識 Agent，裝好第一个工具
免費獲取