[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DWKWJ4DVGWE652XGQPC3C":3,"skill-same:01M79DWKWJ4DVGWE652XGQPC3C":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79DWKWJ4DVGWE652XGQPC3C","code-graph",null,"When and how to ask the code graph of this folder with the code_graph tool before reading many files","spectroscope\u002Fspectroscope","spectroscope","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F306844128?v=4","01M79DQ3TDVZFVMDAQXV630F1E","Christopher Ezell","01M79DQ3V1TGB9HT87FJG4Y06A",2,"MIT","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-core\u002Fsrc\u002Fmain\u002Fresources\u002Fapp-skills\u002Fcode-graph\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-graph\ndescription: When and how to ask the code graph of this folder with the code_graph tool before reading many files\n---\n\n# Code graph\n\nThis folder has a code graph: a map of its classes, functions and files, and of how they call, import and contain each other. The `code_graph` tool asks that map about structure. One call can answer a question that would otherwise take many file reads.\n\n## When to call it\n\nCall `code_graph` before you read files when the question is about structure, for example:\n\n- who calls a function, or what a class depends on\n- how one part of the code reaches another\n- what a change to a function or a file would affect\n- where to start in code you have not read yet\n\nOnce the graph has named the places, read those files to check the details you need, such as an exact line or a value. When the question is about one file you already know, read that file directly.\n\n## The actions\n\n- `query` with `question`: a question in words that names the parts it is about, for example \"how does PlaybookRunner reach the provider\". `budget` (100 to 4000 tokens) keeps the answer short, and `dfs` follows one path deep instead of looking around wide.\n- `path` with `from` and `to`: the shortest chain of calls, imports or containment between two nodes.\n- `explain` with `name`: one node and its direct neighbors.\n- `affected` with `name`: what depends on a node. `depth` (1 to 6) sets how many steps back the answer goes.\n- `god_nodes`: the most connected nodes, and `top` (1 to 50) sets how many. It is a good first call in code you do not know.\n\n## Phrasing a question\n\nName things the way the code names them: a class such as `PlaybookRunner`, a method such as `PlaybookRunner.step`, or a file such as `PlaybookRunner.java`. The graph matches nodes by name, so the exact spelling finds more than a description does. Ask one thing per call; a narrow question gets a short answer.\n\nWhen a name is not found, try the class name alone, then a `query` in words.\n\n## Limits\n\nThe graph shows the code as it was at the last build, and it holds code only, not documentation or images. If files changed since then, tell the person and suggest `\u002Fgraph update`. The answer is the tool's text output, so check anything you plan to change in the file itself.\n","# Code graph\n\nThis folder has a code graph: a map of its classes, functions and files, and of how they call, import and contain each other. The `code_graph` tool asks that map about structure. One call can answer a question that would otherwise take many file reads.\n\n## When to call it\n\nCall `code_graph` before you read files when the question is about structure, for example:\n\n- who calls a function, or what a class depends on\n- how one part of the code reaches another\n- what a change to a function or a file would affect\n- where to start in code you have not read yet\n\nOnce the graph has named the places, read those files to check the details you need, such as an exact line or a value. When the question is about one file you already know, read that file directly.\n\n## The actions\n\n- `query` with `question`: a question in words that names the parts it is about, for example \"how does PlaybookRunner reach the provider\". `budget` (100 to 4000 tokens) keeps the answer short, and `dfs` follows one path deep instead of looking around wide.\n- `path` with `from` and `to`: the shortest chain of calls, imports or containment between two nodes.\n- `explain` with `name`: one node and its direct neighbors.\n- `affected` with `name`: what depends on a node. `depth` (1 to 6) sets how many steps back the answer goes.\n- `god_nodes`: the most connected nodes, and `top` (1 to 50) sets how many. It is a good first call in code you do not know.\n\n## Phrasing a question\n\nName things the way the code names them: a class such as `PlaybookRunner`, a method such as `PlaybookRunner.step`, or a file such as `PlaybookRunner.java`. The graph matches nodes by name, so the exact spelling finds more than a description does. Ask one thing per call; a narrow question gets a short answer.\n\nWhen a name is not found, try the class name alone, then a `query` in words.\n\n## Limits\n\nThe graph shows the code as it was at the last build, and it holds code only, not documentation or images. If files changed since then, tell the person and suggest `\u002Fgraph update`. The answer is the tool's text output, so check anything you plan to change in the file itself.\n",{"name":5,"description":7},"main","4ee98acbdee77bbc9d0b989ac8c3d7421963b1c2","spectro-core\u002Fsrc\u002Fmain\u002Fresources\u002Fapp-skills\u002Fcode-graph",1,"https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope","https:\u002F\u002Fspectroscope.ai","https:\u002F\u002Fgithub.com\u002Fspectroscope","2026-11-11 07:30:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add spectroscope\u002Fspectroscope --skill code-graph",{"tool":38,"command":39},"bunx","bunx skills add spectroscope\u002Fspectroscope --skill code-graph",{"tool":41,"command":42},"pnpm","pnpm dlx skills add spectroscope\u002Fspectroscope --skill code-graph","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-core\u002Fsrc\u002Fmain\u002Fresources\u002Fapp-skills\u002Fcode-graph\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79DY61ZW6AS4ZXPGPK8CYQM","brainstorming","Test fixture skill.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Ftest-bundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fbrainstorming\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79DY3K5E2S4F9CK4QA4V1VD","s","A fixture skill.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fspectrolyzr-fixture\u002Fbundle\u002Fskills\u002Fs\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79DY2H81J251GQT8M9SYXJ2","beta","The second skill of the fixture plugin.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fplugin-fixture\u002Ffixture\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79DY1CTTH4EH1WTKDH8379N","alpha","The first skill of the fixture plugin.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fplugin-fixture\u002Ffixture\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79DXWTRCQD2XM27K0V8MY50","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79DXTXR39NVJX3KBX8ZE44P","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fwriting-plans\u002FSKILL.md",[],[]]