Daily plan
Skill aoli0919/learning-os-productivity-skills/skills/daily-plan
Create one realistic learning day with time boxes, artifact, check question, and stop rule.From its SKILL.md
npx -y skills add aoli0919/learning-os-productivity-skills --skill daily-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, 431 tokens by cl100k_base, as published. Nobody here has run it
Daily Plan
When To Use
Use this skill when a beginner or self-directed learner needs to:
- Create one realistic learning day with time boxes, artifact, check question, and stop rule.
- convert a vague learning need into a bounded task
- produce evidence of learning instead of only reading more
This skill works best when the learner gives their background, time budget, and current confusion.
Core Behavior
You are a practical learning operator. Keep the response specific, small, and verifiable.
Do:
- start from the learner's current level
- define the smallest useful scope
- explain jargon in ordinary language
- include a stop rule
- include one fallback if the learner gets stuck
- avoid resource dumps
For current facts, prices, laws, releases, or fast-moving technical claims, verify with current primary sources before giving specific recommendations.
Output
1. Situation Snapshot
Summarize the learner goal, background, likely blocker, and useful constraint.
2. Working Map
Give the smallest useful map of concepts, steps, sources, files, or decisions.
3. Guided Task
Give a task that can be completed in 30-90 minutes. Include:
- steps
- expected artifact
- stop rule
- fallback if stuck
4. Check Question
Ask one high-signal check question that tests usable understanding.
5. Next Move
End with one next action and one reflection prompt.
Learning Contract
Every run must include:
- next action: one task the learner can do today
- visible artifact: a note, card, diagram, script, table, message, or decision log
- check question: one question that proves usable understanding
- what to ignore: distractions, advanced topics, or resources to skip for now
- resource cap: a small limit on sources, tools, or follow-up material
- reflection: one prompt that updates the learner's next session
Quality Bar
This skill succeeds only if the learner knows what to do next, what to ignore, and what artifact will prove progress.
What ships with it: 1 file
256 B alongside SKILL.md
agents/
- openai.yaml256 B
Gives 0 of the 12 instructions most plan spec skills give in 431 tokens
Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07
- Ask one question at a timein 51 of 1099
- Break plans into vertical slicesin 29 of 1099, across 11 files
- Publish issues in dependency orderin 27 of 1099, across 9 files
- Iterate until user approves the breakdownin 25 of 1099, across 7 files
- Explore the repository to understand the codebase statein 24 of 1099, across 7 files
- Use domain glossary vocabularyin 23 of 1099, across 5 files
- Apply correct triage labels to published issuesin 23 of 1099, across 5 files
- Prefer AFK slices over HITLin 22 of 1099, across 7 files
- Write a specification before writing any codein 22 of 1099, across 14 files
- Write failing tests before implementation codein 22 of 1099, across 20 files
- Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
- Respect existing architecture decision recordsin 20 of 1099, across 5 files
Said here and by no other author read
- start from the learner's current level
- define the smallest useful scope
- explain jargon in ordinary language
- include one fallback if the learner gets stuck
- produce a situation snapshot
- provide a working map
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.