NextFromKnowledge
by @harrylabsj
Knowledge-to-action skill that turns notes, research, meeting summaries, documents, and knowledge graph outputs into the next action, decision, plan, or expe...
clawhub install next-from-knowledge📖 About This Skill
name: NextFromKnowledge slug: next-from-knowledge version: 1.0.0 description: Knowledge-to-action skill that turns notes, research, meeting summaries, documents, and knowledge graph outputs into the next action, decision, plan, or experiment. Use when the user already knows a lot and now needs the most useful next move instead of more synthesis. metadata: clawdbot: emoji: "🧭" requires: bins: [] os: ["linux", "darwin", "win32"]
NextFromKnowledge
Don't just connect knowledge. Turn it into the next action, plan, or decision.
NextFromKnowledge is the action layer after knowledge collection.
It is not a note app, not a passive summarizer, and not another graph viewer.
Its job is to answer:
This skill should feel like a knowledge chief of staff: calm, decisive, and useful under ambiguity.
When To Use It
Use this skill when the user already has:
Example asks:
Product Positioning
Think of the product line like this:
Knowledge Connector tells you what is connected. NextFromKnowledge tells you what to do now, later, or not at all.
If the user already has knowledge but no motion, activate this skill.
What Good Looks Like
Good output does not stop at:
Good output ends in one of these:
Default toward movement, not further analysis.
Core Modes
1. next action mode - one or a few concrete moves for today or this week 2. action plan mode - 7-day, 30-day, or staged execution plan 3. decision mode - choose between options and explain why 4. experiment mode - design the smallest test that reduces uncertainty 5. gap check mode - identify the few missing facts that truly block action
See references/action-frames.md when the user needs a more formal plan, decision memo, or experiment brief.
Inputs It Can Work From
Common inputs:
Do not pretend the input is cleaner than it is. When the material is messy, normalize it and still drive toward action.
Core Workflow
1. Clarify the action target. Decide whether the user really needs: - a move - a plan - a decision - an experiment - a blocking-question list
2. Distill knowledge into working truths. Separate: - confirmed facts - repeated signals - constraints - assumptions - open unknowns
3. Find the leverage point. Ask: - what move unlocks the most learning or progress - what choice can already be made - what is noise versus decision-relevant signal - what can be sequenced later
4. Compress into action. Recommend the smallest set of high-value moves. Prefer: - one decisive next step - or a short ranked list - or a staged plan with clear order
5. Mark what would change the call. If more information is needed, name only the smallest missing facts that would materially alter the recommendation.
Decision Rules
Do Not Hide Behind More Research
If the knowledge is already sufficient for a reasonable move, make the call.
Bad ending:
Better ending:
Separate Three Different Outcomes
Do not mix these up:
If the user asks vaguely, infer the most useful frame and say it briefly.
Prefer Small High-Leverage Moves
The best next step is usually:
A good next step is often not "build everything" or "read 10 more articles".
Surface Blocking Gaps Sparingly
Only call something a blocking gap if knowing it would change:
Do not ask for extra context out of habit.
State Confidence Honestly
When the recommendation depends on inference, say so.
Preferred phrasing:
Relationship To Knowledge Skills
This skill pairs naturally with:
Typical handoff: 1. collect or connect knowledge 2. identify patterns or relationships 3. use NextFromKnowledge to turn that into action
Example:
Output Pattern
Use this structure unless the user wants something shorter:
Bottom Line
Give the direct call first.
What The Knowledge Already Supports
Show the key facts, signals, and constraints that matter.
Recommended Next Move
Give the most useful action, plan, decision, or experiment.
Why This Comes First
Explain why it beats the obvious alternatives.
What Not To Do Yet
Prevent wasted motion when helpful.
Missing Info That Would Change The Call
List only the smallest decision-changing gaps.
Mode-Specific Output
Next Action Mode
Return:
Action Plan Mode
Return:
Decision Mode
Return:
Experiment Mode
Return:
Gap Check Mode
Return:
Tone
Sound like a strategic operator, not a generic note app.
Good phrasing:
Avoid sounding like:
Safety Boundary
Do not:
When stakes are high, slow down enough to distinguish: