[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77PN73WAF08PCWBYXST9BW6":3,"skill-same:01M77PN73WAF08PCWBYXST9BW6":52},{"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},"01M77PN73WAF08PCWBYXST9BW6","no-ai-slop",null,"Strip AI-slop patterns from a draft while preserving the writer's voice, or detect slop without rewriting. Use as the mandatory final pass on any copy before shipping, when the user wants a draft clearer\u002Fless AI-sounding, or when asked \"is this AI slop?\", \"audit this writing\", \"does this read as AI\".","Necmttn\u002Fskills","Necmttn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5212808?v=4","01M77PDTX0P2888A46VQ6DREZG","Neco","01M77PDTXNATPR101437VV6H7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fno-ai-slop\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: no-ai-slop\ndescription: Strip AI-slop patterns from a draft while preserving the writer's voice, or detect slop without rewriting. Use as the mandatory final pass on any copy before shipping, when the user wants a draft clearer\u002Fless AI-sounding, or when asked \"is this AI slop?\", \"audit this writing\", \"does this read as AI\".\n---\n\n# No AI slop\n\nSharp human editor. Preserve the point and the personal voice. Remove AI patterns without\nsanding distinctive writing into generic polished prose.\n\nAdapted from petergyang\u002Fno-ai-slop (MIT, https:\u002F\u002Fgithub.com\u002Fpetergyang\u002Fno-ai-slop), merged\nwith the local tell bank at `~\u002F.claude\u002Fagents\u002Fcopy-wiki-examples.md`.\n\n## Two jobs\n\n**Edit (default).** Make the minimum effective edit with the rules below. Return the full\nedited draft plus a short **What changed** section.\n\n**Detect.** The user asks whether a piece is AI slop, or asks to audit\u002Fscan\u002Fflag without\nrewriting. Name each pattern that appears, quote the offending line, give the fix in a few\nwords. Do not rewrite. Do not score the draft. Do not guess whether AI wrote it - detectors\nguess, named patterns are evidence the user can check. Offer to edit after.\n\n## Before editing\n\n- No draft provided: ask for it.\n- Audience or format unclear: ask one question - who is this for, where does it publish?\n- Goal unclear: ask what the reader should think, feel, or do after reading.\n\n## Editing principles\n\n- **Preserve the writer's real voice.** First note the draft's vocabulary, cadence,\n  bluntness, humor, uncertainty, digressions, level of polish. Keep the traits that feel\n  personal. Do not make every paragraph equally tidy.\n- **Minimum effective edit.** Fix slop, errors, repetition, unclear passages. Leave strong\n  human sentences alone. Cutting must be proportional to the actual slop.\n- **Lead with the point when the setup adds nothing.** Keep a personal aside, story, or\n  admission when it creates context, tension, or character.\n- **Front-load only when it improves clarity.** Do not force every section into the same\n  point-detail-background shape.\n- **Keep the user's meaning.** Never invent claims, examples, stats, quotes, or opinions.\n  Unclear beats invented - ask.\n- **Open it up, don't dumb it down.** Strip jargon, long sentences, abstract nouns, tangled\n  structure. Keep substance, nuance, precision.\n- **Active voice, human subjects.** \"The team shipped it Tuesday\", not \"the decision emerged\".\n- **Be concrete.** \"The integration cut deploy time from 40 minutes to 4\" beats \"improved\n  efficiency\". Protect the specific fact; never smooth a useful detail into generic importance.\n- **Verbs do the work.** \"decided\" over \"made a decision\". \"can\" over \"has the ability to\".\n- **Preserve edge.** Strong opinions, blunt language, humor, profanity, self-interruptions,\n  honest admissions stay when they belong to the writer.\n- **Keep structure unless it hurts the piece.** If you reorganize, say why in What changed.\n\n## Words to cut\n\nBanned: delve, foster, leverage, utilize, facilitate, empower, streamline, robust,\ncutting-edge, paradigm shift, game changer, this is huge, this changes everything, tapestry,\nrealm, beacon, multifaceted, meticulous, intricate, paramount, transformative, elevate,\nembark, supercharge, harness, ever-evolving, unlock, seamless, effortlessly.\n\nOften-empty adverbs: just, literally, honestly, simply, actually, truly, fundamentally,\nimportantly, crucially, inherently, inevitably.\n\nOften-empty phrases: it's worth noting, it's important to note, at the end of the day, when\nit comes to, at its core, in today's world, in the age of, in the world of, the reality is,\nthe truth is, in terms of, with regard to, in order to, going forward, in this article,\nlet's dive in.\n\nAdverbs and phrases are defaults, not absolutes. Keep one when it carries real emphasis,\nuncertainty, contrast, or the writer's spoken rhythm.\n\n## Patterns to cut\n\n**Binary contrasts.** \"This is not X. It's Y.\" \u002F \"The question isn't X, it's Y.\" \u002F \"not just\nX but Y\". State Y directly. \"The question isn't the model. It's the eval.\" becomes \"The eval\nmatters more than the model.\"\n\n**Throat-clearing openers.** \"Here's the thing\", \"Here's what I mean\", \"Let me be clear\",\n\"I'll be honest\", \"The uncomfortable truth is\". Cut, state the point.\n\n**Faux-insight setups.** \"What most people get wrong\", \"Here's what nobody tells you\", \"The\npart everyone misses\". These flatter the writer as lone expert. \"The part everyone misses:\ndistribution is the real moat\" becomes \"Distribution is the moat.\"\n\n**Colon reveals.** Noun phrase, colon, lowercase dramatic reveal: \"The best part: it learns.\"\nRewrite as a plain sentence. Colons are for lists, labels, quotes, not fake drama. Sentence\ncase after a colon unless grammar, a proper noun, a title, or code says otherwise.\n\n**Superficial analysis.** Trailing -ing clauses that pretend to explain meaning: highlighting,\nunderscoring, reflecting, showcasing. \"adds file search, highlighting the team's commitment\nto better workflows\" becomes \"adds file search, so users can find old drafts without leaving\nthe editor.\"\n\n**Importance puffery.** \"stands as a testament\", \"marks a pivotal moment\", \"plays a vital\nrole\", \"solidifies its position\". State the fact, let the reader judge.\n\n**Weasel attribution.** \"Experts agree\", \"studies show\", \"many argue\", \"industry reports\nsuggest\". Name the source or cut the claim. No source: ask, never invent one.\n\n**Fake-strong verbs.** Prefer \"is\" and \"has\" when clearer. \"serves as a centralized hub for\nsponsor management\" becomes \"tracks sponsors, drafts, due dates, and approvals in one place.\"\n\n**Synonym cycling.** Repeat the right word. \"The agent reviews the draft. The assistant\nscores the piece. The tool suggests fixes\" becomes \"The agent reviews the draft, scores it,\nand suggests fixes.\"\n\n**Negative listing.** \"Not a X. Not a Y. A Z.\" Just say Z.\n\n**Dramatic fragmentation.** \"X. And Y. And Z.\" \u002F \"That's it. That's the whole thing.\"\nUse complete sentences.\n\n**Robotic rhythm.** Repeated sentence shapes, identical paragraph structures, stacked punchy\nfragments, forced rule-of-three. Vary shape only when it helps the point.\n\n**Rhetorical setups.** \"What if I told you\", \"Think about it:\", \"Plot twist:\", self-answered\n\"Question? Answer.\" pairs. Drop them.\n\n**Fake-profound kickers.** Cut the final deep line that turns the point into a metaphor or\nmic-drop. Do not rewrite it into a better metaphor. Do not preserve the rhythm. Delete it and\nend on the clearest concrete sentence already in the draft, or a plain takeaway or next action.\n\n**Summary-recap endings.** \"In conclusion\", \"Ultimately\", \"Overall\", or a closing paragraph\nthat restates the piece. The reader was just there.\n\n**Formatting slop.** Emoji in headings, bold sprinkled mid-sentence, bullets where two\nsentences of prose read better, headers over two-sentence sections, Title Case headings.\nFormat follows content, it does not decorate it.\n\n**Em dashes.** None in short copy. One or two in a long draft only when they clearly beat\ncommas, periods, or parentheses. This user's harness blocks them outright, so use hyphens.\n\n**Pasted-LLM artifacts.** Strip `contentReference`, `oaicite`, `oai_citation`, `turn0search0`,\nstray `:::`, stray `+1`, curly quotes where straight quotes belong (especially in code).\n\n## Workflow\n\n1. Read the whole draft first.\n2. Name the core point and 3-5 voice signals to preserve (vocabulary, cadence, bluntness,\n   humor, uncertainty, digressions). Keep this note internal. Can't find the core point: ask.\n3. Detect request: return the findings report from Two jobs and stop.\n4. Edit request: make the minimum effective changes, then Read\n   `~\u002F.claude\u002Fskills\u002Fno-ai-slop\u002Feval.md` and check the result against every item yourself.\n   No separate evaluator agent needed. If the file is unreadable, self-check against the\n   Editing principles and Patterns to cut sections above and say the eval file was missing.\n5. Any check fails: fix and re-run the checks.\n6. Output the full edited draft plus a short **What changed** section.\n\n## Local taste bank\n\n`~\u002F.claude\u002Fagents\u002Fcopy-wiki-examples.md` holds curated tells T1-T21 as BAD to GOOD pairs plus\nuser-contributed examples. User examples outrank everything here, they are this user's real\ncalls. When the user labels copy good or bad, append it there in the same BAD \u002F GOOD \u002F Why\nshape with the date.\n","# No AI slop\n\nSharp human editor. Preserve the point and the personal voice. Remove AI patterns without\nsanding distinctive writing into generic polished prose.\n\nAdapted from petergyang\u002Fno-ai-slop (MIT, https:\u002F\u002Fgithub.com\u002Fpetergyang\u002Fno-ai-slop), merged\nwith the local tell bank at `~\u002F.claude\u002Fagents\u002Fcopy-wiki-examples.md`.\n\n## Two jobs\n\n**Edit (default).** Make the minimum effective edit with the rules below. Return the full\nedited draft plus a short **What changed** section.\n\n**Detect.** The user asks whether a piece is AI slop, or asks to audit\u002Fscan\u002Fflag without\nrewriting. Name each pattern that appears, quote the offending line, give the fix in a few\nwords. Do not rewrite. Do not score the draft. Do not guess whether AI wrote it - detectors\nguess, named patterns are evidence the user can check. Offer to edit after.\n\n## Before editing\n\n- No draft provided: ask for it.\n- Audience or format unclear: ask one question - who is this for, where does it publish?\n- Goal unclear: ask what the reader should think, feel, or do after reading.\n\n## Editing principles\n\n- **Preserve the writer's real voice.** First note the draft's vocabulary, cadence,\n  bluntness, humor, uncertainty, digressions, level of polish. Keep the traits that feel\n  personal. Do not make every paragraph equally tidy.\n- **Minimum effective edit.** Fix slop, errors, repetition, unclear passages. Leave strong\n  human sentences alone. Cutting must be proportional to the actual slop.\n- **Lead with the point when the setup adds nothing.** Keep a personal aside, story, or\n  admission when it creates context, tension, or character.\n- **Front-load only when it improves clarity.** Do not force every section into the same\n  point-detail-background shape.\n- **Keep the user's meaning.** Never invent claims, examples, stats, quotes, or opinions.\n  Unclear beats invented - ask.\n- **Open it up, don't dumb it down.** Strip jargon, long sentences, abstract nouns, tangled\n  structure. Keep substance, nuance, precision.\n- **Active voice, human subjects.** \"The team shipped it Tuesday\", not \"the decision emerged\".\n- **Be concrete.** \"The integration cut deploy time from 40 minutes to 4\" beats \"improved\n  efficiency\". Protect the specific fact; never smooth a useful detail into generic importance.\n- **Verbs do the work.** \"decided\" over \"made a decision\". \"can\" over \"has the ability to\".\n- **Preserve edge.** Strong opinions, blunt language, humor, profanity, self-interruptions,\n  honest admissions stay when they belong to the writer.\n- **Keep structure unless it hurts the piece.** If you reorganize, say why in What changed.\n\n## Words to cut\n\nBanned: delve, foster, leverage, utilize, facilitate, empower, streamline, robust,\ncutting-edge, paradigm shift, game changer, this is huge, this changes everything, tapestry,\nrealm, beacon, multifaceted, meticulous, intricate, paramount, transformative, elevate,\nembark, supercharge, harness, ever-evolving, unlock, seamless, effortlessly.\n\nOften-empty adverbs: just, literally, honestly, simply, actually, truly, fundamentally,\nimportantly, crucially, inherently, inevitably.\n\nOften-empty phrases: it's worth noting, it's important to note, at the end of the day, when\nit comes to, at its core, in today's world, in the age of, in the world of, the reality is,\nthe truth is, in terms of, with regard to, in order to, going forward, in this article,\nlet's dive in.\n\nAdverbs and phrases are defaults, not absolutes. Keep one when it carries real emphasis,\nuncertainty, contrast, or the writer's spoken rhythm.\n\n## Patterns to cut\n\n**Binary contrasts.** \"This is not X. It's Y.\" \u002F \"The question isn't X, it's Y.\" \u002F \"not just\nX but Y\". State Y directly. \"The question isn't the model. It's the eval.\" becomes \"The eval\nmatters more than the model.\"\n\n**Throat-clearing openers.** \"Here's the thing\", \"Here's what I mean\", \"Let me be clear\",\n\"I'll be honest\", \"The uncomfortable truth is\". Cut, state the point.\n\n**Faux-insight setups.** \"What most people get wrong\", \"Here's what nobody tells you\", \"The\npart everyone misses\". These flatter the writer as lone expert. \"The part everyone misses:\ndistribution is the real moat\" becomes \"Distribution is the moat.\"\n\n**Colon reveals.** Noun phrase, colon, lowercase dramatic reveal: \"The best part: it learns.\"\nRewrite as a plain sentence. Colons are for lists, labels, quotes, not fake drama. Sentence\ncase after a colon unless grammar, a proper noun, a title, or code says otherwise.\n\n**Superficial analysis.** Trailing -ing clauses that pretend to explain meaning: highlighting,\nunderscoring, reflecting, showcasing. \"adds file search, highlighting the team's commitment\nto better workflows\" becomes \"adds file search, so users can find old drafts without leaving\nthe editor.\"\n\n**Importance puffery.** \"stands as a testament\", \"marks a pivotal moment\", \"plays a vital\nrole\", \"solidifies its position\". State the fact, let the reader judge.\n\n**Weasel attribution.** \"Experts agree\", \"studies show\", \"many argue\", \"industry reports\nsuggest\". Name the source or cut the claim. No source: ask, never invent one.\n\n**Fake-strong verbs.** Prefer \"is\" and \"has\" when clearer. \"serves as a centralized hub for\nsponsor management\" becomes \"tracks sponsors, drafts, due dates, and approvals in one place.\"\n\n**Synonym cycling.** Repeat the right word. \"The agent reviews the draft. The assistant\nscores the piece. The tool suggests fixes\" becomes \"The agent reviews the draft, scores it,\nand suggests fixes.\"\n\n**Negative listing.** \"Not a X. Not a Y. A Z.\" Just say Z.\n\n**Dramatic fragmentation.** \"X. And Y. And Z.\" \u002F \"That's it. That's the whole thing.\"\nUse complete sentences.\n\n**Robotic rhythm.** Repeated sentence shapes, identical paragraph structures, stacked punchy\nfragments, forced rule-of-three. Vary shape only when it helps the point.\n\n**Rhetorical setups.** \"What if I told you\", \"Think about it:\", \"Plot twist:\", self-answered\n\"Question? Answer.\" pairs. Drop them.\n\n**Fake-profound kickers.** Cut the final deep line that turns the point into a metaphor or\nmic-drop. Do not rewrite it into a better metaphor. Do not preserve the rhythm. Delete it and\nend on the clearest concrete sentence already in the draft, or a plain takeaway or next action.\n\n**Summary-recap endings.** \"In conclusion\", \"Ultimately\", \"Overall\", or a closing paragraph\nthat restates the piece. The reader was just there.\n\n**Formatting slop.** Emoji in headings, bold sprinkled mid-sentence, bullets where two\nsentences of prose read better, headers over two-sentence sections, Title Case headings.\nFormat follows content, it does not decorate it.\n\n**Em dashes.** None in short copy. One or two in a long draft only when they clearly beat\ncommas, periods, or parentheses. This user's harness blocks them outright, so use hyphens.\n\n**Pasted-LLM artifacts.** Strip `contentReference`, `oaicite`, `oai_citation`, `turn0search0`,\nstray `:::`, stray `+1`, curly quotes where straight quotes belong (especially in code).\n\n## Workflow\n\n1. Read the whole draft first.\n2. Name the core point and 3-5 voice signals to preserve (vocabulary, cadence, bluntness,\n   humor, uncertainty, digressions). Keep this note internal. Can't find the core point: ask.\n3. Detect request: return the findings report from Two jobs and stop.\n4. Edit request: make the minimum effective changes, then Read\n   `~\u002F.claude\u002Fskills\u002Fno-ai-slop\u002Feval.md` and check the result against every item yourself.\n   No separate evaluator agent needed. If the file is unreadable, self-check against the\n   Editing principles and Patterns to cut sections above and say the eval file was missing.\n5. Any check fails: fix and re-run the checks.\n6. Output the full edited draft plus a short **What changed** section.\n\n## Local taste bank\n\n`~\u002F.claude\u002Fagents\u002Fcopy-wiki-examples.md` holds curated tells T1-T21 as BAD to GOOD pairs plus\nuser-contributed examples. User examples outrank everything here, they are this user's real\ncalls. When the user labels copy good or bad, append it there in the same BAD \u002F GOOD \u002F Why\nshape with the date.\n",{"name":5,"description":7},"main","b321807e50f72ccb0df5da9aaeba42088271907e","skills\u002Fpersonal\u002Fno-ai-slop","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills","https:\u002F\u002Fgithub.com\u002FNecmttn","https:\u002F\u002Fnecmttn.com","Fractional CTO - \r\nAI Solution Architect","2026-11-07 08:05:35",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Necmttn\u002Fskills --skill no-ai-slop",{"tool":38,"command":39},"bunx","bunx skills add Necmttn\u002Fskills --skill no-ai-slop",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Necmttn\u002Fskills --skill no-ai-slop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fno-ai-slop\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"eval.md","REFERENCE","参考文档",3000,"https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fno-ai-slop\u002Feval.md",[53,60,67,74,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77PNJ1JCKWHR2XJDBX8Q85P","wiki","Recall from the personal LLM wiki at ~\u002Fwiki. Use when the user asks what the wiki says, wants prior thinking\u002Fintuition on a concept, or when grounding a design or decision in previously synthesized knowledge. Read-only - never writes to the wiki.","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fwiki\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77PNERKEH3ZN11HMC6YEH9G","wiki-ingest","Curate a source into the personal LLM wiki at ~\u002Fwiki following its SCHEMA.md - a file, URL, research output, ax session, or a pending ~\u002Fwiki\u002Finbox\u002F brief. Use when the user says \"add this to the wiki\", \"ingest this\", \"promote the inbox\", or after research worth keeping long-term.","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fwiki-ingest\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77PNB9SMTTG3D80BXGCY16B","wiki-harvest","Propose-only sweep of recent coding sessions (via the ax CLI) for recurring concepts that are missing from, or should update, the personal LLM wiki at ~\u002Fwiki. Writes candidate briefs to ~\u002Fwiki\u002Finbox\u002F only - never wiki pages. Use on schedule or when the user asks \"harvest the wiki\" or \"what concepts am I repeating\".","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fwiki-harvest\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M77PN2H1QTPD9GD6VBJ3YBPN","aso-appstore-screenshots","Generate high-converting App Store screenshots by analyzing your app's codebase, discovering core benefits, and creating ASO-optimized screenshot images using Nano Banana Pro.","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmisc\u002Faso-appstore-screenshots\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmisc\u002Faso-appstore-screenshots\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M77PMVGA58GA46JCFJW2JH5X","app-idea","Run a new or existing consumer\u002FAI app idea through the golden-track playbook (~\u002Fwiki\u002Fplaybook\u002Fapps.md) from intake to verdict, write a verdict card, stop for the owner, and ratchet owner overrides back into the doctrine. Use when the user shares an app idea, asks \"should I build X\", \"audit \u003Capp>\", \"re-score \u003Capp>\", or pastes an idea in a product context. Never builds; never promotes a rule on its own.","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmisc\u002Fapp-idea\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M77PMP1976GANF1TD1EH6ZDS","wrap-up","Close down a work session or agent pane cleanly - review the work against every dimension (complete, edge cases, correct, consistent, production ready, goals met), land or file everything of value (follow-up tickets for loose ends, concerns, debt), add human-verification items to a `uat`-labeled checklist issue (builds to verify, flows to smoke), then do safe-only housekeeping (pushed worktrees, own background processes, created sims) and report what was closed, filed, and kept. Use when a session's work is done and the user says \"wrap up\", \"close this down\", \"can we close this\", \"clean up and land it\", when a fleet run or chunk finishes, or before ending a long session that minted resources.","https:\u002F\u002Fgithub.com\u002FNecmttn\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fwrap-up\u002FSKILL.md",[],[]]