[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EFRJM739THJR2N0GAZXDTF":3,"skill-same:01M7EFRJM739THJR2N0GAZXDTF":78},{"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":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M7EFRJM739THJR2N0GAZXDTF","case-studies",null,"Use when turning one named customer's measured win into a case study, or the attributed testimonial quote that travels with it — consent-cleared, metrics-anchored proof for the next skeptical buyer. NOT the deck that sells the vision to a room (that is `pitch-deck`), NOT thought-leadership with no single named customer (that is `article-writing`).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: case-studies\ndescription: \"Use when turning one named customer's measured win into a case study, or the attributed testimonial quote that travels with it — consent-cleared, metrics-anchored proof for the next skeptical buyer. NOT the deck that sells the vision to a room (that is `pitch-deck`), NOT thought-leadership with no single named customer (that is `article-writing`).\"\ntags: [case-study, testimonial, social-proof, customer-story, conversion]\nrecommends: [pitch-deck, article-writing, retention, review-management, brand-voice, landing-copy]\norigin: risco\n---\n\n# case-studies\n\nYou write the consent-cleared, metrics-anchored story of a customer who already won — and the short attributed quote that travels with it. Your reader is the *next* skeptical buyer, not your own marketing team. Every line either advances that buyer's decision or it is cut.\n\nA case study is a proof artifact, not a brochure. B2B buyers rank customer testimonials (55%) and case studies (54%) as top trust formats, just behind original research and peer insight (CMI\u002FMarketingProfs, *B2B Content Marketing: 2025 Benchmarks, Budgets & Trends*, Oct 2024). They are reading to de-risk a purchase. A page that praises the vendor and hides the numbers fails that job no matter how polished the prose.\n\nYou produce two linked things: the **case study** (the full Challenge → Solution → Result story) and the **portable testimonial quote** (named, titled, one claim) that gets lifted onto a landing page, a slide, or a 30-second clip.\n\n## What this produces \u002F route out first\n\nIf the request is not a single customer's measured outcome, hand it off before you write a word.\n\n| The ask | Owner |\n| --- | --- |\n| Document one customer's measured win as proof for the next buyer | **THIS skill** |\n| Sell the company vision\u002Fstory to a room or investors | `..\u002Fpitch-deck\u002FSKILL.md` |\n| Long-form \u002F SEO thought-leadership with no single named customer | `..\u002Farticle-writing\u002FSKILL.md` |\n| Keep an existing customer happy — QBR, expansion, churn-save | `..\u002Fretention\u002FSKILL.md` |\n| Solicit or reply to public reviews \u002F ratings | `..\u002Freview-management\u002FSKILL.md` |\n| The reusable cross-channel tone-of-voice rules | `..\u002Fbrand-voice\u002FSKILL.md` |\n| Drop the proven quote into a converting page | `..\u002Flanding-copy\u002FSKILL.md` |\n| Price the offer this win justifies | `pricing` |\n\nThe one-sentence call: it is a case study if a real, named customer already got a measured result and consented to be quoted.\n\n## The intake gate — STOP if any of these is missing\n\nDo not start prose until you have all three. A missing piece is a gathering task or an anonymization decision, never an invention.\n\n- **The metric set** — baseline, result, timeframe, and a money figure if the customer permits it. Why: a number with no baseline or timeframe is a claim, not a result. \"Increased revenue\" is unfalsifiable; \"€420k → €1.6M in 11 months\" is proof.\n- **The named source** — a real person with title and company for the quote. Why: an anonymous \"— a happy client\" reads as fabricated and a same-industry, named quote lifts lead quality far more than a generic one.\n- **The consent status** — written sign-off to publish the name, quote, logo, and numbers. Why: publishing an un-consented named customer is the legal failure mode, not a style miss (see below).\n\nIf you lack a metric → ask for it or do not claim it. If you lack consent → anonymize honestly (\"a 200-seat logistics SaaS\") or do not ship. Never round a vague number up to look better.\n\n## The legal + consent floor\n\nThis is the hard floor, not a nicety. The FTC Consumer Reviews and Testimonials Rule has been in force since 21 October 2024, with penalties up to ~$53,088 per violation (the FTC's max is inflation-adjusted annually — this is the figure effective 17 Jan 2025; re-check FTC.gov before quoting it as current).\n\n- **Real customer, honest statement.** No fabricated, scripted, or insider testimonial presented as an ordinary customer. If the speaker is an employee, investor, or affiliate, you must add a clear-and-conspicuous material-connection disclosure or drop the quote.\n- **Substantiation.** You may not publish a metric you cannot back with a source. If you cannot point to the data, the number does not go in.\n- **Written consent, kept.** Get sign-off before publishing the name, exact quote, logo, image, and figures. An email confirmation suffices, but it must be retained.\n- **Edit the quote only with approval.** You may tighten a quote for clarity, but the customer must approve the edited wording — you cannot change what they meant.\n\nCarry the consent state in the artifact's front-matter so it is impossible to ship a story whose status is unknown:\n\n```yaml\n---\ncustomer: \"Acme Logistics\"\nconsent: signed          # signed | pending | anonymized\napproved: 2026-05-28     # date the customer signed off on the exact quote\nquote_source: \"interview-2026-05-20.txt\"\n---\n```\n\n`consent: pending` means draft-only. `consent: anonymized` means no name\u002Flogo\u002Fidentifying detail ships. Only `consent: signed` may publish a named, quoted, imaged customer. Full intake form, consent\u002Frelease checklist, approval-email wording, substantiation and insider-disclosure notes, and the anonymization fallback rules live in `references\u002Fconsent-and-substantiation.md`.\n\n## Case-study anatomy\n\nWrite the sections in this order. Each earns its place; cut anything that does not advance the buyer's decision. Target **600–1,200 words** — long enough to prove the result, short enough that a busy buyer finishes it.\n\n1. **Results headline** — one KPI, the single most important number. Why: it is the only line many readers see. \"Fraud cut to 0.10% in 8 weeks,\" not the customer's company name.\n2. **Snapshot box** — above the fold: industry, region, products used, and the headline KPIs. Why: a skeptical buyer self-qualifies in seconds (\"same industry as us? same size?\").\n3. **Challenge** — the measurable pain before, in the customer's words. Why: the buyer must see their own problem to care about the fix.\n4. **Solution** — what was implemented and how, concrete and specific. Why: vague \"we partnered closely\" proves nothing; \"migrated 1,200 SKUs to the new pricing engine in two sprints\" proves capability.\n5. **Result** — the before\u002Fafter numbers with timeframe, as Context-Achievement-Relevance lines (below). Why: this is the proof the whole piece exists to deliver.\n6. **Attributed quote** — named + title + company, one specific claim. Why: the human voice is the conversion lever, and the quote is what travels onto other surfaces.\n7. **Decision-stage CTA** — one next step matched to where the reader now is (\"See pricing,\" \"Book a 20-min fit call\"). Why: proof with no next step wastes the intent it just built.\n\nThe ordered skeleton and a filled mini-example with real-shaped numbers are in `references\u002Fcase-study-skeleton.md`.\n\n## Metrics-first\n\nCollect the numbers before you write any prose. The story is built around the data, not decorated with it.\n\nWrite each result as a **Context → Achievement → Relevance** line: what changed, the measured lift, and what it was worth.\n\n```text\nBad:  \"The new workflow improved efficiency significantly and the team is much happier.\"\nGood: \"Restructuring lead nurturing (context) drove a 43% conversion lift (achievement),\n       generating €1.2M in additional annual revenue (relevance).\"\n\nBad:  \"We helped them process invoices faster.\"\nGood: \"Cut invoice-processing time from 6 days to 4 hours (−97%) within the first quarter.\"\n```\n\nA result that lacks a baseline or a timeframe is not a result — it is an unfalsifiable claim. Always pair before with after, and always state the window.\n\n## Testimonial \u002F quote craft\n\nThe quote is the conversion lever, so make it carry weight. Specific beats glowing. One claim per quote — a quote that says three things says nothing.\n\n```text\nBad:  \"Great product, the team is amazing, highly recommend! — a happy customer\"\nGood: \"We cut new-hire onboarding from 3 weeks to 2 days — my team stopped dreading\n       every new starter. — Ana Pérez, COO, Acme Logistics\"\n```\n\nRules:\n\n- **Named + title + company.** Attribution is what makes it believable. Anonymous quotes read as invented.\n- **Same industry wins.** A quote from the prospect's own sector lifts lead quality; match where you can.\n- **One concrete claim.** Tie the quote to a number or a felt change, not to adjectives.\n- **The customer's voice, not yours.** If it sounds like your marketing, the buyer discounts it. Approve any edit with the customer.\n\n## Format leverage — write once, cut many\n\nDefault to a repurposable structure, because video is now the top-rated B2B content format (58% rate it most effective, with case studies\u002Fcustomer stories close behind at 53% — CMI\u002FMarketingProfs *2025 Benchmarks*, Oct 2024) and testimonials are a measured conversion lever, not decoration: a three-line testimonial block lifted landing-page conversion 34% in VWO's WikiJob A\u002FB test, and Unbounce reported swapping static reviews for video testimonials lifted conversion up to 80%. From one signed-off case study you should be able to cut, with no new approval needed:\n\n- a **pull-stat card** (the headline KPI on its own),\n- a **quote card** (the attributed testimonial),\n- a **30–60s video script** (challenge in one line, result in one line, the quote read aloud).\n\nWrite the prose so these fall out cleanly; do not produce a separate brochure for each. (This is the cut, not a full video-production guide — that craft lives elsewhere.)\n\n## Anti-patterns\n\n| Bad | Good |\n| --- | --- |\n| Hero headline is the customer's company name | Hero is the result + a number (\"Churn cut 40% in one quarter\") |\n| \"Increased revenue\" with no baseline or window | baseline → result → timeframe, every time |\n| Publish the quote before the customer signs off | Exact-quote written approval first, retained |\n| Anonymous \"— a satisfied client\" | Named + title + company, or anonymize the whole story honestly |\n| Superlatives: \"revolutionary\", \"seamless\", \"best-in-class\" | Verifiable specifics with units |\n| Insider\u002Femployee quote presented as a customer | Clear material-connection disclosure, or drop it |\n| Vendor-praise narrative (\"we are proud to...\") | Buyer-serving proof (\"here is what changed for them\") |\n| One 2,500-word wall of prose | 600–1,200 words, snapshot box up top, scannable |\n| A metric you cannot source | Only published numbers you can substantiate on demand |\n\n## Verify + handoffs\n\n`scripts\u002Fverify.sh \u003Ccase-study.md>` is a read-only structural and legal lint. It checks for a quantified hero metric, the required Challenge\u002FSolution\u002FResult sections and snapshot box, an attributed quote, a before→after signal, a CTA, and the `consent:` \u002F `approved:` marker — and it warns on the superlative banlist. It **fails hard** when the hero has no metric, a core section is missing, or consent is unmarked, because shipping an un-consented named quote is the legal risk. It is structural lint only; persuasion quality is the capability eval's job and yours.\n\nHand off when the piece is done: the proven quote → `..\u002Flanding-copy\u002FSKILL.md`, the broader narrative → `..\u002Farticle-writing\u002FSKILL.md`, the slide version → `..\u002Fpitch-deck\u002FSKILL.md`, the public-review angle → `..\u002Freview-management\u002FSKILL.md`.\n","# case-studies\n\nYou write the consent-cleared, metrics-anchored story of a customer who already won — and the short attributed quote that travels with it. Your reader is the *next* skeptical buyer, not your own marketing team. Every line either advances that buyer's decision or it is cut.\n\nA case study is a proof artifact, not a brochure. B2B buyers rank customer testimonials (55%) and case studies (54%) as top trust formats, just behind original research and peer insight (CMI\u002FMarketingProfs, *B2B Content Marketing: 2025 Benchmarks, Budgets & Trends*, Oct 2024). They are reading to de-risk a purchase. A page that praises the vendor and hides the numbers fails that job no matter how polished the prose.\n\nYou produce two linked things: the **case study** (the full Challenge → Solution → Result story) and the **portable testimonial quote** (named, titled, one claim) that gets lifted onto a landing page, a slide, or a 30-second clip.\n\n## What this produces \u002F route out first\n\nIf the request is not a single customer's measured outcome, hand it off before you write a word.\n\n| The ask | Owner |\n| --- | --- |\n| Document one customer's measured win as proof for the next buyer | **THIS skill** |\n| Sell the company vision\u002Fstory to a room or investors | `..\u002Fpitch-deck\u002FSKILL.md` |\n| Long-form \u002F SEO thought-leadership with no single named customer | `..\u002Farticle-writing\u002FSKILL.md` |\n| Keep an existing customer happy — QBR, expansion, churn-save | `..\u002Fretention\u002FSKILL.md` |\n| Solicit or reply to public reviews \u002F ratings | `..\u002Freview-management\u002FSKILL.md` |\n| The reusable cross-channel tone-of-voice rules | `..\u002Fbrand-voice\u002FSKILL.md` |\n| Drop the proven quote into a converting page | `..\u002Flanding-copy\u002FSKILL.md` |\n| Price the offer this win justifies | `pricing` |\n\nThe one-sentence call: it is a case study if a real, named customer already got a measured result and consented to be quoted.\n\n## The intake gate — STOP if any of these is missing\n\nDo not start prose until you have all three. A missing piece is a gathering task or an anonymization decision, never an invention.\n\n- **The metric set** — baseline, result, timeframe, and a money figure if the customer permits it. Why: a number with no baseline or timeframe is a claim, not a result. \"Increased revenue\" is unfalsifiable; \"€420k → €1.6M in 11 months\" is proof.\n- **The named source** — a real person with title and company for the quote. Why: an anonymous \"— a happy client\" reads as fabricated and a same-industry, named quote lifts lead quality far more than a generic one.\n- **The consent status** — written sign-off to publish the name, quote, logo, and numbers. Why: publishing an un-consented named customer is the legal failure mode, not a style miss (see below).\n\nIf you lack a metric → ask for it or do not claim it. If you lack consent → anonymize honestly (\"a 200-seat logistics SaaS\") or do not ship. Never round a vague number up to look better.\n\n## The legal + consent floor\n\nThis is the hard floor, not a nicety. The FTC Consumer Reviews and Testimonials Rule has been in force since 21 October 2024, with penalties up to ~$53,088 per violation (the FTC's max is inflation-adjusted annually — this is the figure effective 17 Jan 2025; re-check FTC.gov before quoting it as current).\n\n- **Real customer, honest statement.** No fabricated, scripted, or insider testimonial presented as an ordinary customer. If the speaker is an employee, investor, or affiliate, you must add a clear-and-conspicuous material-connection disclosure or drop the quote.\n- **Substantiation.** You may not publish a metric you cannot back with a source. If you cannot point to the data, the number does not go in.\n- **Written consent, kept.** Get sign-off before publishing the name, exact quote, logo, image, and figures. An email confirmation suffices, but it must be retained.\n- **Edit the quote only with approval.** You may tighten a quote for clarity, but the customer must approve the edited wording — you cannot change what they meant.\n\nCarry the consent state in the artifact's front-matter so it is impossible to ship a story whose status is unknown:\n\n```yaml\n---\ncustomer: \"Acme Logistics\"\nconsent: signed          # signed | pending | anonymized\napproved: 2026-05-28     # date the customer signed off on the exact quote\nquote_source: \"interview-2026-05-20.txt\"\n---\n```\n\n`consent: pending` means draft-only. `consent: anonymized` means no name\u002Flogo\u002Fidentifying detail ships. Only `consent: signed` may publish a named, quoted, imaged customer. Full intake form, consent\u002Frelease checklist, approval-email wording, substantiation and insider-disclosure notes, and the anonymization fallback rules live in `references\u002Fconsent-and-substantiation.md`.\n\n## Case-study anatomy\n\nWrite the sections in this order. Each earns its place; cut anything that does not advance the buyer's decision. Target **600–1,200 words** — long enough to prove the result, short enough that a busy buyer finishes it.\n\n1. **Results headline** — one KPI, the single most important number. Why: it is the only line many readers see. \"Fraud cut to 0.10% in 8 weeks,\" not the customer's company name.\n2. **Snapshot box** — above the fold: industry, region, products used, and the headline KPIs. Why: a skeptical buyer self-qualifies in seconds (\"same industry as us? same size?\").\n3. **Challenge** — the measurable pain before, in the customer's words. Why: the buyer must see their own problem to care about the fix.\n4. **Solution** — what was implemented and how, concrete and specific. Why: vague \"we partnered closely\" proves nothing; \"migrated 1,200 SKUs to the new pricing engine in two sprints\" proves capability.\n5. **Result** — the before\u002Fafter numbers with timeframe, as Context-Achievement-Relevance lines (below). Why: this is the proof the whole piece exists to deliver.\n6. **Attributed quote** — named + title + company, one specific claim. Why: the human voice is the conversion lever, and the quote is what travels onto other surfaces.\n7. **Decision-stage CTA** — one next step matched to where the reader now is (\"See pricing,\" \"Book a 20-min fit call\"). Why: proof with no next step wastes the intent it just built.\n\nThe ordered skeleton and a filled mini-example with real-shaped numbers are in `references\u002Fcase-study-skeleton.md`.\n\n## Metrics-first\n\nCollect the numbers before you write any prose. The story is built around the data, not decorated with it.\n\nWrite each result as a **Context → Achievement → Relevance** line: what changed, the measured lift, and what it was worth.\n\n```text\nBad:  \"The new workflow improved efficiency significantly and the team is much happier.\"\nGood: \"Restructuring lead nurturing (context) drove a 43% conversion lift (achievement),\n       generating €1.2M in additional annual revenue (relevance).\"\n\nBad:  \"We helped them process invoices faster.\"\nGood: \"Cut invoice-processing time from 6 days to 4 hours (−97%) within the first quarter.\"\n```\n\nA result that lacks a baseline or a timeframe is not a result — it is an unfalsifiable claim. Always pair before with after, and always state the window.\n\n## Testimonial \u002F quote craft\n\nThe quote is the conversion lever, so make it carry weight. Specific beats glowing. One claim per quote — a quote that says three things says nothing.\n\n```text\nBad:  \"Great product, the team is amazing, highly recommend! — a happy customer\"\nGood: \"We cut new-hire onboarding from 3 weeks to 2 days — my team stopped dreading\n       every new starter. — Ana Pérez, COO, Acme Logistics\"\n```\n\nRules:\n\n- **Named + title + company.** Attribution is what makes it believable. Anonymous quotes read as invented.\n- **Same industry wins.** A quote from the prospect's own sector lifts lead quality; match where you can.\n- **One concrete claim.** Tie the quote to a number or a felt change, not to adjectives.\n- **The customer's voice, not yours.** If it sounds like your marketing, the buyer discounts it. Approve any edit with the customer.\n\n## Format leverage — write once, cut many\n\nDefault to a repurposable structure, because video is now the top-rated B2B content format (58% rate it most effective, with case studies\u002Fcustomer stories close behind at 53% — CMI\u002FMarketingProfs *2025 Benchmarks*, Oct 2024) and testimonials are a measured conversion lever, not decoration: a three-line testimonial block lifted landing-page conversion 34% in VWO's WikiJob A\u002FB test, and Unbounce reported swapping static reviews for video testimonials lifted conversion up to 80%. From one signed-off case study you should be able to cut, with no new approval needed:\n\n- a **pull-stat card** (the headline KPI on its own),\n- a **quote card** (the attributed testimonial),\n- a **30–60s video script** (challenge in one line, result in one line, the quote read aloud).\n\nWrite the prose so these fall out cleanly; do not produce a separate brochure for each. (This is the cut, not a full video-production guide — that craft lives elsewhere.)\n\n## Anti-patterns\n\n| Bad | Good |\n| --- | --- |\n| Hero headline is the customer's company name | Hero is the result + a number (\"Churn cut 40% in one quarter\") |\n| \"Increased revenue\" with no baseline or window | baseline → result → timeframe, every time |\n| Publish the quote before the customer signs off | Exact-quote written approval first, retained |\n| Anonymous \"— a satisfied client\" | Named + title + company, or anonymize the whole story honestly |\n| Superlatives: \"revolutionary\", \"seamless\", \"best-in-class\" | Verifiable specifics with units |\n| Insider\u002Femployee quote presented as a customer | Clear material-connection disclosure, or drop it |\n| Vendor-praise narrative (\"we are proud to...\") | Buyer-serving proof (\"here is what changed for them\") |\n| One 2,500-word wall of prose | 600–1,200 words, snapshot box up top, scannable |\n| A metric you cannot source | Only published numbers you can substantiate on demand |\n\n## Verify + handoffs\n\n`scripts\u002Fverify.sh \u003Ccase-study.md>` is a read-only structural and legal lint. It checks for a quantified hero metric, the required Challenge\u002FSolution\u002FResult sections and snapshot box, an attributed quote, a before→after signal, a CTA, and the `consent:` \u002F `approved:` marker — and it warns on the superlative banlist. It **fails hard** when the hero has no metric, a core section is missing, or consent is unmarked, because shipping an un-consented named quote is the legal risk. It is structural lint only; persuasion quality is the capability eval's job and yours.\n\nHand off when the piece is done: the proven quote → `..\u002Flanding-copy\u002FSKILL.md`, the broader narrative → `..\u002Farticle-writing\u002FSKILL.md`, the slide version → `..\u002Fpitch-deck\u002FSKILL.md`, the public-review angle → `..\u002Freview-management\u002FSKILL.md`.\n",{"name":5,"tags":24,"origin":30,"recommends":31,"description":7},[25,26,27,28,29],"case-study","testimonial","social-proof","customer-story","conversion","risco",[32,33,34,35,36,37],"pitch-deck","article-writing","retention","review-management","brand-voice","landing-copy","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fcase-studies",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill case-studies",{"tool":52,"command":53},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill case-studies",{"tool":55,"command":56},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill case-studies","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002FSKILL.md",true,[60,66,70,74],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"evals\u002Fcases.yaml","REFERENCE","参考文档",4170,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002Fevals\u002Fcases.yaml",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"evals\u002FREADME.md",963,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002Fevals\u002FREADME.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcase-study-skeleton.md",3438,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002Freferences\u002Fcase-study-skeleton.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fconsent-and-substantiation.md",3973,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcase-studies\u002Freferences\u002Fconsent-and-substantiation.md",[79,87,92,99,106,113],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":88,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":86},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":86},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":86},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":86},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":86},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]