---
name: daily-three
description: Help a beginner finish two or three genuinely useful small tasks using installed Skills, inspect each saved result and keep an evidence-backed task journal without pretending files were published or used by the learner.
---

# Use Skills on real small tasks

This is level 1-4 of the newbieskill main quest.
Move from trying an example to choosing tasks the learner actually needs to finish.

## Result

- Two or three usable saved results from at least two different Skills.
- A short task journal connecting the original need, chosen Skill, result and checks.
- A clear next task based on what the learner just made.

## Choose small, real tasks

Ask what the learner needs to finish today if the conversation contains no concrete needs.
Offer a short menu grounded in installed capabilities, such as checking a project folder, revising a note or drafting a weekly report.
Let the learner choose; do not turn a small task into a complex workbench.
Prefer a result they can inspect and use immediately.

Start with two tasks. Add a third only when the learner has a useful reason.
Public examples demonstrate the method; they do not substitute for the learner's own material.

## Check the selected Skills

Read the actual installed rules and identify their required inputs and dependencies.
Check whether their supporting files are present.
Do not infer that a catalog page or a saved screenshot is a complete, tested installation.
If a dependency needs another account or fee, explain it before running that task.
Choose an already available alternative when it serves the learner's need.

## Execute one task at a time

1. State a small result and one or two checks in the learner's words.
2. Collect the actual input or ask one focused clarification.
3. Invoke the selected installed Skill and use real tools where the task requires them.
4. Save a named output; keep the original input and existing files intact.
5. Open or read the saved result. Check facts, content and usability against the input.
6. Record what passed, what needs another step and whether the learner has actually used the result.

Do not say the second task ran merely because the first task completed.
If one task fails, keep the successful result and identify the failed task's blocker.

## Keep a useful journal

For each task record `title`, `skill`, `output` and a short `check` explanation.
Use output paths relative to an explicitly selected base directory.
Set `used` to `true` only after the learner confirms use, or when an actual local follow-on operation consumed the result.
Record that use in `usedFor`; “file exists” is not enough.

The read-only helper checks the journal's files and produces hashes:

```text
node scripts/check-journal.mjs <journal.json> <selected-base-directory>
```

The helper verifies distinct tasks, distinct saved files, at least two Skills, file existence and a use/check record.
It cannot establish the truth of a learner's claim or the quality of a document by hashing it.
The Agent must still inspect the content and explain the result.

## Handle missing or incomplete material

- No real task: ask what the learner needs to hand in, send or save today.
- No inputs: request the minimum missing material, not a biography or a complete project archive.
- One complete task only: save it and help finish a second useful task.
- Result not used yet: say “ready to review/use”; do not mark actual use as verified.
- Sending/publishing requires separate authorization; local creation is not permission to send it.

## Self-test tasks

1. Trace three actual local production results to their source Skills and their real follow-on uses; verify the saved file hashes.
2. Build a different two-task journal and check that the minimum useful session passes without inventing a third task.
3. Submit an empty journal and a journal naming a nonexistent output; both must fail without creating those outputs.

Any fabricated execution, unobserved publication, missing file or repeated file counted as two tasks fails acceptance.
An artifact check is not a new Agent run. Record the scope in the evidence.

## Continue the main quest

Return: `/path/daily-three/`.
Next: `/path/prompt-spec/` — give your next task clear acceptance criteria before running it.
Branches can include reports, notes, presentations and publishing formats when the learner's actual task needs them.

## Rights

Original newbieskill workflow. Personal and commercial work is permitted; do not resell the complete package.