[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJWERB2RM1ZAPZVC1KANW5":3,"skill-same:01M7DJWERB2RM1ZAPZVC1KANW5":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7DJWERB2RM1ZAPZVC1KANW5","maestro-humanizer",null,"Use when editing or reviewing prose that sounds AI-written because of inflated claims, sales language, vague sources, repetitive structure, stock phrases, passive voice, filler or chatbot artifacts, while preserving its meaning and the writer's voice.","Orchestration-Maestro\u002Fmaestro-manifests","Orchestration-Maestro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F322897002?v=4","01M7DJV5QYHV5358EX4AGZJZK3","01M7DJV5RPB4CBJZBKV9AHREM6",0,"MIT","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-humanizer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maestro-humanizer\ndescription: \"Use when editing or reviewing prose that sounds AI-written because of inflated claims, sales language, vague sources, repetitive structure, stock phrases, passive voice, filler or chatbot artifacts, while preserving its meaning and the writer's voice.\"\n---\n\n# Review prose without changing its claims\n\nRewrite AI-sounding text so it reads like the writer, not a chatbot. Do not change what it says or make up details.\n\nThe patterns below come from Wikipedia's [\"Signs of AI writing\"](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup.\n\n## What to do\n\nWhen given text to humanize:\n\n1. **Find AI patterns.** Check the text against the patterns below.\n2. **Keep every claim.** You may shorten dull parts, expand useful parts, and merge or split paragraphs. Keep the information even when you change the structure.\n3. **Do not invent facts.** Do not add a fact, name, number, date, quote, or citation unless it comes from the source or the user. If a sentence needs a missing detail, ask for it or use a simpler sentence. You may add an opinion or reaction when the writer's voice calls for one, but you may not add a factual claim. Fiction is exempt because invented details are part of the task.\n4. **Match the voice.** Use the right tone for the text, such as formal, casual, or technical. Add personality only when the text and the writer call for it.\n\nThe input type controls what you return. See [How to return the result](#how-to-return-the-result). Use the same rewrite process in every mode.\n\n## Match the writer's voice\n\nIf the user provides a writing sample (their own previous writing), analyze it before rewriting:\n\n1. Read the sample first. Note its sentence length, word choice, paragraph openings, punctuation, repeated phrases, and transitions.\n2. Match those habits. Do not replace casual words with formal ones or remove deliberate quirks.\n3. If there is no sample, use the guidance below.\n\nA writing sample takes priority over these style rules. If the sample uses em dashes, keep them at about the same rate. Do not apply §14 as a ban.\n\n## Add personality only when it fits\n\nRemoving AI patterns is only half the job. The result should still sound like a person.\n\nUse personality in blog posts, essays, opinions, and personal writing when it fits the writer. Keep reference, technical, legal, and factual text neutral. Do not add opinions or first-person language where they do not belong.\n\nWhen personality fits, keep the writer's opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never invent facts to make the text feel personal.\n\nAll examples below are illustrative, not historical claims. In a real edit, retain only facts\nprovided by the input; an example is not permission to invent a citation.\n\n## Content patterns\n\n### 1. Inflated claims about importance and legacy\n\n**Words to watch:** historic breakthrough, defining achievement, lasting influence, central contribution, sweeping change. Check whether the source actually supports the scale claimed.\n**Problem:** AI writing often claims that ordinary details mark a major change, prove a legacy, or reflect a broad trend.\n**Before:**\n> The example library opened a catalogue desk in May, a defining achievement that reshaped access to local knowledge.\n**After:**\n> The example library opened a catalogue desk in May.\n\n### 2. Name-dropping to prove importance\n\n**Words to watch:** independent coverage, local\u002Fregional\u002Fnational media outlets, written by a leading expert, active social media presence\n**Problem:** AI writing often lists well-known publications or follower counts to prove that a person matters. The list usually gives no useful context.\n**Before:**\n> The example consultant appears in several famous magazines and has an enormous audience, proving her authority. The supplied interview quotes her advice to retain an audit trail.\n**After:**\n> The supplied interview quotes the consultant's advice to retain an audit trail.\n\nIf the source explains what the person said and where, keep that useful citation. Do not invent context for a shorter version.\n\n### 3. Shallow analysis with -ing phrases\n\n**Words to watch:** highlighting\u002Funderscoring\u002Femphasizing..., ensuring..., reflecting\u002Fsymbolizing..., contributing to..., cultivating\u002Ffostering..., encompassing..., showcasing...\n**Problem:** AI writing often adds an -ing phrase to make a simple fact sound deeper than it is.\n**Before:**\n> The example form uses blue headings, reflecting a commitment to clarity and fostering a culture of confident decisions.\n**After:**\n> The example form uses blue headings.\n\n### 4. Sales language\n\n**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning\n**Problem:** AI writing often sounds like an advertisement, especially when it describes places, culture, products, or organizations.\n**Before:**\n> Our breathtaking workspace boasts a revolutionary dashboard showing team assignments for effortless team success.\n**After:**\n> The workspace has a dashboard showing team assignments.\n\n### 5. Vague sources\n\n**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources\u002Fpublications (when few cited)\n**Problem:** AI writing often assigns a claim to unnamed experts, critics, reports, or observers.\n**Before:**\n> Observers say the example queue is vital to organizational resilience. The supplied operations report says it retains jobs after a restart.\n**After:**\n> The supplied operations report says the example queue retains jobs after a restart.\n\nName a real source when the source text provides one. Otherwise, remove the unsupported claim. Never invent a source.\n\n### 6. Formulaic challenges and outlook sections\n\n**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook\n**Problem:** AI articles often add a stock section about challenges, future prospects, or continued growth. These sections usually repeat vague claims instead of adding facts.\n**Before:**\n> Despite these challenges, the example club looks ahead to a dynamic future of continued growth. Its room booking still fails on Mondays.\n**After:**\n> The example club cannot book its room on Mondays.\n\nAdd details such as dates or public actions only when they come from the source or the user.\n\n## Language and grammar patterns\n\n### 7. Overused AI words\n\n**Words to inspect in clusters:** delve, tapestry, pivotal, showcase, underscore. Keep established technical vocabulary, including literal gate\u002Fgating terminology; frequency and context matter more than any one word.\n**Problem:** AI writing uses these words much more often than most people do, especially in groups.\n**Before:**\n> Additionally, the portal showcases an intricate tapestry of workflows, underscoring its pivotal role in helping staff find receipts.\n**After:**\n> Staff use the portal to find receipts.\n\n### 8. Avoiding is and are\n\n**Words to watch:** serves as\u002Fstands as\u002Fmarks\u002Frepresents [a], boasts\u002Ffeatures\u002Foffers [a]\n**Problem:** AI writing often replaces simple verbs such as *is*, *are*, and *has* with longer phrases.\n**Before:**\n> The example ledger serves as the record of payments and boasts a search field.\n**After:**\n> The example ledger is the record of payments and has a search field.\n\n### 9. Not X but Y and clipped negative endings\n\n**Problem:** AI writing overuses forms such as \"Not only...but...\" and \"It's not just X, it's Y.\"\n\nIt also adds clipped endings such as \"no guessing\" instead of writing a clear clause.\n**Before:**\n> The example alert tells the operator that a job failed. It is not just a message; it is a promise of awareness, not merely a notification but a transformation.\n**After:**\n> The example alert tells the operator that a job failed.\n**Before (tailing negation):**\n> The selected account supplies the address, no guessing.\n**After:**\n> The selected account supplies the address, so the user does not have to guess it.\n\n### 10. Forced groups of three\n\n**Problem:** AI writing often forces ideas into groups of three to sound complete.\n**Before:**\n> The example meeting promises knowledge, momentum, and connection, alongside a demonstration and questions.\n**After:**\n> The meeting includes a demonstration and questions.\n\n### 11. Changing names and repeating sentence openings\n\n**Problem:** AI writing handles repetition by rule instead of by ear. It may keep renaming the same person or thing. It may also start several sentences with the same subject, often *she* or *he*.\n\nUse one clear name for the same subject. For repeated openings, merge sentences, change the subject when that helps, or begin with the action.\n**Before (synonym cycling):**\n> The reader opens a record. The consumer checks its status. The client then returns the entry.\n**After:**\n> The reader opens a record, checks its status, and returns it.\n**Before (repeated openings):**\n> He read the label. He read the date. He read the note.\n**After:**\n> He read the label, date, and note.\n\nDo not ban the repeated word. Fix the repeated sentence pattern. The remaining sentence may still start with \"She.\"\n\n### 12. False from X to Y ranges\n\n**Problem:** AI writing often uses \"from X to Y\" when X and Y do not form a real range.\n**Before:**\n> This guide covers source files and gives examples of using them, taking us from source files to limitless creativity.\n**After:**\n> This guide covers source files and gives examples of using them.\n\n### 13. Passive voice and missing subjects\n\n**Problem:** AI writing often hides who acts or drops the subject. Use active voice when it makes the actor and action clearer.\n**Before:**\n> No password needed. The entry is saved automatically by the example application.\n**After:**\n> You do not need a password. The example application saves the entry automatically.\n\n## Style patterns\n\n### 14. Em and en dashes\n\n**Rule:** The final rewrite must not contain em dashes (—) or en dashes (–), unless the writer's sample uses them. Replace a dash with a period, comma, colon, or parentheses, or rewrite the sentence. Also check for spaced dashes (` — `) and double hyphens (` -- `) used as dashes.\n**Before:**\n> The setting—enabled by default—applies to new records—unless the owner opts out.\n**After:**\n> The setting is enabled by default and applies to new records unless the owner opts out.\n**Before:**\n> The form — changed yesterday — now accepts empty notes. Existing records -- still readable -- need no edits.\n**After:**\n> The form, changed yesterday, now accepts empty notes. Existing records are still readable and need no edits.\n\nBefore returning the rewrite, search for `—` and `–`. Remove each one unless the writer's sample uses that mark. In that case, match the sample's rate.\n\n### 15. Too much bold text\n\n**Problem:** AI chatbots often bold words and phrases without a clear reason.\n**Before:**\n> The example view includes **search**, **sorting**, and **filters**.\n**After:**\n> The example view includes search, sorting, and filters.\n\n### 16. Lists with bold mini-headings\n\n**Problem:** AI writing often uses vertical lists in which every item starts with a bold label and a colon.\n**Before:**\n> - **Labels:** Labels can be edited.\n> - **Dates:** Dates can be sorted.\n> - **Notes:** Notes can be searched.\n**After:**\n> You can edit labels, sort dates, and search notes.\n\n### 17. Title case in headings\n\n**Problem:** AI chatbots often capitalize every main word in a heading.\n**Before:**\n> ## How To Read The Example Ledger\n**After:**\n> ## How to read the example ledger\n\n### 18. Emojis\n\n**Problem:** AI chatbots often add emojis to headings and list items as decoration.\n**Before:**\n> 🚀 Launch the example\n> ✅ Check the saved record\n**After:**\n> Launch the example and check the saved record.\n\n### 19. Curly quotation marks\n\n**Problem:** An assistant may use curly quotes (“...”) where the writer or target format uses straight quotes (\"...\").\n**Before:**\n> The note says “record saved” after the write.\n**After:**\n> The note says \"record saved\" after the write.\n\n## Chatbot patterns\n\n### 20. Chatbot text left in the answer\n\n**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., Want me to...?, Want me to give examples?, Should I continue?, let me know, here is a...\n**Problem:** A chatbot's greeting, offer, or closing sometimes remains in text that should stand on its own.\n**Before:**\n> Of course! The example file format contains a header and ordered records. Let me know if you want more details!\n**After:**\n> The example file format contains a header and ordered records.\n\n### 21. Knowledge-limit disclaimers and guesses\n\n**Words to watch:** my training ended, sources are sparse, apparently lived, perhaps attended, probably began. Check whether an admission of missing evidence is followed by an unsupported biography or other guess.\n**Problem:** Older models may mention the date when their knowledge ends. A model may also explain that it could not find a source, then fill the gap with a plausible guess. State what the source does not show, or remove the sentence. Do not present a guess as a fact.\n**Before (cutoff disclaimer):**\n> As of my last update, the supplied notes do not give the example group's founding date.\n**After:**\n> The supplied notes do not give the example group's founding date.\n**Before (speculative gap-fill):**\n> The supplied notes contain no account of the example author's childhood, perhaps because she values privacy and grew up far from a city.\n**After:**\n> The supplied notes contain no account of the example author's childhood.\n\n### 22. Overly agreeable tone\n\n**Problem:** AI assistants often praise the user or agree before giving the answer.\n**Before:**\n> Excellent point! You are absolutely right that the example error does not identify the missing field.\n**After:**\n> The example error does not identify the missing field.\n\n## Filler and hedging\n\n### 23. Filler phrases\n\n**Before → After:**\n\n- \"For the purpose of reading records\" → \"To read records\"\n- \"On account of the missing file\" → \"Because the file is missing\"\n- \"During the present period\" → \"Now\"\n- \"Should a failure be encountered\" → \"If it fails\"\n- \"The reader possesses the capacity to parse\" → \"The reader can parse\"\n- \"A point worth mentioning is that the test fails\" → \"The test fails\"\n\n### 24. Too many qualifiers\n\n**Phrases to watch:** to be fair, it's also possible, could potentially, might arguably, in some cases it may, this is an inference\n**Problem:** Repeated editing can add one qualifier after another until every claim sounds uncertain. Keep a qualifier only when the source supports it and the meaning needs it. Remove caveats that only repair an earlier overstatement.\n**Before:**\n> The change could potentially perhaps reduce delays in some cases.\n**After:**\n> The change may reduce delays.\n\n### 25. Generic positive endings\n\n**Problem:** AI writing often ends with vague optimism instead of the last useful fact.\n**Before:**\n> This improvement begins an exciting journey toward a brighter future for the example project.\n**After:**\n> (Delete the send-off. End with the last supported result or concrete plan.)\n\n### 26. Too many hyphenated word pairs\n\n**Words to watch:** third-party, cross-functional, client-facing, data-driven, decision-making, well-known, high-quality, real-time, long-term, end-to-end\n**Problem:** AI writing often hyphenates these pairs everywhere. Keep the hyphen before a noun when grammar needs it, as in `a high-quality report`. Drop it after the noun, as in `the report is high quality`.\n**Before:**\n> The well-tested parser is well-tested, and the real-time view updates in real-time.\n**After:**\n> The well-tested parser has tests, and the real-time view updates in real time.\n\n### 27. Pretending to reveal a deeper truth\n\n**Phrases to watch:** The real question is, at its core, in reality, what really matters, fundamentally, the deeper issue, the heart of the matter\n**Problem:** AI writing uses these phrases to make an ordinary point sound like a hidden truth.\n**Before:**\n> At its core, the deeper truth is that the example import needs a filename.\n**After:**\n> The example import needs a filename.\n\n### 28. Announcing the next point\n\n**Phrases to watch:** Let's dive in, let's explore, let's break this down, here's what you need to know, now let's look at, without further ado, heads up, quick note, before I forget\n**Problem:** AI writing often announces the next point instead of stating it. A casual phrase such as \"one thing that bit me\" can have the same problem. Remove the announcement, not just its formal tone.\n**Before:**\n> Let us explore what you need to know about the example reader: it accepts a path and returns ordered records.\n**After:**\n> The example reader accepts a path and returns ordered records.\n**Before (casual register):**\n> One thing that caught me out, so listen closely: the example cache stores successful lookups only.\n**After:**\n> The example cache stores successful lookups only.\n\n### 29. A heading repeated in the first sentence\n\n**Signs to watch:** A heading followed by a one-line paragraph that simply restates the heading before the real content begins.\n**Problem:** AI writing often follows a heading with a sentence that only repeats the heading. Remove the repeated sentence.\n**Before:**\n> ## Errors\n>\n> Errors matter.\n>\n> A missing field returns its name to the caller.\n**After:**\n> ## Errors\n>\n> A missing field returns its name to the caller.\n\n### 30. Writing about the previous version\n\n**Problem:** Documentation and comments should describe the current behavior. Mention the previous version only in change logs, release notes, migration guides, and other documents about change.\n**Before:**\n> This lookup replaced the old loop and was added to improve the previous implementation by using an index to avoid scanning every record.\n**After:**\n> The lookup uses an index to avoid scanning every record.\n\n### 31. Forced punchlines and dramatic fragments\n\n**Problem:** AI writing often turns each sentence into a dramatic closing line. One short sentence can add emphasis. A row of short fragments usually feels forced.\n**Before:**\n> Then the import completed. No pauses for manual approval. No hesitation. No looking back. The old world was gone.\n**After:**\n> The import completed without pausing for manual approval.\n\n### 32. Formulaic sayings\n\n**Words to watch:** X is the Y of Z, X becomes a trap, X is not a tool but a mirror, the language of, the currency of, the architecture of\n**Problem:** AI writing often turns an ordinary claim into a saying that sounds deep but adds no detail. Replace the saying with the specific claim.\n**Before:**\n> Simplicity is the currency of confidence. The form is a mirror, not a tool. It has fewer fields, so the reviewer has less to check.\n**After:**\n> The form has fewer fields, so the reviewer has less to check.\n\n### 33. Fake-candid openings\n\n**Phrases to watch:** Honestly?, Look, Here's the thing, The thing is, Let's be honest, Real talk, when used as standalone hooks or fake-candid pauses before an ordinary point.\n**Problem:** AI writing often starts with a staged pause or claim of honesty before making a routine point. State the point directly.\n**Before:**\n> Is the example worth keeping? Honestly? That depends on whether anyone uses it.\n**After:**\n> Whether the example is worth keeping depends on whether anyone uses it.\n\n### 34. Answering objections no one raised\n\n**Phrases to watch:** This isn't (mainly\u002Freally) about, I'm not saying\u002Farguing\u002Ftrying to, To be clear, Don't get me wrong, This is not to say, You could argue\u002Fframe this differently but, Some might say... but\n**Problem:** AI writing may answer an objection that does not appear in the text. Watch for an unattributed statement about what the writer does not mean, especially when the topic appears nowhere else. A direct claim such as \"the API is not thread-safe\" is not this pattern.\n**Before:**\n> To be clear, I am not saying that documentation has no value. This is not about perfection. The link points to a missing file.\n**After:**\n> The link points to a missing file.\n\nRemove only the unsupported defense. If it contains a real claim, state that claim directly. Keep an objection when the text names its source or answers it in full.\n\n### 35. Rejecting fake alternatives\n\n**Phrases to watch:** A tempting option\u002Fapproach would be, One might be tempted to, An obvious approach would be, You might think... but, It would be easy to just, Some would suggest\n**Problem:** AI writing may introduce an option that no reader would consider, reject it in a clause, and never mention it again. This often leaves an old drafting idea in the final text. Remove the fake option and state the real constraint directly.\n**Before:**\n> An obvious alternative would be to restart the whole machine every time, but the example only needs to reload the changed file.\n**After:**\n> The example reloads only the changed file.\n\nOne rejected option may be valid. Several short, unrelated rejections are a stronger sign. Ask what new information each sentence adds. If it only records an earlier edit, rewrite the paragraph around its main point.\n\n## Check for false positives\n\n### What not to flag\n\nA person may use some of these patterns. Do not treat any item below as proof by itself:\n\n- **Perfect grammar and consistent style.** Many writers are professionals or have been edited. Polish does not equal AI.\n- **Mixed casual and formal styles.** This can reflect the writer's field, age, or personal habits.\n- **\"Bland\" or \"robotic\" prose.** AI prose has *specific* tells. Generic dryness without those tells is just dry writing.\n- **Formal or academic words.** §7 lists specific words that AI writing overuses. Do not simplify every formal word.\n- **Letter-style opening or closing on a comment.** Salutations and sign-offs predate language-model assistants.\n- **Common transition words in isolation.** *Additionally*, *moreover*, *consequently* are AI-coded only when piled up. One *however* is not a tell.\n- **Curly quotes alone.** macOS, Word, Google Docs, and most CMSes auto-curl by default. Curly quotes only count when stacked with other tells.\n- **Em dashes alone.** Many editors and journalists use them often. Em dashes are evidence only when paired with formulaic sales-y rhythm.\n- **One short sentence for emphasis.** Flag dramatic fragments only when several appear in a row.\n- **Deliberate repeated openings.** Writers may repeat an opening to build rhythm or pressure, as in \"She came. She saw. She conquered.\" Change it only when the repetition adds nothing.\n- **\"Honestly\" or \"look\" mid-sentence.** These are ordinary in casual writing. The tell is the standalone theatrical opener, not the word itself.\n- **Useful limits and disclaimers.** Keep scope statements, legal and safety notices, real corrections, named objections, replies, and FAQ answers.\n- **Real alternatives.** Keep options that a reader may consider in a design document, tutorial, or argument. Remove only an unlikely option that the text dismisses and never uses again.\n- **Unsourced claims.** Most of the web is unsourced. Lack of citations doesn't prove anything.\n- **Correct, complex formatting.** Visual editors and templates produce clean output without any AI.\n- **Secondhand text.** Do not rewrite watched phrases inside quotations, titles, proper names, or examples where the phrase is being discussed rather than used.\n\nWhen unsure, look for several patterns together. One em dash proves nothing. Several stock patterns in the same passage are stronger evidence.\n\n### Human details to keep\n\nThese details often carry the writer's voice. Keep them unless they hurt the meaning:\n\n- **Specific, unusual details.** Keep a real address, an odd quote, or a phrase such as \"the lawyer who used to work upstairs from my dentist.\"\n- **Mixed feelings and unresolved tension.** Keep lines such as \"I think this is mostly good, but it bothers me, and I can't fully explain why.\"\n- **Dated, era-bound references.** Slang, memes, or in-jokes that map to a specific year and subculture. Models lag by a year or more.\n- **Deliberate first-person choices.** Keep a cut or word choice when the writer can explain why it belongs.\n- **Variety in sentence length.** Real writing alternates short and long. AI writing tends toward an even, mid-length cadence.\n- **Genuine asides, parentheticals, or self-corrections.** \"(I keep wanting to say 'almost' here, but it really was certain.)\" Models rarely interrupt themselves like this.\n- **Older edits.** Text predating November 30, 2022, the public launch of widely used chat assistants, is very unlikely to have been generated by one.\n\n---\n\n## How to return the result\n\n**Pasted text (default).** Return the draft, a short list of remaining AI patterns, and the final rewrite.\n\n**File mode.** When the user names a file, run the full rewrite process but write only the final text to the file. Change prose only. Keep code blocks, YAML metadata, data, and link targets unchanged. Then give the user a short summary.\n\n**Embedded mode.** When another task uses this skill for a pull request, commit message, or document, return only the final text.\n\n## Rewrite process\n\n1. Read the source and mark each AI pattern.\n2. Write a draft. Read it aloud. Check the rhythm, details, simple verbs such as *is* and *has*, and the right level of formality.\n3. Ask two questions:\n   - **\"What still sounds AI-generated?\"**\n   - **\"Did the rewrite add or remove any fact, name, number, date, quote, citation, ranking, or other claim?\"**\n   Treat any unsupported addition or lost claim as an error.\n4. Write the final version. State each point naturally instead of patching one flagged phrase at a time. If a sentence stays awkward, rewrite the paragraph around its main point. Apply the dash rule in §14.\n\nReturn the result required by [How to return the result](#how-to-return-the-result).\n\n## Source\n\nThis skill is based on [Wikipedia: Signs of AI writing](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. Its patterns come from reviews of AI-generated text on Wikipedia.\n\nTreat predictable stock phrasing as a prompt to inspect the text, not as proof of who wrote it.\n","# Review prose without changing its claims\n\nRewrite AI-sounding text so it reads like the writer, not a chatbot. Do not change what it says or make up details.\n\nThe patterns below come from Wikipedia's [\"Signs of AI writing\"](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup.\n\n## What to do\n\nWhen given text to humanize:\n\n1. **Find AI patterns.** Check the text against the patterns below.\n2. **Keep every claim.** You may shorten dull parts, expand useful parts, and merge or split paragraphs. Keep the information even when you change the structure.\n3. **Do not invent facts.** Do not add a fact, name, number, date, quote, or citation unless it comes from the source or the user. If a sentence needs a missing detail, ask for it or use a simpler sentence. You may add an opinion or reaction when the writer's voice calls for one, but you may not add a factual claim. Fiction is exempt because invented details are part of the task.\n4. **Match the voice.** Use the right tone for the text, such as formal, casual, or technical. Add personality only when the text and the writer call for it.\n\nThe input type controls what you return. See [How to return the result](#how-to-return-the-result). Use the same rewrite process in every mode.\n\n## Match the writer's voice\n\nIf the user provides a writing sample (their own previous writing), analyze it before rewriting:\n\n1. Read the sample first. Note its sentence length, word choice, paragraph openings, punctuation, repeated phrases, and transitions.\n2. Match those habits. Do not replace casual words with formal ones or remove deliberate quirks.\n3. If there is no sample, use the guidance below.\n\nA writing sample takes priority over these style rules. If the sample uses em dashes, keep them at about the same rate. Do not apply §14 as a ban.\n\n## Add personality only when it fits\n\nRemoving AI patterns is only half the job. The result should still sound like a person.\n\nUse personality in blog posts, essays, opinions, and personal writing when it fits the writer. Keep reference, technical, legal, and factual text neutral. Do not add opinions or first-person language where they do not belong.\n\nWhen personality fits, keep the writer's opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never invent facts to make the text feel personal.\n\nAll examples below are illustrative, not historical claims. In a real edit, retain only facts\nprovided by the input; an example is not permission to invent a citation.\n\n## Content patterns\n\n### 1. Inflated claims about importance and legacy\n\n**Words to watch:** historic breakthrough, defining achievement, lasting influence, central contribution, sweeping change. Check whether the source actually supports the scale claimed.\n**Problem:** AI writing often claims that ordinary details mark a major change, prove a legacy, or reflect a broad trend.\n**Before:**\n> The example library opened a catalogue desk in May, a defining achievement that reshaped access to local knowledge.\n**After:**\n> The example library opened a catalogue desk in May.\n\n### 2. Name-dropping to prove importance\n\n**Words to watch:** independent coverage, local\u002Fregional\u002Fnational media outlets, written by a leading expert, active social media presence\n**Problem:** AI writing often lists well-known publications or follower counts to prove that a person matters. The list usually gives no useful context.\n**Before:**\n> The example consultant appears in several famous magazines and has an enormous audience, proving her authority. The supplied interview quotes her advice to retain an audit trail.\n**After:**\n> The supplied interview quotes the consultant's advice to retain an audit trail.\n\nIf the source explains what the person said and where, keep that useful citation. Do not invent context for a shorter version.\n\n### 3. Shallow analysis with -ing phrases\n\n**Words to watch:** highlighting\u002Funderscoring\u002Femphasizing..., ensuring..., reflecting\u002Fsymbolizing..., contributing to..., cultivating\u002Ffostering..., encompassing..., showcasing...\n**Problem:** AI writing often adds an -ing phrase to make a simple fact sound deeper than it is.\n**Before:**\n> The example form uses blue headings, reflecting a commitment to clarity and fostering a culture of confident decisions.\n**After:**\n> The example form uses blue headings.\n\n### 4. Sales language\n\n**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning\n**Problem:** AI writing often sounds like an advertisement, especially when it describes places, culture, products, or organizations.\n**Before:**\n> Our breathtaking workspace boasts a revolutionary dashboard showing team assignments for effortless team success.\n**After:**\n> The workspace has a dashboard showing team assignments.\n\n### 5. Vague sources\n\n**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources\u002Fpublications (when few cited)\n**Problem:** AI writing often assigns a claim to unnamed experts, critics, reports, or observers.\n**Before:**\n> Observers say the example queue is vital to organizational resilience. The supplied operations report says it retains jobs after a restart.\n**After:**\n> The supplied operations report says the example queue retains jobs after a restart.\n\nName a real source when the source text provides one. Otherwise, remove the unsupported claim. Never invent a source.\n\n### 6. Formulaic challenges and outlook sections\n\n**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook\n**Problem:** AI articles often add a stock section about challenges, future prospects, or continued growth. These sections usually repeat vague claims instead of adding facts.\n**Before:**\n> Despite these challenges, the example club looks ahead to a dynamic future of continued growth. Its room booking still fails on Mondays.\n**After:**\n> The example club cannot book its room on Mondays.\n\nAdd details such as dates or public actions only when they come from the source or the user.\n\n## Language and grammar patterns\n\n### 7. Overused AI words\n\n**Words to inspect in clusters:** delve, tapestry, pivotal, showcase, underscore. Keep established technical vocabulary, including literal gate\u002Fgating terminology; frequency and context matter more than any one word.\n**Problem:** AI writing uses these words much more often than most people do, especially in groups.\n**Before:**\n> Additionally, the portal showcases an intricate tapestry of workflows, underscoring its pivotal role in helping staff find receipts.\n**After:**\n> Staff use the portal to find receipts.\n\n### 8. Avoiding is and are\n\n**Words to watch:** serves as\u002Fstands as\u002Fmarks\u002Frepresents [a], boasts\u002Ffeatures\u002Foffers [a]\n**Problem:** AI writing often replaces simple verbs such as *is*, *are*, and *has* with longer phrases.\n**Before:**\n> The example ledger serves as the record of payments and boasts a search field.\n**After:**\n> The example ledger is the record of payments and has a search field.\n\n### 9. Not X but Y and clipped negative endings\n\n**Problem:** AI writing overuses forms such as \"Not only...but...\" and \"It's not just X, it's Y.\"\n\nIt also adds clipped endings such as \"no guessing\" instead of writing a clear clause.\n**Before:**\n> The example alert tells the operator that a job failed. It is not just a message; it is a promise of awareness, not merely a notification but a transformation.\n**After:**\n> The example alert tells the operator that a job failed.\n**Before (tailing negation):**\n> The selected account supplies the address, no guessing.\n**After:**\n> The selected account supplies the address, so the user does not have to guess it.\n\n### 10. Forced groups of three\n\n**Problem:** AI writing often forces ideas into groups of three to sound complete.\n**Before:**\n> The example meeting promises knowledge, momentum, and connection, alongside a demonstration and questions.\n**After:**\n> The meeting includes a demonstration and questions.\n\n### 11. Changing names and repeating sentence openings\n\n**Problem:** AI writing handles repetition by rule instead of by ear. It may keep renaming the same person or thing. It may also start several sentences with the same subject, often *she* or *he*.\n\nUse one clear name for the same subject. For repeated openings, merge sentences, change the subject when that helps, or begin with the action.\n**Before (synonym cycling):**\n> The reader opens a record. The consumer checks its status. The client then returns the entry.\n**After:**\n> The reader opens a record, checks its status, and returns it.\n**Before (repeated openings):**\n> He read the label. He read the date. He read the note.\n**After:**\n> He read the label, date, and note.\n\nDo not ban the repeated word. Fix the repeated sentence pattern. The remaining sentence may still start with \"She.\"\n\n### 12. False from X to Y ranges\n\n**Problem:** AI writing often uses \"from X to Y\" when X and Y do not form a real range.\n**Before:**\n> This guide covers source files and gives examples of using them, taking us from source files to limitless creativity.\n**After:**\n> This guide covers source files and gives examples of using them.\n\n### 13. Passive voice and missing subjects\n\n**Problem:** AI writing often hides who acts or drops the subject. Use active voice when it makes the actor and action clearer.\n**Before:**\n> No password needed. The entry is saved automatically by the example application.\n**After:**\n> You do not need a password. The example application saves the entry automatically.\n\n## Style patterns\n\n### 14. Em and en dashes\n\n**Rule:** The final rewrite must not contain em dashes (—) or en dashes (–), unless the writer's sample uses them. Replace a dash with a period, comma, colon, or parentheses, or rewrite the sentence. Also check for spaced dashes (` — `) and double hyphens (` -- `) used as dashes.\n**Before:**\n> The setting—enabled by default—applies to new records—unless the owner opts out.\n**After:**\n> The setting is enabled by default and applies to new records unless the owner opts out.\n**Before:**\n> The form — changed yesterday — now accepts empty notes. Existing records -- still readable -- need no edits.\n**After:**\n> The form, changed yesterday, now accepts empty notes. Existing records are still readable and need no edits.\n\nBefore returning the rewrite, search for `—` and `–`. Remove each one unless the writer's sample uses that mark. In that case, match the sample's rate.\n\n### 15. Too much bold text\n\n**Problem:** AI chatbots often bold words and phrases without a clear reason.\n**Before:**\n> The example view includes **search**, **sorting**, and **filters**.\n**After:**\n> The example view includes search, sorting, and filters.\n\n### 16. Lists with bold mini-headings\n\n**Problem:** AI writing often uses vertical lists in which every item starts with a bold label and a colon.\n**Before:**\n> - **Labels:** Labels can be edited.\n> - **Dates:** Dates can be sorted.\n> - **Notes:** Notes can be searched.\n**After:**\n> You can edit labels, sort dates, and search notes.\n\n### 17. Title case in headings\n\n**Problem:** AI chatbots often capitalize every main word in a heading.\n**Before:**\n> ## How To Read The Example Ledger\n**After:**\n> ## How to read the example ledger\n\n### 18. Emojis\n\n**Problem:** AI chatbots often add emojis to headings and list items as decoration.\n**Before:**\n> 🚀 Launch the example\n> ✅ Check the saved record\n**After:**\n> Launch the example and check the saved record.\n\n### 19. Curly quotation marks\n\n**Problem:** An assistant may use curly quotes (“...”) where the writer or target format uses straight quotes (\"...\").\n**Before:**\n> The note says “record saved” after the write.\n**After:**\n> The note says \"record saved\" after the write.\n\n## Chatbot patterns\n\n### 20. Chatbot text left in the answer\n\n**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., Want me to...?, Want me to give examples?, Should I continue?, let me know, here is a...\n**Problem:** A chatbot's greeting, offer, or closing sometimes remains in text that should stand on its own.\n**Before:**\n> Of course! The example file format contains a header and ordered records. Let me know if you want more details!\n**After:**\n> The example file format contains a header and ordered records.\n\n### 21. Knowledge-limit disclaimers and guesses\n\n**Words to watch:** my training ended, sources are sparse, apparently lived, perhaps attended, probably began. Check whether an admission of missing evidence is followed by an unsupported biography or other guess.\n**Problem:** Older models may mention the date when their knowledge ends. A model may also explain that it could not find a source, then fill the gap with a plausible guess. State what the source does not show, or remove the sentence. Do not present a guess as a fact.\n**Before (cutoff disclaimer):**\n> As of my last update, the supplied notes do not give the example group's founding date.\n**After:**\n> The supplied notes do not give the example group's founding date.\n**Before (speculative gap-fill):**\n> The supplied notes contain no account of the example author's childhood, perhaps because she values privacy and grew up far from a city.\n**After:**\n> The supplied notes contain no account of the example author's childhood.\n\n### 22. Overly agreeable tone\n\n**Problem:** AI assistants often praise the user or agree before giving the answer.\n**Before:**\n> Excellent point! You are absolutely right that the example error does not identify the missing field.\n**After:**\n> The example error does not identify the missing field.\n\n## Filler and hedging\n\n### 23. Filler phrases\n\n**Before → After:**\n\n- \"For the purpose of reading records\" → \"To read records\"\n- \"On account of the missing file\" → \"Because the file is missing\"\n- \"During the present period\" → \"Now\"\n- \"Should a failure be encountered\" → \"If it fails\"\n- \"The reader possesses the capacity to parse\" → \"The reader can parse\"\n- \"A point worth mentioning is that the test fails\" → \"The test fails\"\n\n### 24. Too many qualifiers\n\n**Phrases to watch:** to be fair, it's also possible, could potentially, might arguably, in some cases it may, this is an inference\n**Problem:** Repeated editing can add one qualifier after another until every claim sounds uncertain. Keep a qualifier only when the source supports it and the meaning needs it. Remove caveats that only repair an earlier overstatement.\n**Before:**\n> The change could potentially perhaps reduce delays in some cases.\n**After:**\n> The change may reduce delays.\n\n### 25. Generic positive endings\n\n**Problem:** AI writing often ends with vague optimism instead of the last useful fact.\n**Before:**\n> This improvement begins an exciting journey toward a brighter future for the example project.\n**After:**\n> (Delete the send-off. End with the last supported result or concrete plan.)\n\n### 26. Too many hyphenated word pairs\n\n**Words to watch:** third-party, cross-functional, client-facing, data-driven, decision-making, well-known, high-quality, real-time, long-term, end-to-end\n**Problem:** AI writing often hyphenates these pairs everywhere. Keep the hyphen before a noun when grammar needs it, as in `a high-quality report`. Drop it after the noun, as in `the report is high quality`.\n**Before:**\n> The well-tested parser is well-tested, and the real-time view updates in real-time.\n**After:**\n> The well-tested parser has tests, and the real-time view updates in real time.\n\n### 27. Pretending to reveal a deeper truth\n\n**Phrases to watch:** The real question is, at its core, in reality, what really matters, fundamentally, the deeper issue, the heart of the matter\n**Problem:** AI writing uses these phrases to make an ordinary point sound like a hidden truth.\n**Before:**\n> At its core, the deeper truth is that the example import needs a filename.\n**After:**\n> The example import needs a filename.\n\n### 28. Announcing the next point\n\n**Phrases to watch:** Let's dive in, let's explore, let's break this down, here's what you need to know, now let's look at, without further ado, heads up, quick note, before I forget\n**Problem:** AI writing often announces the next point instead of stating it. A casual phrase such as \"one thing that bit me\" can have the same problem. Remove the announcement, not just its formal tone.\n**Before:**\n> Let us explore what you need to know about the example reader: it accepts a path and returns ordered records.\n**After:**\n> The example reader accepts a path and returns ordered records.\n**Before (casual register):**\n> One thing that caught me out, so listen closely: the example cache stores successful lookups only.\n**After:**\n> The example cache stores successful lookups only.\n\n### 29. A heading repeated in the first sentence\n\n**Signs to watch:** A heading followed by a one-line paragraph that simply restates the heading before the real content begins.\n**Problem:** AI writing often follows a heading with a sentence that only repeats the heading. Remove the repeated sentence.\n**Before:**\n> ## Errors\n>\n> Errors matter.\n>\n> A missing field returns its name to the caller.\n**After:**\n> ## Errors\n>\n> A missing field returns its name to the caller.\n\n### 30. Writing about the previous version\n\n**Problem:** Documentation and comments should describe the current behavior. Mention the previous version only in change logs, release notes, migration guides, and other documents about change.\n**Before:**\n> This lookup replaced the old loop and was added to improve the previous implementation by using an index to avoid scanning every record.\n**After:**\n> The lookup uses an index to avoid scanning every record.\n\n### 31. Forced punchlines and dramatic fragments\n\n**Problem:** AI writing often turns each sentence into a dramatic closing line. One short sentence can add emphasis. A row of short fragments usually feels forced.\n**Before:**\n> Then the import completed. No pauses for manual approval. No hesitation. No looking back. The old world was gone.\n**After:**\n> The import completed without pausing for manual approval.\n\n### 32. Formulaic sayings\n\n**Words to watch:** X is the Y of Z, X becomes a trap, X is not a tool but a mirror, the language of, the currency of, the architecture of\n**Problem:** AI writing often turns an ordinary claim into a saying that sounds deep but adds no detail. Replace the saying with the specific claim.\n**Before:**\n> Simplicity is the currency of confidence. The form is a mirror, not a tool. It has fewer fields, so the reviewer has less to check.\n**After:**\n> The form has fewer fields, so the reviewer has less to check.\n\n### 33. Fake-candid openings\n\n**Phrases to watch:** Honestly?, Look, Here's the thing, The thing is, Let's be honest, Real talk, when used as standalone hooks or fake-candid pauses before an ordinary point.\n**Problem:** AI writing often starts with a staged pause or claim of honesty before making a routine point. State the point directly.\n**Before:**\n> Is the example worth keeping? Honestly? That depends on whether anyone uses it.\n**After:**\n> Whether the example is worth keeping depends on whether anyone uses it.\n\n### 34. Answering objections no one raised\n\n**Phrases to watch:** This isn't (mainly\u002Freally) about, I'm not saying\u002Farguing\u002Ftrying to, To be clear, Don't get me wrong, This is not to say, You could argue\u002Fframe this differently but, Some might say... but\n**Problem:** AI writing may answer an objection that does not appear in the text. Watch for an unattributed statement about what the writer does not mean, especially when the topic appears nowhere else. A direct claim such as \"the API is not thread-safe\" is not this pattern.\n**Before:**\n> To be clear, I am not saying that documentation has no value. This is not about perfection. The link points to a missing file.\n**After:**\n> The link points to a missing file.\n\nRemove only the unsupported defense. If it contains a real claim, state that claim directly. Keep an objection when the text names its source or answers it in full.\n\n### 35. Rejecting fake alternatives\n\n**Phrases to watch:** A tempting option\u002Fapproach would be, One might be tempted to, An obvious approach would be, You might think... but, It would be easy to just, Some would suggest\n**Problem:** AI writing may introduce an option that no reader would consider, reject it in a clause, and never mention it again. This often leaves an old drafting idea in the final text. Remove the fake option and state the real constraint directly.\n**Before:**\n> An obvious alternative would be to restart the whole machine every time, but the example only needs to reload the changed file.\n**After:**\n> The example reloads only the changed file.\n\nOne rejected option may be valid. Several short, unrelated rejections are a stronger sign. Ask what new information each sentence adds. If it only records an earlier edit, rewrite the paragraph around its main point.\n\n## Check for false positives\n\n### What not to flag\n\nA person may use some of these patterns. Do not treat any item below as proof by itself:\n\n- **Perfect grammar and consistent style.** Many writers are professionals or have been edited. Polish does not equal AI.\n- **Mixed casual and formal styles.** This can reflect the writer's field, age, or personal habits.\n- **\"Bland\" or \"robotic\" prose.** AI prose has *specific* tells. Generic dryness without those tells is just dry writing.\n- **Formal or academic words.** §7 lists specific words that AI writing overuses. Do not simplify every formal word.\n- **Letter-style opening or closing on a comment.** Salutations and sign-offs predate language-model assistants.\n- **Common transition words in isolation.** *Additionally*, *moreover*, *consequently* are AI-coded only when piled up. One *however* is not a tell.\n- **Curly quotes alone.** macOS, Word, Google Docs, and most CMSes auto-curl by default. Curly quotes only count when stacked with other tells.\n- **Em dashes alone.** Many editors and journalists use them often. Em dashes are evidence only when paired with formulaic sales-y rhythm.\n- **One short sentence for emphasis.** Flag dramatic fragments only when several appear in a row.\n- **Deliberate repeated openings.** Writers may repeat an opening to build rhythm or pressure, as in \"She came. She saw. She conquered.\" Change it only when the repetition adds nothing.\n- **\"Honestly\" or \"look\" mid-sentence.** These are ordinary in casual writing. The tell is the standalone theatrical opener, not the word itself.\n- **Useful limits and disclaimers.** Keep scope statements, legal and safety notices, real corrections, named objections, replies, and FAQ answers.\n- **Real alternatives.** Keep options that a reader may consider in a design document, tutorial, or argument. Remove only an unlikely option that the text dismisses and never uses again.\n- **Unsourced claims.** Most of the web is unsourced. Lack of citations doesn't prove anything.\n- **Correct, complex formatting.** Visual editors and templates produce clean output without any AI.\n- **Secondhand text.** Do not rewrite watched phrases inside quotations, titles, proper names, or examples where the phrase is being discussed rather than used.\n\nWhen unsure, look for several patterns together. One em dash proves nothing. Several stock patterns in the same passage are stronger evidence.\n\n### Human details to keep\n\nThese details often carry the writer's voice. Keep them unless they hurt the meaning:\n\n- **Specific, unusual details.** Keep a real address, an odd quote, or a phrase such as \"the lawyer who used to work upstairs from my dentist.\"\n- **Mixed feelings and unresolved tension.** Keep lines such as \"I think this is mostly good, but it bothers me, and I can't fully explain why.\"\n- **Dated, era-bound references.** Slang, memes, or in-jokes that map to a specific year and subculture. Models lag by a year or more.\n- **Deliberate first-person choices.** Keep a cut or word choice when the writer can explain why it belongs.\n- **Variety in sentence length.** Real writing alternates short and long. AI writing tends toward an even, mid-length cadence.\n- **Genuine asides, parentheticals, or self-corrections.** \"(I keep wanting to say 'almost' here, but it really was certain.)\" Models rarely interrupt themselves like this.\n- **Older edits.** Text predating November 30, 2022, the public launch of widely used chat assistants, is very unlikely to have been generated by one.\n\n---\n\n## How to return the result\n\n**Pasted text (default).** Return the draft, a short list of remaining AI patterns, and the final rewrite.\n\n**File mode.** When the user names a file, run the full rewrite process but write only the final text to the file. Change prose only. Keep code blocks, YAML metadata, data, and link targets unchanged. Then give the user a short summary.\n\n**Embedded mode.** When another task uses this skill for a pull request, commit message, or document, return only the final text.\n\n## Rewrite process\n\n1. Read the source and mark each AI pattern.\n2. Write a draft. Read it aloud. Check the rhythm, details, simple verbs such as *is* and *has*, and the right level of formality.\n3. Ask two questions:\n   - **\"What still sounds AI-generated?\"**\n   - **\"Did the rewrite add or remove any fact, name, number, date, quote, citation, ranking, or other claim?\"**\n   Treat any unsupported addition or lost claim as an error.\n4. Write the final version. State each point naturally instead of patching one flagged phrase at a time. If a sentence stays awkward, rewrite the paragraph around its main point. Apply the dash rule in §14.\n\nReturn the result required by [How to return the result](#how-to-return-the-result).\n\n## Source\n\nThis skill is based on [Wikipedia: Signs of AI writing](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FWikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. Its patterns come from reviews of AI-generated text on Wikipedia.\n\nTreat predictable stock phrasing as a prompt to inspect the text, not as proof of who wrote it.\n",{"name":5,"description":7},"main","f33b1a1de12042270a260ffdddd74b67671a1d9a","manifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-humanizer","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro","Automated guardrails for faster, better, more maintainable and more secure code. Our Northstar: never reached, always pursued.","2026-11-09 01:08:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-humanizer",{"tool":36,"command":37},"bunx","bunx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-humanizer",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-humanizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-humanizer\u002FSKILL.md",true,[],[45,52,57,62,67,72],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DK0KB6JRRJRQPMXG075AQ6","audit","Fixture skill.","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":53,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7DK0JAQG1J25DG064S7PR27","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":58,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DK0HBNY88V2B7PF5E4JWZS","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":63,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DK0G9CB5MFGRD73SNEXXYE","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":68,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DK0FA198RVD2KCEW9YDQ6K","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":73,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7DK0EAZVV9A5CN27PD2MTMB","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002F.drafts\u002Faudit\u002FSKILL.md",[],[]]