[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YDB752ZKVBZ28XJMSRZ27":3,"skill-same:01M79YDB752ZKVBZ28XJMSRZ27":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M79YDB752ZKVBZ28XJMSRZ27","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.","Blind-Striker\u002Fagent-skills-and-plugins","Blind-Striker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965259?v=4","01M79WFXTE5PH0C1VB7B54ANMN","Deniz İrgin","01M79WFXV5KZ5GST1K8G035DM5",1,"MIT","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fplugins\u002Fdeniz-process\u002Fskills\u002Fponytail-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ponytail-audit\ndescription: \"Quality audit of a whole repo: bugs, security holes, what breaks\n  under real load, risky code without tests, slow paths, and what to delete,\n  merge or split. Ranked, each finding explained in plain English. One-shot\n  report, changes nothing.\"\ndisable-model-invocation: true\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,"disable-model-invocation":24},true,"master","b30b1c1908dbc56a8184128f18803053d762ccb5","plugins\u002Fdeniz-process\u002Fskills\u002Fponytail-audit",0,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins","https:\u002F\u002Fgithub.com\u002FBlind-Striker","denizirgin.com","VP of Engineering - \r\n@armutcom @homeruntech @prontopro\r\n |  Speaker \r\n@CodeFiction\r\n, http:\u002F\u002Fcodefiction.tech | Developer, gamer, blogger, maiden iron fan","2026-11-13 00:23:18",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill ponytail-audit",{"tool":40,"command":41},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill ponytail-audit",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill ponytail-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fplugins\u002Fdeniz-process\u002Fskills\u002Fponytail-audit\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M79YGWBJ52PHMSTKJ3RJ3AWR","writing-tunit-tests","Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fwriting-tunit-tests\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79YGR3Y9RCRS6TD71D0KKP8","dotnet-walls","Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fdotnet-walls\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79YGFNJBST7D803NQW3SBYM","csharp-15","Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`\u002F`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15\u002Fpreview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`\u002Fflag loop exits or capacity\u002Fcomparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121\u002FCS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fcsharp-15\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},"01M79YGAV031473HSX6FN87ENH","verified-waves","Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fverified-waves\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},"01M79YG6QXNND4WRPP3GATSY8J","harness","The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fharness\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},"01M79YG2P5S91SDTA5912XJ4FV","delegating-to-worker-models","Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fdelegating-to-worker-models\u002FSKILL.md",[],[]]