[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F981N4B5KRN5FP0VC1ZX2X":3,"skill-same:01M7F981N4B5KRN5FP0VC1ZX2X":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":51},"01M7F981N4B5KRN5FP0VC1ZX2X","discord-configure",null,"Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks \"how do I set this up\" or \"who can reach me,\" or wants to check channel status.","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\u002Fdiscord-configure\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: discord-configure\ndescription: Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks \"how do I set this up\" or \"who can reach me,\" or wants to check channel status.\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Write\n  - Bash(ls *)\n  - Bash(mkdir *)\n---\n\n# \u002Fdiscord:configure — Discord Channel Setup\n\nWrites the bot token to `~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` and orients the\nuser on access policy. The server reads both files at boot.\n\nArguments passed: `$ARGUMENTS`\n\n---\n\n## Dispatch on arguments\n\n### No args — status and guidance\n\nRead both state files and give the user a complete picture:\n\n1. **Token** — check `~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` for\n   `DISCORD_BOT_TOKEN`. Show set\u002Fnot-set; if set, show first 6 chars masked.\n\n2. **Access** — read `~\u002F.claude\u002Fchannels\u002Fdiscord\u002Faccess.json` (missing file\n   = defaults: `dmPolicy: \"pairing\"`, empty allowlist). Show:\n   - DM policy and what it means in one line\n   - Allowed senders: count, and list display names or snowflakes\n   - Pending pairings: count, with codes and display names if any\n   - Guild channels opted in: count\n\n3. **What next** — end with a concrete next step based on state:\n   - No token → *\"Run `\u002Fdiscord:configure \u003Ctoken>` with your bot token from\n     the Developer Portal → Bot → Reset Token.\"*\n   - Token set, policy is pairing, nobody allowed → *\"DM your bot on\n     Discord. It replies with a code; approve with `\u002Fdiscord:access pair\n     \u003Ccode>`.\"*\n   - Token set, someone allowed → *\"Ready. DM your bot to reach the\n     assistant.\"*\n\n**Push toward lockdown — always.** The goal for every setup is `allowlist`\nwith a defined list. `pairing` is not a policy to stay on; it's a temporary\nway to capture Discord snowflakes you don't know. Once the IDs are in,\npairing has done its job and should be turned off.\n\nDrive the conversation this way:\n\n1. Read the allowlist. Tell the user who's in it.\n2. Ask: *\"Is that everyone who should reach you through this bot?\"*\n3. **If yes and policy is still `pairing`** → *\"Good. Let's lock it down so\n   nobody else can trigger pairing codes:\"* and offer to run\n   `\u002Fdiscord:access policy allowlist`. Do this proactively — don't wait to\n   be asked.\n4. **If no, people are missing** → *\"Have them DM the bot; you'll approve\n   each with `\u002Fdiscord:access pair \u003Ccode>`. Run this skill again once\n   everyone's in and we'll lock it.\"* Or, if they can get snowflakes\n   directly: *\"Enable Developer Mode in Discord (User Settings → Advanced),\n   right-click them → Copy User ID, then `\u002Fdiscord:access allow \u003Cid>`.\"*\n5. **If the allowlist is empty and they haven't paired themselves yet** →\n   *\"DM your bot to capture your own ID first. Then we'll add anyone else\n   and lock it down.\"*\n6. **If policy is already `allowlist`** → confirm this is the locked state.\n   If they need to add someone, Copy User ID is the clean path — no need to\n   reopen pairing.\n\nDiscord already gates reach (shared-server requirement + Public Bot toggle),\nbut that's not a substitute for locking the allowlist. Never frame `pairing`\nas the correct long-term choice. Don't skip the lockdown offer.\n\n### `\u003Ctoken>` — save it\n\n1. Treat `$ARGUMENTS` as the token (trim whitespace). Discord bot tokens are\n   long base64-ish strings, typically starting `MT` or `Nz`. Generated from\n   Developer Portal → Bot → Reset Token; only shown once.\n2. `mkdir -p ~\u002F.claude\u002Fchannels\u002Fdiscord`\n3. Read existing `.env` if present; update\u002Fadd the `DISCORD_BOT_TOKEN=` line,\n   preserve other keys. Write back, no quotes around the value.\n4. `chmod 600 ~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` — the token is a credential.\n5. Confirm, then show the no-args status so the user sees where they stand.\n\n### `clear` — remove the token\n\nDelete the `DISCORD_BOT_TOKEN=` line (or the file if that's the only line).\n\n---\n\n## Implementation notes\n\n- The channels dir might not exist if the server hasn't run yet. Missing file\n  = not configured, not an error.\n- The server reads `.env` once at boot. Token changes need a session restart\n  or `\u002Freload-plugins`. Say so after saving.\n- `access.json` is re-read on every inbound message — policy changes via\n  `\u002Fdiscord:access` take effect immediately, no restart.\n","# \u002Fdiscord:configure — Discord Channel Setup\n\nWrites the bot token to `~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` and orients the\nuser on access policy. The server reads both files at boot.\n\nArguments passed: `$ARGUMENTS`\n\n---\n\n## Dispatch on arguments\n\n### No args — status and guidance\n\nRead both state files and give the user a complete picture:\n\n1. **Token** — check `~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` for\n   `DISCORD_BOT_TOKEN`. Show set\u002Fnot-set; if set, show first 6 chars masked.\n\n2. **Access** — read `~\u002F.claude\u002Fchannels\u002Fdiscord\u002Faccess.json` (missing file\n   = defaults: `dmPolicy: \"pairing\"`, empty allowlist). Show:\n   - DM policy and what it means in one line\n   - Allowed senders: count, and list display names or snowflakes\n   - Pending pairings: count, with codes and display names if any\n   - Guild channels opted in: count\n\n3. **What next** — end with a concrete next step based on state:\n   - No token → *\"Run `\u002Fdiscord:configure \u003Ctoken>` with your bot token from\n     the Developer Portal → Bot → Reset Token.\"*\n   - Token set, policy is pairing, nobody allowed → *\"DM your bot on\n     Discord. It replies with a code; approve with `\u002Fdiscord:access pair\n     \u003Ccode>`.\"*\n   - Token set, someone allowed → *\"Ready. DM your bot to reach the\n     assistant.\"*\n\n**Push toward lockdown — always.** The goal for every setup is `allowlist`\nwith a defined list. `pairing` is not a policy to stay on; it's a temporary\nway to capture Discord snowflakes you don't know. Once the IDs are in,\npairing has done its job and should be turned off.\n\nDrive the conversation this way:\n\n1. Read the allowlist. Tell the user who's in it.\n2. Ask: *\"Is that everyone who should reach you through this bot?\"*\n3. **If yes and policy is still `pairing`** → *\"Good. Let's lock it down so\n   nobody else can trigger pairing codes:\"* and offer to run\n   `\u002Fdiscord:access policy allowlist`. Do this proactively — don't wait to\n   be asked.\n4. **If no, people are missing** → *\"Have them DM the bot; you'll approve\n   each with `\u002Fdiscord:access pair \u003Ccode>`. Run this skill again once\n   everyone's in and we'll lock it.\"* Or, if they can get snowflakes\n   directly: *\"Enable Developer Mode in Discord (User Settings → Advanced),\n   right-click them → Copy User ID, then `\u002Fdiscord:access allow \u003Cid>`.\"*\n5. **If the allowlist is empty and they haven't paired themselves yet** →\n   *\"DM your bot to capture your own ID first. Then we'll add anyone else\n   and lock it down.\"*\n6. **If policy is already `allowlist`** → confirm this is the locked state.\n   If they need to add someone, Copy User ID is the clean path — no need to\n   reopen pairing.\n\nDiscord already gates reach (shared-server requirement + Public Bot toggle),\nbut that's not a substitute for locking the allowlist. Never frame `pairing`\nas the correct long-term choice. Don't skip the lockdown offer.\n\n### `\u003Ctoken>` — save it\n\n1. Treat `$ARGUMENTS` as the token (trim whitespace). Discord bot tokens are\n   long base64-ish strings, typically starting `MT` or `Nz`. Generated from\n   Developer Portal → Bot → Reset Token; only shown once.\n2. `mkdir -p ~\u002F.claude\u002Fchannels\u002Fdiscord`\n3. Read existing `.env` if present; update\u002Fadd the `DISCORD_BOT_TOKEN=` line,\n   preserve other keys. Write back, no quotes around the value.\n4. `chmod 600 ~\u002F.claude\u002Fchannels\u002Fdiscord\u002F.env` — the token is a credential.\n5. Confirm, then show the no-args status so the user sees where they stand.\n\n### `clear` — remove the token\n\nDelete the `DISCORD_BOT_TOKEN=` line (or the file if that's the only line).\n\n---\n\n## Implementation notes\n\n- The channels dir might not exist if the server hasn't run yet. Missing file\n  = not configured, not an error.\n- The server reads `.env` once at boot. Token changes need a session restart\n  or `\u002Freload-plugins`. Say so after saving.\n- `access.json` is re-read on every inbound message — policy changes via\n  `\u002Fdiscord:access` take effect immediately, no restart.\n",{"name":5,"description":7,"allowed-tools":24,"user-invocable":29},[25,26,27,28],"Read","Write","Bash(ls *)","Bash(mkdir *)",true,"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fagent-dev\u002Fskills\u002Fdiscord-configure",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":40,"prompt":50,"zipAvailable":29},[41,44,47],{"tool":42,"command":43},"npx","npx skills add siddu1004\u002FSFP --skill discord-configure",{"tool":45,"command":46},"bunx","bunx skills add siddu1004\u002FSFP --skill discord-configure",{"tool":48,"command":49},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill discord-configure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fagent-dev\u002Fskills\u002Fdiscord-configure\u002FSKILL.md",[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":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":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]