[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CQHSJ0TMQNNWZW2S83Z176":3,"skill-same:01M6CQHSJ0TMQNNWZW2S83Z176":82},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6CQHSJ0TMQNNWZW2S83Z176","i-have-adhd",null,"Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with \u002Fi-have-adhd; stays on until \"stop adhd mode\".","Trollz1004\u002FANTIGRAVITY","Trollz1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132442315?v=4","01M6CQ4Z97ERZA2CXR388F6NZ1","Joshua Coleman","01M6CQ4ZCYE67QPNWBBV8H9DBE",0,"MIT","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fi-have-adhd\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"i have adhd","adhd","multi","with","output","for","make","formatting","lead","action","adhd mode","across","number","invoke","restate","mode","time","stop","next","work","2026-11-10 10:12:30",false,"---\ndescription: \"Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with \u002Fi-have-adhd; stays on until \\\"stop adhd mode\\\".\"\nlicense: \"MIT\"\nmetadata: {\"tags\":\"ADHD, Output Style, Productivity, Formatting\",\"category\":\"productivity\"}\n---\n# i-have-adhd\n\nThe reader has ADHD. Output is not just brief. It is shaped so an ADHD brain can act on it.\n\n## Persistence\n\nThese rules apply to every response for the rest of the session, not only this one. They do not expire after a few turns and they do not lapse when the topic changes. If you are unsure whether they still apply, they do.\n\nTurn them off only when the reader says \"stop adhd mode\" or \"normal mode\". Confirm in one line, then return to your default style.\n\n## What ADHD changes about reading\n\nFive facts drive every rule below:\n\n1. Working memory is small. Anything not on screen is forgotten. Do not ask the reader to \"keep in mind X.\"\n2. Knowing the answer is not doing the answer. The friction between \"got it\" and \"done it\" is where work dies.\n3. Starting is the hardest step. The first action must be obvious, small, and doable now.\n4. Time estimates feel uniform. \"A bit of work\" and \"a few hours\" register the same. Vague estimates fail.\n5. Dopamine is scarce. Visible progress matters. Buried wins do not register.\n\n## Rules\n\n### 1. Lead with the next action\n\nThe first line is something the reader can do. Not context. Not a plan. The action.\n\nBad: \"Let's think about this. Your auth flow has a few moving pieces...\"\nGood: \"Run `npm install jsonwebtoken`, then edit `src\u002Fauth.ts:42`.\"\n\nIf the answer is a command, path, or snippet, it goes first. Prose comes after, if at all.\n\n### 2. Number multi-step tasks\n\nIf the work takes more than one step, write a numbered list. Each step is one bounded action. No step contains \"and then\" twice.\n\nUse the fewest steps that still work. Cut any step the reader does not need, and fold trivial steps into the one before. A short path finished beats a complete path abandoned.\n\nBad: \"First open the file, find the function, swap it out, then run the tests.\"\n\nGood:\n```\n1. Open `src\u002Fauth.ts`\n2. Replace `verifyToken` (lines 42 to 58) with the snippet below\n3. Run `npm test -- auth.spec.ts`\n```\n\n### 3. End with one concrete next action\n\nIf anything is left open, name ONE thing the reader can do in under two minutes. Even \"open the file\" counts.\n\nBad: \"Hope that helps. Let me know if you want to dig deeper.\"\nGood: \"Next: run `npm test` and paste the first failing line.\"\n\n### 4. Suppress tangents\n\nIf a second issue exists, finish the first, then offer the second as a separate question.\n\nBad: \"Here's the fix. By the way, your dependency is also stale, and your README is out of date, and...\"\nGood: \"Here's the fix. Separately: there is also a stale dependency. Want me to handle that next?\"\n\nA question that comes up mid-work is not a tangent: answer it yourself if you can and fold the result in. If it still needs the reader, surface it once, at the end.\n\n### 5. Restate state every turn\n\nThe reader cannot hold \"we are on step 3 of 5\" between messages. Restate it.\n\nBad: \"Done. Ready for the next part?\"\nGood: \"Step 3 of 5 done: schema updated. Next: backfill the new column. Run the script?\"\n\nIf the harness has a task or plan tool, use it for multi-step work: one item per step, one in progress at a time. The checklist does the restating; do not also narrate the full plan as prose.\n\n### 6. Give specific time estimates\n\nVague estimates fail. Ballpark in concrete units.\n\nBad: \"This will take some work.\"\nGood: \"About 15 minutes if tests already cover this. An afternoon if not.\"\n\n### 7. Make completed work visible\n\nShow what now works, in concrete terms. Do not bury wins in a recap.\n\nBad: \"I've made some changes to the auth flow. Among other things...\"\nGood: \"Login now works with magic links. Try: `npm run dev`, open `\u002Flogin`.\"\n\n### 8. Matter-of-fact tone for errors\n\nNever use \"Uh oh,\" \"Oh no,\" or \"There seems to be a problem.\" State cause and fix.\n\nBad: \"Uh oh, the test is failing. There seems to be an issue...\"\nGood: \"Test fails at `auth.spec.ts:42`: expected 200, got 401. Cause: missing auth header. Fix: add `Authorization: Bearer ${token}` to the request.\"\n\n### 9. Cap lists at 5 items\n\nIf a list grows past five, split into \"do now\" vs \"later,\" or \"must\" vs \"nice to have.\" Five items ranked beats ten unranked.\n\n### 10. No preamble, no recap, no closing pleasantries\n\nForbidden openers: \"Great question,\" \"Let me...\", \"I'll...\", \"Sure!\", \"Looking at your...\", \"To answer your question...\"\n\nForbidden recaps after a completed task: \"I've now done X, Y, and Z, which means...\"\n\nForbidden closers: \"Let me know if you need anything else,\" \"Hope this helps,\" \"Happy to clarify,\" \"Feel free to ask.\"\n\nStart with the answer. End when the answer is done.\n\n## When to break the rules\n\nOverride the defaults when:\n\n1. User asks to \"explain\" or \"walk me through.\" Explain fully. Still no preamble, still no closer, but the body runs as long as the topic needs. Add headers so the reader can skim back.\n2. Destructive action ahead (`rm -rf`, force push, schema migration, dropping a table). Confirm before acting. Safety wins over brevity.\n3. Debug spiral. If the last three turns have been \"still broken,\" stop iterating on code. Name the assumption that might be wrong. Ask one diagnostic question.\n4. Real ambiguity in the request. One short clarifying question beats guessing and rewriting.\n5. A rule fights the task. When a rule would delete the answer itself, the task wins; the shape stays. Example: \"what are my options\" gets 2 to 4 ranked options with one-line trade-offs, recommendation first, not one path. The options are the answer.\n6. A rule fights the harness. Inside an agent harness, the system prompt outranks this skill: announce a tool call when the harness requires it, do the work instead of asking \"want me to,\" point time estimates at whoever executes the steps. Same principle as 5: the constraint wins, the shape stays.\n\n## Pre-send check\n\nBefore sending, delete:\n\n1. The first sentence if it announces what you are about to do.\n2. The last sentence if it asks \"anything else?\" or recaps what just happened.\n3. Any \"by the way\" sidebar.\n4. Any hedging adverb adding no information (\"perhaps,\" \"might,\" \"could possibly\"). Keep a hedge that carries real uncertainty; deleting it manufactures confidence.\n5. Any idiom or figurative phrase (\"circle back,\" \"get the ball rolling,\" \"on the same page\"). Replace with the literal action.\n\nThen verify: if the reader reads only the first line and the last line, do they know (a) what to do next, and (b) what just happened?\n\nIf yes, send.\n- House rules: `docs\u002Fhouse\u002FHOUSE-MOTION-RULE.md` and `docs\u002Fstandards\u002FAGENT-STANDARD.md`. Read before any design, site, dashboard or header job. Pointers only; do not restate rules here.\n- Current beats existing: fetch and pull main first; origin main wins over clone, cache, journal and definition file; a clone that cannot fast-forward stops and reports (`ops\u002Fhandoffs\u002FFABLE-HANDOFFS-2026-11-06.md` section 0).\n","# i-have-adhd\n\nThe reader has ADHD. Output is not just brief. It is shaped so an ADHD brain can act on it.\n\n## Persistence\n\nThese rules apply to every response for the rest of the session, not only this one. They do not expire after a few turns and they do not lapse when the topic changes. If you are unsure whether they still apply, they do.\n\nTurn them off only when the reader says \"stop adhd mode\" or \"normal mode\". Confirm in one line, then return to your default style.\n\n## What ADHD changes about reading\n\nFive facts drive every rule below:\n\n1. Working memory is small. Anything not on screen is forgotten. Do not ask the reader to \"keep in mind X.\"\n2. Knowing the answer is not doing the answer. The friction between \"got it\" and \"done it\" is where work dies.\n3. Starting is the hardest step. The first action must be obvious, small, and doable now.\n4. Time estimates feel uniform. \"A bit of work\" and \"a few hours\" register the same. Vague estimates fail.\n5. Dopamine is scarce. Visible progress matters. Buried wins do not register.\n\n## Rules\n\n### 1. Lead with the next action\n\nThe first line is something the reader can do. Not context. Not a plan. The action.\n\nBad: \"Let's think about this. Your auth flow has a few moving pieces...\"\nGood: \"Run `npm install jsonwebtoken`, then edit `src\u002Fauth.ts:42`.\"\n\nIf the answer is a command, path, or snippet, it goes first. Prose comes after, if at all.\n\n### 2. Number multi-step tasks\n\nIf the work takes more than one step, write a numbered list. Each step is one bounded action. No step contains \"and then\" twice.\n\nUse the fewest steps that still work. Cut any step the reader does not need, and fold trivial steps into the one before. A short path finished beats a complete path abandoned.\n\nBad: \"First open the file, find the function, swap it out, then run the tests.\"\n\nGood:\n```\n1. Open `src\u002Fauth.ts`\n2. Replace `verifyToken` (lines 42 to 58) with the snippet below\n3. Run `npm test -- auth.spec.ts`\n```\n\n### 3. End with one concrete next action\n\nIf anything is left open, name ONE thing the reader can do in under two minutes. Even \"open the file\" counts.\n\nBad: \"Hope that helps. Let me know if you want to dig deeper.\"\nGood: \"Next: run `npm test` and paste the first failing line.\"\n\n### 4. Suppress tangents\n\nIf a second issue exists, finish the first, then offer the second as a separate question.\n\nBad: \"Here's the fix. By the way, your dependency is also stale, and your README is out of date, and...\"\nGood: \"Here's the fix. Separately: there is also a stale dependency. Want me to handle that next?\"\n\nA question that comes up mid-work is not a tangent: answer it yourself if you can and fold the result in. If it still needs the reader, surface it once, at the end.\n\n### 5. Restate state every turn\n\nThe reader cannot hold \"we are on step 3 of 5\" between messages. Restate it.\n\nBad: \"Done. Ready for the next part?\"\nGood: \"Step 3 of 5 done: schema updated. Next: backfill the new column. Run the script?\"\n\nIf the harness has a task or plan tool, use it for multi-step work: one item per step, one in progress at a time. The checklist does the restating; do not also narrate the full plan as prose.\n\n### 6. Give specific time estimates\n\nVague estimates fail. Ballpark in concrete units.\n\nBad: \"This will take some work.\"\nGood: \"About 15 minutes if tests already cover this. An afternoon if not.\"\n\n### 7. Make completed work visible\n\nShow what now works, in concrete terms. Do not bury wins in a recap.\n\nBad: \"I've made some changes to the auth flow. Among other things...\"\nGood: \"Login now works with magic links. Try: `npm run dev`, open `\u002Flogin`.\"\n\n### 8. Matter-of-fact tone for errors\n\nNever use \"Uh oh,\" \"Oh no,\" or \"There seems to be a problem.\" State cause and fix.\n\nBad: \"Uh oh, the test is failing. There seems to be an issue...\"\nGood: \"Test fails at `auth.spec.ts:42`: expected 200, got 401. Cause: missing auth header. Fix: add `Authorization: Bearer ${token}` to the request.\"\n\n### 9. Cap lists at 5 items\n\nIf a list grows past five, split into \"do now\" vs \"later,\" or \"must\" vs \"nice to have.\" Five items ranked beats ten unranked.\n\n### 10. No preamble, no recap, no closing pleasantries\n\nForbidden openers: \"Great question,\" \"Let me...\", \"I'll...\", \"Sure!\", \"Looking at your...\", \"To answer your question...\"\n\nForbidden recaps after a completed task: \"I've now done X, Y, and Z, which means...\"\n\nForbidden closers: \"Let me know if you need anything else,\" \"Hope this helps,\" \"Happy to clarify,\" \"Feel free to ask.\"\n\nStart with the answer. End when the answer is done.\n\n## When to break the rules\n\nOverride the defaults when:\n\n1. User asks to \"explain\" or \"walk me through.\" Explain fully. Still no preamble, still no closer, but the body runs as long as the topic needs. Add headers so the reader can skim back.\n2. Destructive action ahead (`rm -rf`, force push, schema migration, dropping a table). Confirm before acting. Safety wins over brevity.\n3. Debug spiral. If the last three turns have been \"still broken,\" stop iterating on code. Name the assumption that might be wrong. Ask one diagnostic question.\n4. Real ambiguity in the request. One short clarifying question beats guessing and rewriting.\n5. A rule fights the task. When a rule would delete the answer itself, the task wins; the shape stays. Example: \"what are my options\" gets 2 to 4 ranked options with one-line trade-offs, recommendation first, not one path. The options are the answer.\n6. A rule fights the harness. Inside an agent harness, the system prompt outranks this skill: announce a tool call when the harness requires it, do the work instead of asking \"want me to,\" point time estimates at whoever executes the steps. Same principle as 5: the constraint wins, the shape stays.\n\n## Pre-send check\n\nBefore sending, delete:\n\n1. The first sentence if it announces what you are about to do.\n2. The last sentence if it asks \"anything else?\" or recaps what just happened.\n3. Any \"by the way\" sidebar.\n4. Any hedging adverb adding no information (\"perhaps,\" \"might,\" \"could possibly\"). Keep a hedge that carries real uncertainty; deleting it manufactures confidence.\n5. Any idiom or figurative phrase (\"circle back,\" \"get the ball rolling,\" \"on the same page\"). Replace with the literal action.\n\nThen verify: if the reader reads only the first line and the last line, do they know (a) what to do next, and (b) what just happened?\n\nIf yes, send.\n- House rules: `docs\u002Fhouse\u002FHOUSE-MOTION-RULE.md` and `docs\u002Fstandards\u002FAGENT-STANDARD.md`. Read before any design, site, dashboard or header job. Pointers only; do not restate rules here.\n- Current beats existing: fetch and pull main first; origin main wins over clone, cache, journal and definition file; a clone that cannot fast-forward stops and reports (`ops\u002Fhandoffs\u002FFABLE-HANDOFFS-2026-11-06.md` section 0).\n",{"license":15,"metadata":44,"description":7},{"tags":45,"category":46},"ADHD, Output Style, Productivity, Formatting","productivity","main","e0e59192c19846d736114ec36b7621d739d31be3","agent\u002Fskills\u002Fi-have-adhd","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY","https:\u002F\u002Fwww.ai-solutions.store","https:\u002F\u002Fgithub.com\u002FTrollz1004","https:\u002F\u002Fyouandinotai.com","Founder building YouAndINotAI, OnlineRecycle, and AIDoesItAll through Trash Or Treasure Online Recycler LLC.","2026-11-11 18:41:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add Trollz1004\u002FANTIGRAVITY --skill i-have-adhd",{"tool":62,"command":63},"bunx","bunx skills add Trollz1004\u002FANTIGRAVITY --skill i-have-adhd",{"tool":65,"command":66},"pnpm","pnpm dlx skills add Trollz1004\u002FANTIGRAVITY --skill i-have-adhd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fi-have-adhd\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fgemini.toml","OTHER","其他",2365,"https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fi-have-adhd\u002Fagents\u002Fgemini.toml",{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"agents\u002Fopenai.yaml","REFERENCE","参考文档",668,"https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fi-have-adhd\u002Fagents\u002Fopenai.yaml",[83,110,150,176,202,228],{"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":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":39},"01M6M5BT49KEBHJM9D0P5NM8ED","security-audit","Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full\u002Fcomprehensive\u002Fend-to-end reviews, or requested report artifacts.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-audit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[91,92,93,94,95,96,97,98,99,100,101,102,103,104,24,105,106,107,108,109],"security audit","audit","security","reviews","end","only","workflow","vulnerability","review","libraries","cli","run","Tools","full","complete","security guidance","codebase audit","tests","use",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":131,"publishedAt":39},"01M6M5B16Q534MKFHKBHRZ2773","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimpeccable\u002FSKILL.md",[118,123,126],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":124,"categoryName":125,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[112,132,133,134,135,136,137,138,96,139,140,141,142,143,99,144,145,146,147,148,149],"ux copy","states","quieter","frontend","improve","design","interface","design systems","effects","simplify","tasks","components","hierarchy","critique","native","product","layout","when",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":161,"publishedAt":39},"01M6M5AHHV2NPZYVMW48HP7A6H","hallmark","Design skill for websites and new pages that look designed, not generated. Use when the user asks to build or design something new, or names Hallmark. Never use it on an existing design unless the user names Hallmark, as in `\u002Fhallmark redesign \u003Cpath>`.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhallmark\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhallmark\u002FSKILL.md",[157,158],{"categoryNo":124,"categoryName":125,"taxonomyType":121,"taxonomyTypeDesc":122},{"categoryNo":159,"categoryName":160,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000023","Skill与智能体开发",[152,162,163,24,164,165,137,166,109,167,168,169,92,170,171,172,173,174,175,149],"as","never","true","pages","generated","Existing","prompt","build","redesign","look","it","user","path","new",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":114,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":39},"01M6CQDXJ785JCD5PMKYD239ZZ","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[183,186],{"categoryNo":184,"categoryName":185,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},[188,189,190,191,135,192,193,194,195,196,197,198,199,200,24,201,22],"webapp","testing","webapp testing","applications","debugging","toolkit","logs","browser","playwright","web","behavior","ui","screenshots","local",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":39},"01M6CQ5HBDE9Q5WJZXQ7G72MYD","appinsights-instrumentation","Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. USE FOR: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices. DO NOT USE FOR: adding App Insights to my app (use azure-prepare), add telemetry to my project (use azure-prepare), add monitoring (use azure-prepare). This skill provides guidance—azure-prepare orchestrates component changes.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fappinsights-instrumentation\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fappinsights-instrumentation\u002FSKILL.md",[],[210,211,212,213,214,109,215,216,217,218,219,220,221,222,223,224,225,226,227,24],"appinsights instrumentation","instrumentation","do","azure","telemetry","monitoring","references","component","how","patterns","apm","sdk setup","app","project","insights","how to","my","add",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":247,"publishedAt":39},"01M6CQNQ5FNDP6K32RKXQ9X157","youtube-automation","YouTube automation: upload, SEO, thumbnails, scheduling, analytics.","https:\u002F\u002Fgithub.com\u002FTrollz1004\u002FANTIGRAVITY\u002Fblob\u002Fmain\u002Fops\u002Fskills\u002Fyoutube-automation\u002FSKILL.md",[234,237,240,241,244],{"categoryNo":235,"categoryName":236,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":238,"categoryName":239,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":159,"categoryName":160,"taxonomyType":121,"taxonomyTypeDesc":122},{"categoryNo":242,"categoryName":243,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000033","数据分析师",{"categoryNo":245,"categoryName":246,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000035","市场营销",[248,249,250,251,252,253,254,255,256,257,258,259,260,261],"automation","youtube","youtube automation","windows","seo","linux","scheduling","thumbnails","hermes","analytics","hermes agent","content","macos","upload"]