[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F986CRS3XYGF3KP0VFNX38":3,"skill-same:01M7F986CRS3XYGF3KP0VFNX38":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F986CRS3XYGF3KP0VFNX38","ecc-guide",null,"Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.","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\u002Fagent-dev\u002Fskills\u002Fecc-guide\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ecc-guide\ndescription: Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.\nmetadata:\n  origin: community\n---\n\n# ECC Guide\n\nUse this skill when a user needs help understanding, navigating, installing, or choosing parts of ECC.\n\n## When To Use\n\nUse this skill when the user:\n\n- asks what ECC includes\n- wants help finding a skill, command, agent, hook, rule, or install profile\n- is new to the repository and needs a guided path\n- asks \"how do I do X with ECC?\"\n- asks which ECC components fit a project\n- needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate\n- is confused by install paths, duplicate installs, reset\u002Funinstall, or selective install options\n\n## Core Principle\n\nAnswer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.\n\nWhen the ECC repository is available, inspect the relevant files before giving a concrete answer:\n\n```bash\nnode scripts\u002Fci\u002Fcatalog.js --json\nfind skills -maxdepth 2 -name SKILL.md | sort\nfind commands -maxdepth 1 -name '*.md' | sort\nfind agents -maxdepth 1 -name '*.md' | sort\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --list-components --json\n```\n\nUse the smallest set of reads needed for the user's question.\n\n## Repository Map\n\n- `README.md`: install paths, uninstall\u002Freset guidance, public positioning, FAQs\n- `AGENTS.md`: contributor guidance and project structure\n- `agent.yaml`: exported gitagent surface and command list\n- `commands\u002F`: maintained slash-command compatibility shims\n- `skills\u002F*\u002FSKILL.md`: reusable workflows and domain playbooks\n- `agents\u002F*.md`: delegated subagent role prompts\n- `rules\u002F`: language and harness rules\n- `hooks\u002FREADME.md`, `hooks\u002Fhooks.json`, `scripts\u002Fhooks\u002F`: hook behavior and safety gates\n- `manifests\u002Finstall-*.json`: selective install modules, components, profiles, and target support\n- `docs\u002F`: harness guides, architecture notes, translated docs, release docs\n\n## Response Style\n\nLead with the answer, then give the next action. Most users do not need a full catalog dump.\n\nGood first response shape:\n\n1. what to use\n2. why it fits\n3. exact file or command to inspect\n4. one next command or question\n\nAvoid:\n\n- listing every skill or command by default\n- repeating large README sections\n- recommending retired command shims when a skill-first path exists\n- claiming a component exists without checking the filesystem\n- replacing install guidance with manual copy commands when the managed installer supports the target\n\n## Common Tasks\n\n### New User Onboarding\n\nGive a short menu:\n\n- install or reset ECC\n- pick skills for a project\n- understand commands vs skills\n- inspect hooks and safety behavior\n- run a harness audit\n- find a specific workflow\n\nPoint to `README.md` for install\u002Freset and `\u002Fproject-init` for project-specific onboarding.\n\n### Feature Discovery\n\nFor \"what should I use for X?\":\n\n1. Search `skills\u002F`, `commands\u002F`, and `agents\u002F`.\n2. Prefer skills as the primary workflow surface.\n3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.\n4. Mention agents when delegation is useful.\n\nUseful searches:\n\n```bash\nrg -n \"\u003Cquery>\" skills commands agents docs\nfind skills -maxdepth 2 -name SKILL.md | sort\n```\n\n### Install Guidance\n\nUse managed install paths:\n\n```bash\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --profile minimal --target claude --json\nnode scripts\u002Finstall-apply.js --profile minimal --target claude --dry-run\n```\n\nFor specific skill installs:\n\n```bash\nnode scripts\u002Finstall-plan.js --skills \u003Cskill-id> --target claude --json\nnode scripts\u002Finstall-apply.js --skills \u003Cskill-id> --target claude --dry-run\n```\n\nWarn users not to stack plugin installs and full manual\u002Fprofile installs unless they intentionally want duplicate surfaces.\n\n### Project Onboarding\n\nUse `\u002Fproject-init` when the user wants ECC configured for a target repo. The expected sequence is:\n\n1. detect the stack from project files\n2. resolve a dry-run install plan\n3. inspect existing `CLAUDE.md` and settings files\n4. ask before applying changes\n5. keep generated guidance minimal and repo-specific\n\n### Troubleshooting\n\nAsk for the target harness and install path first, then inspect:\n\n- plugin install metadata\n- `.claude\u002F`, `.cursor\u002F`, `.codex\u002F`, `.gemini\u002F`, `.opencode\u002F`, `.codebuddy\u002F`, `.joycode\u002F`, or `.qwen\u002F`\n- `hooks\u002Fhooks.json`\n- install-state files\n- relevant command\u002Fskill files\n\nFor repo health, suggest:\n\n```bash\nnpm run harness:audit -- --format text\nnpm run observability:ready\nnpm test\n```\n\n## Output Templates\n\n### Short Recommendation\n\n```text\nUse \u003Cskill-or-command>. It fits because \u003Creason>.\n\nCanonical file: \u003Cpath>\nVerify with: \u003Ccommand>\nNext: \u003Cone concrete action>\n```\n\n### Search Results\n\n```text\nBest matches:\n- \u003Cpath>: \u003Cwhy it matters>\n- \u003Cpath>: \u003Cwhy it matters>\n\nRecommendation: \u003Cwhich one to use first and why>\n```\n\n### Install Plan Summary\n\n```text\nDetected: \u003Cstack evidence>\nTarget: \u003Charness>\nPlan: \u003Cprofile\u002Fmodules\u002Fskills>\nDry run: \u003Ccommand>\nWould change: \u003Cpaths>\nNeeds approval before apply: \u003Cyes\u002Fno>\n```\n\n## Related Surfaces\n\n- `\u002Fproject-init`: stack-aware onboarding plan for a target repo\n- `\u002Fharness-audit`: deterministic readiness scorecard\n- `\u002Fskill-health`: skill quality review\n- `\u002Fskill-create`: generate a new skill from local git history\n- `\u002Fsecurity-scan`: inspect Claude\u002FOpenCode configuration security\n","# ECC Guide\n\nUse this skill when a user needs help understanding, navigating, installing, or choosing parts of ECC.\n\n## When To Use\n\nUse this skill when the user:\n\n- asks what ECC includes\n- wants help finding a skill, command, agent, hook, rule, or install profile\n- is new to the repository and needs a guided path\n- asks \"how do I do X with ECC?\"\n- asks which ECC components fit a project\n- needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate\n- is confused by install paths, duplicate installs, reset\u002Funinstall, or selective install options\n\n## Core Principle\n\nAnswer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.\n\nWhen the ECC repository is available, inspect the relevant files before giving a concrete answer:\n\n```bash\nnode scripts\u002Fci\u002Fcatalog.js --json\nfind skills -maxdepth 2 -name SKILL.md | sort\nfind commands -maxdepth 1 -name '*.md' | sort\nfind agents -maxdepth 1 -name '*.md' | sort\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --list-components --json\n```\n\nUse the smallest set of reads needed for the user's question.\n\n## Repository Map\n\n- `README.md`: install paths, uninstall\u002Freset guidance, public positioning, FAQs\n- `AGENTS.md`: contributor guidance and project structure\n- `agent.yaml`: exported gitagent surface and command list\n- `commands\u002F`: maintained slash-command compatibility shims\n- `skills\u002F*\u002FSKILL.md`: reusable workflows and domain playbooks\n- `agents\u002F*.md`: delegated subagent role prompts\n- `rules\u002F`: language and harness rules\n- `hooks\u002FREADME.md`, `hooks\u002Fhooks.json`, `scripts\u002Fhooks\u002F`: hook behavior and safety gates\n- `manifests\u002Finstall-*.json`: selective install modules, components, profiles, and target support\n- `docs\u002F`: harness guides, architecture notes, translated docs, release docs\n\n## Response Style\n\nLead with the answer, then give the next action. Most users do not need a full catalog dump.\n\nGood first response shape:\n\n1. what to use\n2. why it fits\n3. exact file or command to inspect\n4. one next command or question\n\nAvoid:\n\n- listing every skill or command by default\n- repeating large README sections\n- recommending retired command shims when a skill-first path exists\n- claiming a component exists without checking the filesystem\n- replacing install guidance with manual copy commands when the managed installer supports the target\n\n## Common Tasks\n\n### New User Onboarding\n\nGive a short menu:\n\n- install or reset ECC\n- pick skills for a project\n- understand commands vs skills\n- inspect hooks and safety behavior\n- run a harness audit\n- find a specific workflow\n\nPoint to `README.md` for install\u002Freset and `\u002Fproject-init` for project-specific onboarding.\n\n### Feature Discovery\n\nFor \"what should I use for X?\":\n\n1. Search `skills\u002F`, `commands\u002F`, and `agents\u002F`.\n2. Prefer skills as the primary workflow surface.\n3. Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.\n4. Mention agents when delegation is useful.\n\nUseful searches:\n\n```bash\nrg -n \"\u003Cquery>\" skills commands agents docs\nfind skills -maxdepth 2 -name SKILL.md | sort\n```\n\n### Install Guidance\n\nUse managed install paths:\n\n```bash\nnode scripts\u002Finstall-plan.js --list-profiles\nnode scripts\u002Finstall-plan.js --profile minimal --target claude --json\nnode scripts\u002Finstall-apply.js --profile minimal --target claude --dry-run\n```\n\nFor specific skill installs:\n\n```bash\nnode scripts\u002Finstall-plan.js --skills \u003Cskill-id> --target claude --json\nnode scripts\u002Finstall-apply.js --skills \u003Cskill-id> --target claude --dry-run\n```\n\nWarn users not to stack plugin installs and full manual\u002Fprofile installs unless they intentionally want duplicate surfaces.\n\n### Project Onboarding\n\nUse `\u002Fproject-init` when the user wants ECC configured for a target repo. The expected sequence is:\n\n1. detect the stack from project files\n2. resolve a dry-run install plan\n3. inspect existing `CLAUDE.md` and settings files\n4. ask before applying changes\n5. keep generated guidance minimal and repo-specific\n\n### Troubleshooting\n\nAsk for the target harness and install path first, then inspect:\n\n- plugin install metadata\n- `.claude\u002F`, `.cursor\u002F`, `.codex\u002F`, `.gemini\u002F`, `.opencode\u002F`, `.codebuddy\u002F`, `.joycode\u002F`, or `.qwen\u002F`\n- `hooks\u002Fhooks.json`\n- install-state files\n- relevant command\u002Fskill files\n\nFor repo health, suggest:\n\n```bash\nnpm run harness:audit -- --format text\nnpm run observability:ready\nnpm test\n```\n\n## Output Templates\n\n### Short Recommendation\n\n```text\nUse \u003Cskill-or-command>. It fits because \u003Creason>.\n\nCanonical file: \u003Cpath>\nVerify with: \u003Ccommand>\nNext: \u003Cone concrete action>\n```\n\n### Search Results\n\n```text\nBest matches:\n- \u003Cpath>: \u003Cwhy it matters>\n- \u003Cpath>: \u003Cwhy it matters>\n\nRecommendation: \u003Cwhich one to use first and why>\n```\n\n### Install Plan Summary\n\n```text\nDetected: \u003Cstack evidence>\nTarget: \u003Charness>\nPlan: \u003Cprofile\u002Fmodules\u002Fskills>\nDry run: \u003Ccommand>\nWould change: \u003Cpaths>\nNeeds approval before apply: \u003Cyes\u002Fno>\n```\n\n## Related Surfaces\n\n- `\u002Fproject-init`: stack-aware onboarding plan for a target repo\n- `\u002Fharness-audit`: deterministic readiness scorecard\n- `\u002Fskill-health`: skill quality review\n- `\u002Fskill-create`: generate a new skill from local git history\n- `\u002Fsecurity-scan`: inspect Claude\u002FOpenCode configuration security\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fagent-dev\u002Fskills\u002Fecc-guide",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add siddu1004\u002FSFP --skill ecc-guide",{"tool":41,"command":42},"bunx","bunx skills add siddu1004\u002FSFP --skill ecc-guide",{"tool":44,"command":45},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill ecc-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-dev\u002Fskills\u002Fecc-guide\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]