[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FA4TC8577MX6W99K2GATF5":3,"skill-same:01M7FA4TC8577MX6W99K2GATF5":47},{"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":31,"updatedAt":32,"install":33,"resources":46},"01M7FA4TC8577MX6W99K2GATF5","gsd-spike",null,"Spike an idea through experiential exploration, or propose what to spike next (frontier mode)","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fagents\u002Fskills\u002Fgsd-spike\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: gsd-spike\ndescription: \"Spike an idea through experiential exploration, or propose what to spike next (frontier mode)\"\n---\nInvoke this Pi skill with `\u002Fskill:gsd-spike`.\n\n**Pi dispatch (fail closed).** Pi has no built-in subagent API; GSD provides the `gsd_dispatch` tool. Where a workflow step dispatches a named `gsd-*` role, call `gsd_dispatch` with `role` (the installed role name) and `task` (the full task text). A workflow that still writes the step as an `Agent(...)` call means the same: its `subagent_type` is the `role` and its `prompt` is the `task`. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If `gsd_dispatch` reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.\n\n**Pi includes.** Pi does not expand `@path` references in a skill. Before doing anything else, read every file listed under `\u003Cexecution_context>` below with your read tool (the leading `@` is accepted), then follow the workflow they define.\n\n\n\n\u003Carguments>(the text typed after the skill name)\u003C\u002Farguments>\n\nThe text inside `\u003Carguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.\n\n\u003Cobjective>\nSpike an idea through experiential exploration — build focused experiments to feel the pieces\nof a future app, validate feasibility, and produce verified knowledge for the real build.\nSpikes live in `.planning\u002Fspikes\u002F` and integrate with GSD commit patterns, state tracking,\nand handoff workflows.\n\nTwo modes:\n- **Idea mode** (default) — describe an idea to spike\n- **Frontier mode** (no argument or \"frontier\") — analyzes existing spike landscape and proposes integration and frontier spikes\n\nDoes not require prior new-project setup — auto-creates `.planning\u002Fspikes\u002F` if needed.\n\u003C\u002Fobjective>\n\n\u003Cexecution_context>\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Fworkflows\u002Fspike.md\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Fworkflows\u002Fspike-wrap-up.md\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Freferences\u002Fui-brand.md\n\u003C\u002Fexecution_context>\n\n\n\n\u003Ccontext>\nIdea: the `\u003Carguments>` block\n\n**Available flags:**\n- `--quick` — Skip decomposition\u002Falignment, jump straight to building. Use when you already know what to spike.\n- `--text` — Use plain-text numbered lists instead of AskUserQuestion (for non-Claude runtimes).\n- `--wrap-up` — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.\n\u003C\u002Fcontext>\n\n\u003Cprocess>\nParse the first token of the `\u003Carguments>` block:\n- If it is `--wrap-up`: strip the flag, execute the spike-wrap-up workflow\n- Otherwise: pass all of the `\u003Carguments>` block as the idea to the spike workflow end-to-end.\n\nPreserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).\n\u003C\u002Fprocess>\n","Invoke this Pi skill with `\u002Fskill:gsd-spike`.\n\n**Pi dispatch (fail closed).** Pi has no built-in subagent API; GSD provides the `gsd_dispatch` tool. Where a workflow step dispatches a named `gsd-*` role, call `gsd_dispatch` with `role` (the installed role name) and `task` (the full task text). A workflow that still writes the step as an `Agent(...)` call means the same: its `subagent_type` is the `role` and its `prompt` is the `task`. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If `gsd_dispatch` reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.\n\n**Pi includes.** Pi does not expand `@path` references in a skill. Before doing anything else, read every file listed under `\u003Cexecution_context>` below with your read tool (the leading `@` is accepted), then follow the workflow they define.\n\n\n\n\u003Carguments>(the text typed after the skill name)\u003C\u002Farguments>\n\nThe text inside `\u003Carguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.\n\n\u003Cobjective>\nSpike an idea through experiential exploration — build focused experiments to feel the pieces\nof a future app, validate feasibility, and produce verified knowledge for the real build.\nSpikes live in `.planning\u002Fspikes\u002F` and integrate with GSD commit patterns, state tracking,\nand handoff workflows.\n\nTwo modes:\n- **Idea mode** (default) — describe an idea to spike\n- **Frontier mode** (no argument or \"frontier\") — analyzes existing spike landscape and proposes integration and frontier spikes\n\nDoes not require prior new-project setup — auto-creates `.planning\u002Fspikes\u002F` if needed.\n\u003C\u002Fobjective>\n\n\u003Cexecution_context>\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Fworkflows\u002Fspike.md\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Fworkflows\u002Fspike-wrap-up.md\n@__GSD_PI_ENGINE_ROOT__\u002Fgsd-core\u002Freferences\u002Fui-brand.md\n\u003C\u002Fexecution_context>\n\n\n\n\u003Ccontext>\nIdea: the `\u003Carguments>` block\n\n**Available flags:**\n- `--quick` — Skip decomposition\u002Falignment, jump straight to building. Use when you already know what to spike.\n- `--text` — Use plain-text numbered lists instead of AskUserQuestion (for non-Claude runtimes).\n- `--wrap-up` — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.\n\u003C\u002Fcontext>\n\n\u003Cprocess>\nParse the first token of the `\u003Carguments>` block:\n- If it is `--wrap-up`: strip the flag, execute the spike-wrap-up workflow\n- Otherwise: pass all of the `\u003Carguments>` block as the idea to the spike workflow end-to-end.\n\nPreserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).\n\u003C\u002Fprocess>\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fagents\u002Fskills\u002Fgsd-spike",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill gsd-spike",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill gsd-spike",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill gsd-spike","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fagents\u002Fskills\u002Fgsd-spike\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","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\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]