[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DKQRM97JTMZT32DMZTHD0A":3,"skill-same:01M7DKQRM97JTMZT32DMZTHD0A":64},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7DKQRM97JTMZT32DMZTHD0A","to-spec",null,"Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","vc999999999\u002Fskillflux-catalog","vc999999999","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104196942?v=4","01M7DKFQK2JRAY2C9EMD7FHBWG","jiangbing","01M7DKFQKQA5E0BWZ1WQY4G9WA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-spec\ndescription: \"Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.\"\ndisable-model-invocation: true\n---\n\nThis skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n","This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nA LONG, numbered list of user stories. Each user story should be in the format of:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nThis list of user stories should be extremely extensive and cover all aspects of the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- A description of what makes a good test (only test external behavior, not implementation details)\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n",{"name":5,"description":7,"disable-model-invocation":25},true,"main","18f52829480a4e8df7dd5d9c13ce3b5284311891","skills\u002Fdevelopment\u002Fto-spec\u002F1.0.0","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog","https:\u002F\u002Fgithub.com\u002Fvc999999999","2026-10-11 20:16:46",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":25},[34,37,40],{"tool":35,"command":36},"npx","npx skills add vc999999999\u002Fskillflux-catalog --skill to-spec",{"tool":38,"command":39},"bunx","bunx skills add vc999999999\u002Fskillflux-catalog --skill to-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add vc999999999\u002Fskillflux-catalog --skill to-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002FSKILL.md",[45,51,56,60],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",135,"https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1068,{"path":57,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":58,"sourceHtmlUrl":59},"skillflux.json",985,"https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002Fskillflux.json",{"path":61,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":62,"sourceHtmlUrl":63},"skillflux.review.json",2346,"https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fto-spec\u002F1.0.0\u002Fskillflux.review.json",[65,73,81,89,97,105],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":20},"01M7DKTKB8RM9NFNA9VD5QNM59","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-schematics\u002F1.0.0\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-schematics\u002F1.0.0\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M7DKTE1BMWDNRQ6JHSB8YZVM","scientific-critical-thinking","Evaluates scientific claims and evidence quality. Applies to experimental design validity, biases and confounders, statistical interpretation, evidence grading frameworks (GRADE, Cochrane Risk of Bias), and teaching critical analysis. Supports evidence appraisal and identifying flaws; formal peer review writing belongs to peer-review.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-critical-thinking\u002F1.0.0\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-critical-thinking\u002F1.0.0\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":20},"01M7DKT74MD9SFF7K4ZGQJ5PAY","scientific-brainstorming","Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs. Use for early-stage research brainstorming or prioritizing candidate directions; hand off empirical validation, study design, ethics or regulatory review, and clinical questions to appropriate experts or skills.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-brainstorming\u002F1.0.0\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fscientific-brainstorming\u002F1.0.0\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M7DKT1837E2PSV5Y6EQV4A4B","aer-tables-figures","Use when constructing or revising regression tables, descriptive statistics tables, or figures after results are estimated and before submission for an AER, AER:Insights, or AEJ manuscript. Implements AER booktabs house style, regression-table layout, and figure-note conventions.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-tables-figures\u002F1.0.0\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-tables-figures\u002F1.0.0\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M7DKSW7MJQ8A88TJC1H293PB","aer-statspai","Use when aer-identification has fixed the design, after methodology choice and before aer-robustness or aer-tables-figures, to run an AER-track analysis with StatsPAI — the agent-native Python engine and MCP server for causal inference, robustness, sensitivity, and publication-ready table export.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-statspai\u002F1.0.0\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-statspai\u002F1.0.0\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7DKSQKV1429VSPVVHAM1QQM","aer-robustness","Use when the main empirical results exist but the manuscript lacks the robustness, heterogeneity, mechanism, and placebo checks that AER referees will demand. Apply after aer-identification and before aer-introduction so that the value-added paragraph can reference these tests.","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-robustness\u002F1.0.0\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvc999999999\u002Fskillflux-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Faer-robustness\u002F1.0.0\u002FSKILL.md",[],[]]