graph-ask-demo
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
TEST FIXTURE (not a user skill): reads CPU and memory in parallel, then asks before saving. It exists because it is the only thing that reproduces the graph_ask path end to end — a fan, a join, and a human node. Safe to run; safe to delete if the ask path ever gets a fixture home of its own.
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- board-workerSkill
- board-triage-specifierSkill
- create-a-skillSkill
- execdesk-action-board-prepSkill
- execdesk-action-competitor-monitorSkill
- execdesk-action-competitor-positioningSkill
- execdesk-action-content-calendarSkill
- execdesk-action-decision-frameworkSkill
- execdesk-action-growth-hack-runnerSkill
- execdesk-action-icp-profileSkill
- execdesk-action-quarterly-goals-reviewSkill
- execdesk-action-twitter-thread-drafterSkill
- execdesk-action-weekly-briefSkill
- execdesk-ceoSkill
- execdesk-chief-of-staffSkill
- execdesk-cmoSkill
- think-deepSkill
- docker-compose-devSkill
- calendar-hold-approvalSkill
- chuck-norrisSkill
- email-send-approvalSkill
- inbox-and-agendaSkill
- meeting-brief-graphSkill
- multi-mcp-testSkill
- schedule-badge-proofSkill
- stopping-point-testSkill
- turn-log-smokeSkill
- code-review-templateSkill
- custom-skill-templateSkill
- daily-research-briefSkill
- pr-review-pipelineSkill
- research-analysis-templateSkill
- ship-a-featureSkill
- autonomous-planSkill
- browser-toolsSkill
- code-reviewSkill
- deep-thinkingSkill
- first-skillSkill
- helloSkill
- implementation-planningSkill
- install-mcp-serverSkill
- masterySkill
- mcp-builderSkill
- mcp-installerSkill
- morning-briefSkill
- new-user-walkthroughSkill
- oauth-authenticationSkill
- onboardingSkill
- parallel-code-analysisSkill
- project-wizardSkill
- qa-reportSkill
- qa-testingSkill
- regression-testSkill
- self-improveSkill
- self-learningSkill
- skill-developmentSkill
- social-media-marketingSkill
- soulSkill
- The first 60 shown.
The file
Files
Graph ask demo
This is a test fixture living in the skills tree. It is a real, triggerable skill (
graph ask demo), kept because it is the only thing that reproduces theask me:path end to end against a real run record. It reads CPU and memory and writes nothing. If the ask path gets a proper fixture home, delete this.
Two harmless probes run together, a join needs 1 of 2, then it stops and asks.
This exists so the ask me: path can be tested against a real run record rather
than a synthetic event.
Shape
together probes:
cpu: mcp-monitor.get_cpu_info {}
mem: mcp-monitor.get_memory_info {}
then:
need: 1 of 2
brief: write one short line about the machine from {cpu, mem}
ask me:
save this reading?<!-- AGENT_ACTIONS: {"initial_steps":[{"args":{},"id":"cpu","on_fail":"skip","parallel_group":"probes","server":"mcp-monitor","tool":"get_cpu_info"},{"args":{},"id":"mem","on_fail":"skip","parallel_group":"probes","server":"mcp-monitor","tool":"get_memory_info"},{"id":"join_probes","in":["cpu","mem"],"kind":"join","min_success":1,"mode":"all_settled","on_partial":"continue_with_warning"},{"depends_on":["join_probes"],"id":"brief","prompt":"write one short line about the machine from {cpu, mem}"}],"schema_version":"1.1","stopping_points":[{"id":1,"options":{"1":{"label":"Yes","steps":[],"vars":{}},"2":{"label":"No","steps":[],"vars":{}}},"title":"save this reading?","type":"menu"}]} -->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.

