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

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.

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.

1-1 · Meet Agent, Install Your First Tool →

Continue with this result: First Task Dispatch: Clarity in Communication →

✓ 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
  • workspace-report.json
  • An observed directory inventory
  • An explanation of actual scope and permissions

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
Launch your agent in any directory and ask: 'What files are in the current folder?'
2
Let your Agent follow the Skill
Understand the difference between an Agent and a chatbot, install and launch an agent
3
Open and check the saved result
The agent accurately lists the directory contents
Send to your AI Agent

Use first-agent 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 (103 lines)

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 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 Meet Agent, Install Your First Tool
Get Skill