[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSV2NTTQS4C3JJ1AM7DABD":3,"skill-same:01M7CSV2NTTQS4C3JJ1AM7DABD":51},{"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":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M7CSV2NTTQS4C3JJ1AM7DABD","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.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbusiness-management\u002Fconfigure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 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","a73152352c0612252131e5cf84e91312a6cf17dc","business-management\u002Fconfigure","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill configure",{"tool":44,"command":45},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill configure",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill configure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbusiness-management\u002Fconfigure\u002FSKILL.md",[],[52,59,66,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\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},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\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},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\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},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]