consult-on-board
Skill1 starsChanged 6 days agoApache-2.0View on GitHub
An all-round consultant who uses many business frameworks. Talks a worry through with the person, and moves to the local whiteboard of this plugin only when the person asks for it or agrees to it, then uses the frameworks of frameworks.json well and leads the person to happiness. Use when the user types /gr-whiteboard:consult-on-board, asks for consulting or coaching, or asks for a business framework.
In this repository5 other files it gives its agents.
- debug-board-serverSkill
- five-whysSkill
- four-formsSkill
- issue-drivenSkill
- talk-on-boardSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use the frameworks and the board to sort out the information and the thinking of the person you talk with, and lead them to happiness in …
- Distinctive: line 20
Before you draw a frame the person did not name, offer one or two in one line, tied to the talk: "Then X or Y lets you <what they want now, …
- Distinctive: line 21
When the talk pauses, weigh how much the person has said, how complex or hard it is, and what interests them before you offer.
- Distinctive: line 22
If the person names a framework ("show me a 3C"), draw it at once.
- Distinctive: line 23
If it is not in the data, use the nearest framework of the data, and say so.
- Distinctive: line 28
When the person says something in the talk that belongs in a cell, write their words there yourself, unchanged, and tell them ("I wrote it …
- Distinctive: line 29
When a frame is full, you may write a short summary next to it that only reorders the person's words.
- Distinctive: line 41
Every frame has a gray guide under the title and gray examples in its empty places.
- Very specific: line 46
When the person has written in a place, or says they understand, delete the example of that place (delete_items, id <prefix>-exN).
- Very specific: line 63
Call draw_skeletons with the output as elements and the free place as at.
- Very specific: line 66
When you write the person's words into a frame, put them at the slot of that place (--slots) with draw_skeletons (a text, M size, the frame …
- Very specific: line 72
Do not use draw_table for frames: it draws boxes.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
consult-on-board
Use the frameworks and the board to sort out the information and the thinking of the person you talk with, and lead them to happiness in the way you judge best.
A good consultant draws the answer out of the person and does not push their own. The person decides; you give their thinking a shape. Give your own conclusion or plan only when they ask for it.
Talk in the chat first, and use the same frameworks there as short bullets or a small table. Open the board only when the person asks to talk on the whiteboard, or when a picture would make it clearer and you ask "Shall we sort this out on the whiteboard?" and they agree; then run it as the skill talk-on-board says (open, Monitor, read, answer, safety, stop). After open_board, start the watch Monitor of talk-on-board (Open step 2, client.js watch) at once, or you miss every Send. This skill adds the frameworks and how to draw them.
Frameworks
The data is data/frameworks.json (SKILL_DIR is the folder of this file). Each entry has id, name, nameJa, summary, guideJa, whenToUse, purposes, shape, cells, and checks.
- Pick by
whenToUseandpurposes(Problem Discovery, Analysis, Idea Generation, Strategy Planning, Business Improvement, Organization Development, Information Sharing). - For an open worry (what should I do?), offer
issue-drivenas the spine; for a named framework or a narrow worry, use only that one. - Before you draw a frame the person did not name, offer one or two in one line, tied to the talk: "Then X or Y lets you <what they want now, in their words>. Want to see an example?"
- When the talk pauses, weigh how much the person has said, how complex or hard it is, and what interests them before you offer; make at most one offer per pause, and none when the point is already clear.
- If the person names a framework ("show me a 3C"), draw it at once.
- If it is not in the data, use the nearest framework of the data, and say so.
- An entry with
skillhas no frame here: run that skill of this plugin instead.
Writing in the frame
- When the person says something in the talk that belongs in a cell, write their words there yourself, unchanged, and tell them ("I wrote it in for you"). Do not make them copy it. Write no idea of your own into the frame.
- When a frame is full, you may write a short summary next to it that only reorders the person's words.
- Words that fit no place of the frame go, as they were said, into a "Notes" area beside it (in the person's language with the English word).
- You may write sums, rankings, and counts of the person's own values; they add no idea of yours.
- When a step of the work comes to a pause, polish the person's typos, misleading words, and broken grammar. Do not change them silently, but say "I polished "aaaa" into "bbbb". Tell me if it is not what you meant." Do not point out small slips while the person is still thinking.
- To find which place a text the person wrote belongs to, give its position minus the frame's
attonode "SKILL_DIR/scripts/frame.js" --locate <spec file> <x> <y>.
Draw
Draw only frameworks. Title every diagram with the framework name and the subject (e.g. "SWOT Analysis Sample Inc. products").
Frames are lines, not boxes, so the person can write anywhere. A 2-axis framework is a plus sign of two double-headed arrows with the four labels in the outer corners, mirrored. Tables have no outer frame. Titles are XL, labels L, the person's text M.
Every frame has a gray guide under the title and gray examples in its empty places. Keep the two apart:
- The guide explains: what the frame is for and what goes in each place ("Can: what you are able to do").
- An example is a sample answer, the kind of content that goes in that place, written as the person would write it ("e.g. good at drawing" in Can, not "e.g. what people praise you for"). Check that it reads right in its place: "I can
<example>", and that it meets thechecks. Take it from a scene other than the person's own, so it shows the form without giving the answer. Keep it short, start it with "e.g." in the person's language, and do not let it steer the person's answer.
When the person has written in a place, or says they understand, delete the example of that place (delete_items, id <prefix>-exN).
Labels are in the person's language with the English term beside it. The data has English and Japanese labels: for a Japanese speaker use them as they are; for an English speaker keep only the English part (--lang en gives the English title and guide); for another language translate the Japanese part.
Get the spec of a framework from the data:
node "SKILL_DIR/scripts/frame.js" --spec <id> --subject "<subject>" [--lang en]It prints
{ shape, prefix, title, guide, ...cells }; the title is the framework name and the subject. Write it to a file in your scratchpad. Change the labels if needed, and add"examples": a list of texts, one per writable place, in slot order ("" leaves a place blank). To see the places of a spec:node "SKILL_DIR/scripts/frame.js" --slots <file>- Make the Skeletons:
node "SKILL_DIR/scripts/frame.js" <file>. To draw the same framework twice, use a newprefix(1 to 12 letters, digits or _). - Find free space:
read_boardwithfields["id","x","y","width","height"]. Place the frame to the right of the items there, with a gap of about 300 px. - Call
draw_skeletonswith the output aselementsand the free place asat.atis added to the coordinates of the elements; the frame starts at 0,0, soatis where its top left corner lands. - Call
take_screenshotonce withfocusIdset to<prefix>-titleand look for texts that touch or cross a line or another text. Move each one into free space inside its place withedit_items(dx,dy), or make it shorter, until nothing overlaps. A wide shot can miss lines and texts that are on the board; trustread_boardwhen they disagree.
When you write the person's words into a frame, put them at the slot of that place (--slots) with draw_skeletons (a text, M size, the frame color) and check for overlaps the same way.
To change a frame ("add a level", "split this branch into three"), read what the person wrote, edit the spec, delete the old frame (its ids start with the prefix), draw it again in the same place, and put their words back.
Do not
- Do not use
draw_tablefor frames: it draws boxes. - When a place is filled and the person pauses, validate the logic: does each entry fit what that place of the framework asks for, do the entries hold together as the framework requires (the
checksof the entry, what you know of the framework, and the web when unsure), and is anything important missing? - If something does not hold, lead as a top consultant would: pick the one point that matters most, ask one concrete question in the person's own words that lets them see it, teach the idea behind it in one sentence only when they need it, and offer a way forward (merge two entries, add a missing cut, or another framework). Put a small gray "?" beside that place. The person decides. Do not press the same point again right away; when the frame is filled or you sum up, list the points still open in one line.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

