[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CS9D68E6QTNJZYYNE3XY06":3,"skill-same:01M7CS9D68E6QTNJZYYNE3XY06":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CS9D68E6QTNJZYYNE3XY06","ponytail-audit",null,"Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for \"audit this codebase\", \"review the whole repo\", \"find bloat\", \"what can I delete\", \u002Fponytail-audit.","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\u002Fai-agents\u002Fponytail-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ponytail-audit\ndescription: >\n  Quality audit of a whole repo: bugs, security holes, what breaks under real\n  load, risky code without tests, slow paths, and what to delete, merge or\n  split. Ranked, each finding explained in plain English. One-shot report,\n  changes nothing. Use for \"audit this codebase\", \"review the whole repo\",\n  \"find bloat\", \"what can I delete\", \u002Fponytail-audit.\n---\n\nAudit the whole repo like the senior developer who just inherited it and\nwill be paged when it breaks. Order of importance: correct, safe, holds under\nload, tested, fast, lean. Lean still matters: every extra line must be read,\ntested and fixed later. This is a report the user asked for, so give it in full.\n\n## 1. Map first\n\n- Audit what the user names: a folder, a package, or the whole repo.\n  Nothing named: the whole repo.\n- Read the README, the deploy and build config, the dependency list, the\n  entry points (main, routes, handlers, jobs, CLI commands) and the tests.\n- Find the expected load: one person running a script, or many users and\n  processes at once. Judge scale against that, and say which load you assumed.\n- Trace the main flows end to end: where data comes in, what is stored,\n  what goes out. Read those paths fully: input from users, money, auth,\n  data writes, background jobs, anything shared between processes.\n- Big repo: go deep where a mistake costs the most, not file by file. Say\n  which parts you did not read.\n\n## 2. Look for\n\n1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,\n   rounding, time zones), callers that disagree with what a function returns,\n   the same rule applied differently in two places.\n2. **Risk:** security holes (injection, weak randomness, secrets in code,\n   missing checks on input from users), data loss (errors swallowed, writes\n   in the wrong order, no transaction).\n3. **Scale:** fine for one user, wrong for many: check-then-write races, the\n   same work done by every process, memory or lists that only grow, a query\n   per item, O(n^2) on big input, per-process state that must be shared.\n4. **Missing test:** risky logic (a branch, a parser, money, security, data\n   writes) with no test that fails when it breaks. One good test, not coverage.\n5. **Speed:** big slowdowns are problems. Small wins (work repeated in a hot\n   loop) are suggestions; some software counts every millisecond.\n6. **Lean:** code that should not exist or should be smaller.\n   - delete: dead code, unused options, flags and config, speculative features\n   - reuse: two helpers doing the same thing (keep one, name the path)\n   - stdlib \u002F native: the standard library or platform already does it;\n     a dependency doing what a few lines or the platform can do\n   - yagni: interface with one implementation, factory with one product,\n     wrapper that only passes calls through\n   - merge: near-copies that must change together\n   - split: one function or class doing several unrelated jobs, so it is\n     hard to read or test. Split by job, never by line count, and never into\n     helpers that exist only to make a function shorter.\n\n## 3. Check before you report\n\n- Every finding needs a concrete case: \"this input or situation leads to this\n  wrong result\". No case, no finding.\n- Before calling code unused, grep the whole tree for it, including tests,\n  fixtures, config, and string or dynamic references.\n- A shortcut marked with a `shortcut:` (or older `ponytail:`) comment that names its limit is a\n  decision, not a finding, unless the expected load already crosses it.\n- Propose the smallest fix that works. Prefer fixes that delete code. Never\n  add layers, frameworks or config the problem does not need.\n- No style taste, no \"consider\", no vague worries.\n\n## 4. Output\n\nVery simple English: short sentences, everyday words. Explain a technical\nterm the first time you use it. The reader may never have seen this code.\n\nStart with `What this repo does:` in two or three sentences, and the load\nyou assumed.\n\nThen the findings in three groups, most important first, skip empty groups:\n- **Must fix:** bug, security, data loss, breaks at the expected load.\n- **Should fix:** risky code without a test, real slowness, duplication, a\n  function that mixes jobs, code that should not exist.\n- **Nice to have:** small speed-ups, shorter forms.\n\nNumber findings across all groups, so the user can say \"fix 2 and 5\". At\nmost 20 findings; if you left smaller ones out, say how many.\nEvery finding has all four parts, each one or two short sentences:\n\n2. **Orders land on the wrong day** (`billing\u002Fclose_day.py:L40-52`)\n   - **What this is:** At midnight this job closes the day and bills all orders of that day.\n   - **Problem:** It takes \"today\" from the server clock, which runs in UTC. An order placed\n     at 00:30 in Berlin is billed on the day before.\n   - **Fix:** Compute the day once in the shop's time zone:\n     `datetime.now(ZoneInfo(\"Europe\u002FBerlin\")).date()`. One line, nothing else changes.\n   - **If we skip it:** Late orders show the wrong date, and accounting fixes them by hand.\n\nEnd with:\n- `Verdict:` one line: healthy, or what to fix first.\n- `Lean: -\u003CN> lines, -\u003CM> dependencies possible.` when lean findings exist.\n- `Not checked:` the parts you did not read or could not run.\n\nNothing found: `What this repo does:`, then `Healthy. Nothing to fix.` and\none line on what you checked.\n\nOne-shot report, changes no code.\n","Audit the whole repo like the senior developer who just inherited it and\nwill be paged when it breaks. Order of importance: correct, safe, holds under\nload, tested, fast, lean. Lean still matters: every extra line must be read,\ntested and fixed later. This is a report the user asked for, so give it in full.\n\n## 1. Map first\n\n- Audit what the user names: a folder, a package, or the whole repo.\n  Nothing named: the whole repo.\n- Read the README, the deploy and build config, the dependency list, the\n  entry points (main, routes, handlers, jobs, CLI commands) and the tests.\n- Find the expected load: one person running a script, or many users and\n  processes at once. Judge scale against that, and say which load you assumed.\n- Trace the main flows end to end: where data comes in, what is stored,\n  what goes out. Read those paths fully: input from users, money, auth,\n  data writes, background jobs, anything shared between processes.\n- Big repo: go deep where a mistake costs the most, not file by file. Say\n  which parts you did not read.\n\n## 2. Look for\n\n1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,\n   rounding, time zones), callers that disagree with what a function returns,\n   the same rule applied differently in two places.\n2. **Risk:** security holes (injection, weak randomness, secrets in code,\n   missing checks on input from users), data loss (errors swallowed, writes\n   in the wrong order, no transaction).\n3. **Scale:** fine for one user, wrong for many: check-then-write races, the\n   same work done by every process, memory or lists that only grow, a query\n   per item, O(n^2) on big input, per-process state that must be shared.\n4. **Missing test:** risky logic (a branch, a parser, money, security, data\n   writes) with no test that fails when it breaks. One good test, not coverage.\n5. **Speed:** big slowdowns are problems. Small wins (work repeated in a hot\n   loop) are suggestions; some software counts every millisecond.\n6. **Lean:** code that should not exist or should be smaller.\n   - delete: dead code, unused options, flags and config, speculative features\n   - reuse: two helpers doing the same thing (keep one, name the path)\n   - stdlib \u002F native: the standard library or platform already does it;\n     a dependency doing what a few lines or the platform can do\n   - yagni: interface with one implementation, factory with one product,\n     wrapper that only passes calls through\n   - merge: near-copies that must change together\n   - split: one function or class doing several unrelated jobs, so it is\n     hard to read or test. Split by job, never by line count, and never into\n     helpers that exist only to make a function shorter.\n\n## 3. Check before you report\n\n- Every finding needs a concrete case: \"this input or situation leads to this\n  wrong result\". No case, no finding.\n- Before calling code unused, grep the whole tree for it, including tests,\n  fixtures, config, and string or dynamic references.\n- A shortcut marked with a `shortcut:` (or older `ponytail:`) comment that names its limit is a\n  decision, not a finding, unless the expected load already crosses it.\n- Propose the smallest fix that works. Prefer fixes that delete code. Never\n  add layers, frameworks or config the problem does not need.\n- No style taste, no \"consider\", no vague worries.\n\n## 4. Output\n\nVery simple English: short sentences, everyday words. Explain a technical\nterm the first time you use it. The reader may never have seen this code.\n\nStart with `What this repo does:` in two or three sentences, and the load\nyou assumed.\n\nThen the findings in three groups, most important first, skip empty groups:\n- **Must fix:** bug, security, data loss, breaks at the expected load.\n- **Should fix:** risky code without a test, real slowness, duplication, a\n  function that mixes jobs, code that should not exist.\n- **Nice to have:** small speed-ups, shorter forms.\n\nNumber findings across all groups, so the user can say \"fix 2 and 5\". At\nmost 20 findings; if you left smaller ones out, say how many.\nEvery finding has all four parts, each one or two short sentences:\n\n2. **Orders land on the wrong day** (`billing\u002Fclose_day.py:L40-52`)\n   - **What this is:** At midnight this job closes the day and bills all orders of that day.\n   - **Problem:** It takes \"today\" from the server clock, which runs in UTC. An order placed\n     at 00:30 in Berlin is billed on the day before.\n   - **Fix:** Compute the day once in the shop's time zone:\n     `datetime.now(ZoneInfo(\"Europe\u002FBerlin\")).date()`. One line, nothing else changes.\n   - **If we skip it:** Late orders show the wrong date, and accounting fixes them by hand.\n\nEnd with:\n- `Verdict:` one line: healthy, or what to fix first.\n- `Lean: -\u003CN> lines, -\u003CM> dependencies possible.` when lean findings exist.\n- `Not checked:` the parts you did not read or could not run.\n\nNothing found: `What this repo does:`, then `Healthy. Nothing to fix.` and\none line on what you checked.\n\nOne-shot report, changes no code.\n",{"name":5,"description":7},"main","a73152352c0612252131e5cf84e91312a6cf17dc","ai-agents\u002Fponytail-audit","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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-audit",{"tool":38,"command":39},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-audit",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill ponytail-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Fponytail-audit\u002FSKILL.md",true,[],[47,54,61,69,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":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":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]