[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75N432MPYAXEPDYMFND4M8P":3,"skill-same:01M75N432MPYAXEPDYMFND4M8P":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M75N432MPYAXEPDYMFND4M8P","antigravity-protocol",null,"Use this skill ALWAYS whenever the user asks you to write code, modify files, fix bugs, plan features, or do any software development task. Trigger this whenever the user wants efficient execution, low token usage, or mentions \"antigravity\", \"planning mode\", \"fast path\", or complains about you using too many tokens or thinking too much.","TehutiRaEl\u002FTHEHIVE","TehutiRaEl","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F267495122?v=4","01M75N1QQQHT359S3XMYK7NPCB","01M75N1QRAW5P8P43HEHWMXCTE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fantigravity\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\r\nname: antigravity-protocol\r\ndescription: Use this skill ALWAYS whenever the user asks you to write code, modify files, fix bugs, plan features, or do any software development task. Trigger this whenever the user wants efficient execution, low token usage, or mentions \"antigravity\", \"planning mode\", \"fast path\", or complains about you using too many tokens or thinking too much.\r\n---\r\n\r\n# Antigravity Protocol: High-Efficiency Coding\r\nThis skill instructs Claude to drop high-token conversational behavior and adopt a strict, API-driven, structured approach to software development, prioritizing exact edits and planning over exploratory guessing.\r\n\r\n1. Core Directives (Always Follow These)\r\n   Never use generic terminal commands (cat, grep, sed, ls, or complex bash scripts) for file operations or exploration.\r\n   Use specific tools (like view_file, grep_search, replace_file_content) if available, relying on structured JSON\u002Ftext APIs rather than terminal strings.\r\n   Use chunk-based editing. Never output full file contents. Issue search-and-replace style edits targeting exact line numbers.\r\n   Stop guessing. If a request is ambiguous, do NOT write test scripts to \"figure it out\". Stop and ask the user a specific question.\r\n   Acknowledge and Act. Do NOT write preambles (\"I understand you want to...\"). Do NOT summarize step-by-step what you just did unless asked. Output the tool call and state \"Done.\"\r\n2. Process Intent (Determine Mode)\r\n   When the user gives a prompt, categorize it immediately into one of three modes:\r\n\r\nMode A: Investigatory (No output needed except answers)\r\nTrigger: \"How does X work?\", \"Where is Y defined?\"\r\nAction: Search the codebase silently. Output only the short answer. Do not create a plan.\r\nMode B: The Fast Path (Small Changes)\r\nTrigger: \"Fix this typo\", \"Center the button\", \"Make the background red\".\r\nAction:\r\nRetrieve the file context to find exact line numbers.\r\nIssue a precise replace_file_content tool call.\r\nClose turn with \"Change applied.\" No planning required.\r\nMode C: Strict Planning Mode (Large Tasks)\r\nTrigger: \"Add a new page\", \"Implement auth\", \"Refactor the database\".\r\nAction:\r\nSilent Research: Use specific search tools to trace dependencies. Do NOT modify any code in this phase.\r\nCreate Plan: Generate an implementation_plan.md file. Document exact files to touch ([NEW], [MODIFY], [DELETE]) and the logical changes.\r\nHalt for Approval: Stop generating text. Wait for the user to reply \"Yes\" or approve the plan.\r\nExecute Checklist: Create a task.md checklist ([ ], [\u002F], [x]). Execute the specific file diffs as defined in the plan, updating the checklist as you go without deviating. 3. Tool Hierarchy\r\nEvaluate tools in this strict priority order:\r\n\r\nview_file \u002F grep_search (Highest Priority - Targeted reads, low token)\r\nreplace_file_content \u002F multi_replace_file_content (For targeted edits)\r\nwrite_to_file (Only for brand new files)\r\nrun_command via terminal (Lowest Priority - Use ONLY for running compiled tests, starting servers, or installing packages. NEVER for edits or file reading).\r\n\r\n\r\n---\r\n*Sourced verbatim (MIT, KINGSTAR-OMEGA\u002Fclaude-token-optimizer) into the Sovereign Hive by Fable, 2026-07-13.*\r\n","# Antigravity Protocol: High-Efficiency Coding\r\nThis skill instructs Claude to drop high-token conversational behavior and adopt a strict, API-driven, structured approach to software development, prioritizing exact edits and planning over exploratory guessing.\r\n\r\n1. Core Directives (Always Follow These)\r\n   Never use generic terminal commands (cat, grep, sed, ls, or complex bash scripts) for file operations or exploration.\r\n   Use specific tools (like view_file, grep_search, replace_file_content) if available, relying on structured JSON\u002Ftext APIs rather than terminal strings.\r\n   Use chunk-based editing. Never output full file contents. Issue search-and-replace style edits targeting exact line numbers.\r\n   Stop guessing. If a request is ambiguous, do NOT write test scripts to \"figure it out\". Stop and ask the user a specific question.\r\n   Acknowledge and Act. Do NOT write preambles (\"I understand you want to...\"). Do NOT summarize step-by-step what you just did unless asked. Output the tool call and state \"Done.\"\r\n2. Process Intent (Determine Mode)\r\n   When the user gives a prompt, categorize it immediately into one of three modes:\r\n\r\nMode A: Investigatory (No output needed except answers)\r\nTrigger: \"How does X work?\", \"Where is Y defined?\"\r\nAction: Search the codebase silently. Output only the short answer. Do not create a plan.\r\nMode B: The Fast Path (Small Changes)\r\nTrigger: \"Fix this typo\", \"Center the button\", \"Make the background red\".\r\nAction:\r\nRetrieve the file context to find exact line numbers.\r\nIssue a precise replace_file_content tool call.\r\nClose turn with \"Change applied.\" No planning required.\r\nMode C: Strict Planning Mode (Large Tasks)\r\nTrigger: \"Add a new page\", \"Implement auth\", \"Refactor the database\".\r\nAction:\r\nSilent Research: Use specific search tools to trace dependencies. Do NOT modify any code in this phase.\r\nCreate Plan: Generate an implementation_plan.md file. Document exact files to touch ([NEW], [MODIFY], [DELETE]) and the logical changes.\r\nHalt for Approval: Stop generating text. Wait for the user to reply \"Yes\" or approve the plan.\r\nExecute Checklist: Create a task.md checklist ([ ], [\u002F], [x]). Execute the specific file diffs as defined in the plan, updating the checklist as you go without deviating. 3. Tool Hierarchy\r\nEvaluate tools in this strict priority order:\r\n\r\nview_file \u002F grep_search (Highest Priority - Targeted reads, low token)\r\nreplace_file_content \u002F multi_replace_file_content (For targeted edits)\r\nwrite_to_file (Only for brand new files)\r\nrun_command via terminal (Lowest Priority - Use ONLY for running compiled tests, starting servers, or installing packages. NEVER for edits or file reading).\r\n\r\n\r\n---\r\n*Sourced verbatim (MIT, KINGSTAR-OMEGA\u002Fclaude-token-optimizer) into the Sovereign Hive by Fable, 2026-07-13.*\r\n",{"name":5,"description":7},"main","b4ebd6d8c3b36347a5d435bcb343a5fc1c6f08d1",".claude\u002Fskills\u002Fantigravity","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE","https:\u002F\u002Fgithub.com\u002FTehutiRaEl","2026-11-15 04:00:21",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add TehutiRaEl\u002FTHEHIVE --skill antigravity-protocol",{"tool":35,"command":36},"bunx","bunx skills add TehutiRaEl\u002FTHEHIVE --skill antigravity-protocol",{"tool":38,"command":39},"pnpm","pnpm dlx skills add TehutiRaEl\u002FTHEHIVE --skill antigravity-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fantigravity\u002FSKILL.md",true,[],[44,51,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M76XP63XDM4PFPX8MMVYN9JX","preamble-gate","Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent\u002Fsubagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI\u002Ftriggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log\u002Fdiff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpreamble-gate\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75RAYXC1W361YR9NBXD59AM","visionary-recommender","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills\u002Fvisionary-recommender\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75RAQN9Q450RD57J2S6FSR4","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75RAG1XMCJMF30HFV5S79AK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75RA8RK2JVWB8MYGRB65V75","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75RA08RXYRFSTNC6EEEX4ZD","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FTehutiRaEl\u002FTHEHIVE\u002Fblob\u002Fmain\u002Fskills-library\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[]]