[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQN2BA49P4WJY08DCX7BAH":3,"skill-same:01M7CQN2BA49P4WJY08DCX7BAH":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CQN2BA49P4WJY08DCX7BAH","loom-interactive-diagram",null,"Create and check editable diagrams during standalone or Loom work. Use when the agent needs to create a diagram for the user to edit in an external editor or read back saved changes; draw.io is the default format.","kouko\u002Floom-plugins","kouko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1480254?v=4","01M7CQCPAJR9C92XDGR0QDCQ98","01M7CQCPB8FTVY1BT26ENK1YP4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loom-interactive-diagram\ndescription: |\n  Create and check editable diagrams during standalone or Loom work. Use when the agent needs to create a diagram for the user to edit in an external editor or read back saved changes; draw.io is the default format.\nversion: 1.0.0\n---\n\n# Shared editable diagrams\n\nUse this tool when a diagram should be editable by the user during a\ndiscussion, with or without an active Loom change. The conversation carries\nthe file path and a text projection; the user opens the file in an editor.\n\nOutside Loom, ask where to save a new diagram and use an explicit directory:\n`new example --output-dir \u003Cproject-dir>`. This creates `example.drawio` and\n`example.projection.md` there. Do not infer a destination from the current\ndirectory. A direct command without a destination reports an error.\n\nFor Loom work, start from `docs\u002Floom\u002F\u003Cchange-id>\u002F`. If starting at the\nrepository root, create the diagram with `new \u003Cname> --change-id \u003Cchange-id>`\n(or `new \u003Cbackend-id> \u003Cname> --change-id \u003Cchange-id>`), then run\n`cd docs\u002Floom\u002F\u003Cchange-id>\u002F` before using any relative diagram path. The id must\nname an existing `docs\u002Floom\u002Fintent\u002F\u003Cchange-id>.md`; an explicit id inside a\nchange directory must match that directory. Generated files go to\n`docs\u002Floom\u002F\u003Cchange-id>\u002Fdiagrams\u002F`. Run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py`\nwith one of these commands:\n\n- `list-backends`: show available formats.\n- `new \u003Cname>`: create an empty draw.io diagram and matching projection.\n- `new \u003Cbackend-id> \u003Cname>`: create one with a selected format.\n- `new \u003Cname> --output-dir \u003Cproject-dir>`: create a standalone diagram and\n  projection at the explicitly selected directory.\n- `copy \u003Csource> --change-id \u003Cchange-id>`: copy an existing diagram into the\n  selected Loom change, with a new projection beside the copy. From its change\n  directory, omit `--change-id`. Outside Loom, use\n  `copy \u003Csource> --output-dir \u003Cproject-dir>` after the user names that project\n  directory. Never overwrite an existing diagram or projection.\n- `project [diagrams\u002F\u003Cname>.\u003Cext>]`: regenerate a managed\n  projection after an edit. The path must stay inside the selected change's\n  `diagrams\u002F` directory, including after resolving symlinks.\n- `project \u003Cdiagram-path> --in-place`: for a standalone diagram or after the\n  user chooses direct editing, regenerate the adjacent projection. A missing\n  projection is created for a registered diagram format. Symlinked diagram\n  and projection paths are rejected; ask for the resolved original path.\n- `check [\u003Cdiagram-path>]`: validate one diagram or every registered diagram\n  under `diagrams\u002F` and every diagram linked from `spec.md`; return nonzero\n  and name each invalid file or difference. Spec links resolve from `spec.md`.\n  Read-only checks of named external diagrams remain supported. Outside Loom,\n  pass the selected diagram path explicitly.\n\nBefore each external edit, ask the user whether to copy the diagram into the\nproject; show the resolved source path and the proposed destination. Wait for\nthe answer before copying or editing. Ask on every new edit request, even if\nthe user has previously selected direct editing, and do not act on silence.\nIf the user chooses a copy during Loom work, put it in\n`docs\u002Floom\u002F\u003Cchange-id>\u002Fdiagrams\u002F` and tell them that actual path. Outside\nLoom, ask for the project directory if it is unknown, then use `--output-dir`.\nIf the user chooses the original, use its resolved path and `--in-place` after\nthe edit; the original and its adjacent projection may change, and no backup\nis made. A read-only check does not trigger the copy question.\n\nThe default backend is `drawio`. A backend is one file in `backends\u002F`; the\nselection is recorded in the projection header. See `references\u002Fbackends.md`\nfor the callable contract and `references\u002Fprojection.md` for the text format.\n\nFor a Loom copy or new diagram, run the watcher and follow-up commands from\n`docs\u002Floom\u002F\u003Cchange-id>\u002F`. For standalone or direct external editing, use the\nselected diagram's path instead. When the user is editing during the current\nconversation turn, tell them which diagram you are waiting for and keep the\nturn active. After your last write,\nrun `python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fwait_for_save.py\n\u003Cdiagram-path> --timeout 120` in a live tool session that yields output\nwhile the process keeps running; retain its session identifier. Wait for\n`READY`, then tell the user they can edit and save that diagram. Continue\npolling that same tool session during this turn for `CHANGED`, `TIMEOUT`, or\n`ERROR`. `READY` means the content baseline was read. `CHANGED` means that\nsame file has held changed content across two reads; it does not identify who\nor what wrote it. Read the file, run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py\nproject \u003Cdiagram-path>` for a managed diagram or `project \u003Cdiagram-path>\n--in-place` for a standalone diagram or explicitly selected original. Run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py\ncheck` to validate all managed diagrams, or `check \u003Cdiagram-path>` for a\nstandalone or external original. Restate the visible edit. On `TIMEOUT`, say that no\nchanged save was observed and the user can still send a message to continue.\nOn `ERROR`, name the file and ask the user to save it again. Unrelated file\nchanges and identical-content saves do not end the wait. The watcher cannot\nresume a turn after it has ended.\n\nFor edits outside an active wait, read the saved file and follow the same\n`project` then `check` procedure.\nFor VS Code and desktop setup and the acceptance procedure, follow\n`references\u002Feditor-setup.md`. Do not claim live synchronization from a static\nfile check.\n","# Shared editable diagrams\n\nUse this tool when a diagram should be editable by the user during a\ndiscussion, with or without an active Loom change. The conversation carries\nthe file path and a text projection; the user opens the file in an editor.\n\nOutside Loom, ask where to save a new diagram and use an explicit directory:\n`new example --output-dir \u003Cproject-dir>`. This creates `example.drawio` and\n`example.projection.md` there. Do not infer a destination from the current\ndirectory. A direct command without a destination reports an error.\n\nFor Loom work, start from `docs\u002Floom\u002F\u003Cchange-id>\u002F`. If starting at the\nrepository root, create the diagram with `new \u003Cname> --change-id \u003Cchange-id>`\n(or `new \u003Cbackend-id> \u003Cname> --change-id \u003Cchange-id>`), then run\n`cd docs\u002Floom\u002F\u003Cchange-id>\u002F` before using any relative diagram path. The id must\nname an existing `docs\u002Floom\u002Fintent\u002F\u003Cchange-id>.md`; an explicit id inside a\nchange directory must match that directory. Generated files go to\n`docs\u002Floom\u002F\u003Cchange-id>\u002Fdiagrams\u002F`. Run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py`\nwith one of these commands:\n\n- `list-backends`: show available formats.\n- `new \u003Cname>`: create an empty draw.io diagram and matching projection.\n- `new \u003Cbackend-id> \u003Cname>`: create one with a selected format.\n- `new \u003Cname> --output-dir \u003Cproject-dir>`: create a standalone diagram and\n  projection at the explicitly selected directory.\n- `copy \u003Csource> --change-id \u003Cchange-id>`: copy an existing diagram into the\n  selected Loom change, with a new projection beside the copy. From its change\n  directory, omit `--change-id`. Outside Loom, use\n  `copy \u003Csource> --output-dir \u003Cproject-dir>` after the user names that project\n  directory. Never overwrite an existing diagram or projection.\n- `project [diagrams\u002F\u003Cname>.\u003Cext>]`: regenerate a managed\n  projection after an edit. The path must stay inside the selected change's\n  `diagrams\u002F` directory, including after resolving symlinks.\n- `project \u003Cdiagram-path> --in-place`: for a standalone diagram or after the\n  user chooses direct editing, regenerate the adjacent projection. A missing\n  projection is created for a registered diagram format. Symlinked diagram\n  and projection paths are rejected; ask for the resolved original path.\n- `check [\u003Cdiagram-path>]`: validate one diagram or every registered diagram\n  under `diagrams\u002F` and every diagram linked from `spec.md`; return nonzero\n  and name each invalid file or difference. Spec links resolve from `spec.md`.\n  Read-only checks of named external diagrams remain supported. Outside Loom,\n  pass the selected diagram path explicitly.\n\nBefore each external edit, ask the user whether to copy the diagram into the\nproject; show the resolved source path and the proposed destination. Wait for\nthe answer before copying or editing. Ask on every new edit request, even if\nthe user has previously selected direct editing, and do not act on silence.\nIf the user chooses a copy during Loom work, put it in\n`docs\u002Floom\u002F\u003Cchange-id>\u002Fdiagrams\u002F` and tell them that actual path. Outside\nLoom, ask for the project directory if it is unknown, then use `--output-dir`.\nIf the user chooses the original, use its resolved path and `--in-place` after\nthe edit; the original and its adjacent projection may change, and no backup\nis made. A read-only check does not trigger the copy question.\n\nThe default backend is `drawio`. A backend is one file in `backends\u002F`; the\nselection is recorded in the projection header. See `references\u002Fbackends.md`\nfor the callable contract and `references\u002Fprojection.md` for the text format.\n\nFor a Loom copy or new diagram, run the watcher and follow-up commands from\n`docs\u002Floom\u002F\u003Cchange-id>\u002F`. For standalone or direct external editing, use the\nselected diagram's path instead. When the user is editing during the current\nconversation turn, tell them which diagram you are waiting for and keep the\nturn active. After your last write,\nrun `python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fwait_for_save.py\n\u003Cdiagram-path> --timeout 120` in a live tool session that yields output\nwhile the process keeps running; retain its session identifier. Wait for\n`READY`, then tell the user they can edit and save that diagram. Continue\npolling that same tool session during this turn for `CHANGED`, `TIMEOUT`, or\n`ERROR`. `READY` means the content baseline was read. `CHANGED` means that\nsame file has held changed content across two reads; it does not identify who\nor what wrote it. Read the file, run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py\nproject \u003Cdiagram-path>` for a managed diagram or `project \u003Cdiagram-path>\n--in-place` for a standalone diagram or explicitly selected original. Run\n`python3 \u003Cplugin-root>\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py\ncheck` to validate all managed diagrams, or `check \u003Cdiagram-path>` for a\nstandalone or external original. Restate the visible edit. On `TIMEOUT`, say that no\nchanged save was observed and the user can still send a message to continue.\nOn `ERROR`, name the file and ask the user to save it again. Unrelated file\nchanges and identical-content saves do not end the wait. The watcher cannot\nresume a turn after it has ended.\n\nFor edits outside an active wait, read the saved file and follow the same\n`project` then `check` procedure.\nFor VS Code and desktop setup and the acceptance procedure, follow\n`references\u002Feditor-setup.md`. Do not claim live synchronization from a static\nfile check.\n",{"name":5,"version":23,"description":24},"1.0.0","Create and check editable diagrams during standalone or Loom work. Use when the agent needs to create a diagram for the user to edit in an external editor or read back saved changes; draw.io is the default format.\n","main","3b1a9972644517911454530dc1876f88525b1f37","loom-workflow\u002Fskills\u002Floom-interactive-diagram","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins","https:\u002F\u002Fgithub.com\u002Fkouko","2026-11-15 00:45:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add kouko\u002Floom-plugins --skill loom-interactive-diagram",{"tool":37,"command":38},"bunx","bunx skills add kouko\u002Floom-plugins --skill loom-interactive-diagram",{"tool":40,"command":41},"pnpm","pnpm dlx skills add kouko\u002Floom-plugins --skill loom-interactive-diagram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002FSKILL.md",true,[45,51,55,61,65,69,73,77],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"backends\u002Fdemo_json.py","SCRIPT","脚本",1952,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Fbackends\u002Fdemo_json.py",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"backends\u002Fdrawio.py",3536,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Fbackends\u002Fdrawio.py",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"README.md","REFERENCE","参考文档",2124,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002FREADME.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fbackends.md",788,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Freferences\u002Fbackends.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Feditor-setup.md",4619,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Freferences\u002Feditor-setup.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fprojection.md",1736,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Freferences\u002Fprojection.md",{"path":74,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fdiagram.py",15014,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fdiagram.py",{"path":78,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fwait_for_save.py",1678,"https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-interactive-diagram\u002Fscripts\u002Fwait_for_save.py",[82,89,96,103,110,117],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CQNVD2W5MP7PKX3MD0YSQE","using-loom-workflow","Route broad Loom workflow-tool requests to the right skill. Use when the request spans tools or the right workflow skill is unclear.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fusing-loom-workflow\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7CQNNTPVG52CS2C6Q9HJ2E2","skill-retro","Review selected past or current Claude Code or Codex sessions against readable target skill sources and related integration. Produce source-linked proposals without applying changes.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fskill-retro\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7CQNHR1BDKJ63CC4R1RY9GE","recap-state","Give an in-session recap of current progress for 'where were we', '我們剛剛在幹嘛', '剛剛講到哪', '我跟丟了', 'ちょっと振り返って', '今どこだっけ', or '振り返り'. The built-in \u002Frecap is an away-summary.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Frecap-state\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7CQNE1A9272WPRE1MM3JRFK","project-retro","Review one current or specified coding session for source-backed project\ndevelopment improvements. Use for a requested retrospective, including\n振り返り seeking improvements; not for current-progress recaps or recurring skill mining.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Fproject-retro\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7CQNACJB36T0A039HT89P38","loom-visualization","Show comparisons, flows, decisions, states or reasoning chains as tables, ASCII or Mermaid in coding chat, including when a Loom station reports to the user (intent restatement, choices, acceptance test results); not Obsidian notes.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-visualization\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M7CQN7TVS0XF44JXQBWA32Z1","loom-memory","Record repo-wide lessons when saving to your own memory or asked to remember; recall, reconcile, or forget them when a task needs it.","https:\u002F\u002Fgithub.com\u002Fkouko\u002Floom-plugins\u002Fblob\u002Fmain\u002Floom-workflow\u002Fskills\u002Floom-memory\u002FSKILL.md",[],[]]