[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CB3KCX647MN3TKFZY0E7RV":3,"skill-same:01M6CB3KCX647MN3TKFZY0E7RV":87},{"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":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6CB3KCX647MN3TKFZY0E7RV","ai-pattern-detection",null,"Review editorial phrase patterns and suggest contextual alternatives; legacy name does not imply authorship detection. Use when reviewing or editing content, or when the user mentions authenticity or natural voice.","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fwriting\u002Fskills\u002Fai-pattern-detection\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"pattern detection","detection","ai pattern detection","pattern","when","review","editorial","alternatives","authorship","authenticity","name","patterns","Legacy","use","user","editing","voice","content","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: ai-pattern-detection\ndescription: Review editorial phrase patterns and suggest contextual alternatives; legacy name does not imply authorship detection. Use when reviewing or editing content, or when the user mentions authenticity or natural voice.\nversion: 1.0.0\nplatforms: [all]\n\n---\n\n# AI Pattern Detection Skill\n\n## Purpose\n\nReview phrase patterns and suggest edits that fit the author’s intent and audience. This skill does not detect authorship or certify naturalness.\n\nThese are editorial preferences, not evidence of human or AI authorship. Apply only the requirements chosen by the author or project; other phrase and structure suggestions are advisory. Preserve quotations, code, literal terms, inventories, checklists, questionnaires, intentional punctuation, necessary uncertainty and domain terminology. A flagged phrase can be retained with a reason. Zero highlights and numeric scores are not publication gates. Never invent metrics, experiences, opinions or failures to satisfy a style marker.\n\n## When This Skill Applies\n\n- Generating any prose, documentation, or written content\n- Reviewing or editing existing documents\n- User mentions \"AI detection\", \"writing quality\", \"authentic voice\"\n- User asks to \"make it sound more natural\" or \"less robotic\"\n- Creating marketing copy, documentation, or communications\n\n## Detection Categories\n\n### Legacy High-Priority Patterns (Review in Context)\n\nThese phrases can be uninformative in some contexts; none identifies content as AI-generated:\n\n1. **Corporate Buzzwords**: \"seamlessly integrates\", \"cutting-edge\", \"revolutionary\", \"next-generation\", \"comprehensive solution\"\n2. **Vague Intensifiers**: \"dramatically improves\", \"significantly enhances\", \"vastly superior\"\n3. **Formulaic Transitions**: \"Moreover,\", \"Furthermore,\", \"Additionally,\", \"In conclusion,\"\n4. **Performative Language**: \"aims to provide\", \"strives to achieve\", \"designed to enhance\"\n5. **Academic Passive**: \"It has been observed that...\", \"It can be argued that...\"\n\n### Structural Patterns (Flag When Overused)\n\n1. **Three-item lists**: \"reliable, scalable, and secure\"\n2. **Em-dash overuse**: Multiple em-dashes in a paragraph\n3. **Identical paragraph structure**: Topic → 3 points → conclusion repeated\n4. **Balanced hedging**: \"While X has challenges, it also offers opportunities\"\n\n### Contextual Patterns (Check Frequency)\n\nReview frequency in the document and language; there is no universal acceptable ratio for these words:\n- manifest, revolutionary, next-generation\n- robust, scalable, comprehensive\n- synergy, leverage, utilize\n\n## Replacement Guidelines\n\n| Instead of | Use |\n|-----------|-----|\n| \"plays a crucial role\" | \"handles\" \u002F \"manages\" \u002F \"does\" |\n| \"seamlessly integrates\" | \"works with\" \u002F \"connects to\" |\n| \"cutting-edge\" | \"new\" \u002F \"recent\" \u002F specific tech name |\n| \"Moreover,\" | [just start the next sentence] |\n| \"comprehensive solution\" | [specific description of what it does] |\n| \"dramatically improves\" | [specific metric: \"reduces latency by 40%\"] |\n| \"robust\" | \"handles X requests\u002Fsecond\" \u002F \"99.9% uptime\" |\n\n## Editorial Features to Consider\n\nUse these only when relevant and supported by the supplied material:\n\n1. **Specific opinions**: \"I prefer X because...\" not \"X is preferred\"\n2. **Acknowledged trade-offs**: \"This approach sacrifices Y for Z\"\n3. **Real-world constraints**: \"Budget limited us to...\"\n4. **Uncertainty where appropriate**: \"We're not sure yet whether...\"\n5. **Varied sentence structure**: Mix short and long, different openings\n6. **Domain-specific vocabulary**: Use actual technical terms, not generic descriptions\n\n## Application Process\n\nWhen generating or reviewing content:\n\n1. **Scan** for phrase patterns and explicitly mandated style rules\n2. **Count** contextual pattern frequency\n3. **Check** structural variety\n4. **Suggest** edits grounded in the source; retain intentional phrasing with a reason\n5. **Verify** facts, author intent, uncertainty and protected content survive the edit\n\n## Examples\n\n### Before (Generic Wording)\n> The platform seamlessly integrates cutting-edge technology to dramatically improve workflow efficiency. Moreover, it plays a crucial role in enabling next-generation solutions. In conclusion, this comprehensive approach transforms how teams collaborate.\n\n### After (Specific Wording; Requires Supporting Facts)\n> The platform connects to existing tools through standard APIs. Initial tests show 40% faster task completion. Teams report fewer context switches between applications.\n\n## Script Reference\n\nThe Python `scripts\u002Fpattern_scanner.py` is a **legacy regex scanner**, not the contextual diagnostic implementation. It:\n- Counts pattern frequencies\n- Labels matches using legacy severity categories; these are advisory absent a user rule\n- Generates replacement suggestions\n- Preserves the deprecated numeric `authenticity_score` (0–100) and `grade` for compatibility, with a deprecation notice; neither measures authorship or publication readiness\n\nFor contextual programmatic review, use `WritingValidationEngine.diagnose(content, options)` or the exported `diagnoseWriting` API. Results include UTF-16 spans, context, explanations and reasoned exceptions. They carry `publicationGate: false`. The Python scanner does not implement these context or exception fields.\n\n## Integration\n\nThis skill works with:\n- `\u002Fwriting-validator` command for explicit validation\n- `writing-validator` agent for deep analysis\n- Content tasks when this skill is invoked; invocation is not proof of runtime integration\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fvoice-framework\u002FREADME.md — Voice framework for target style profiles\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Finstruction-comprehension.md — Parsing content requirements accurately\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002FREADME.md — SDLC framework context for documentation quality\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference for writing-related commands\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fresearch-before-decision.md — Research patterns before making writing recommendations\n","# AI Pattern Detection Skill\n\n## Purpose\n\nReview phrase patterns and suggest edits that fit the author’s intent and audience. This skill does not detect authorship or certify naturalness.\n\nThese are editorial preferences, not evidence of human or AI authorship. Apply only the requirements chosen by the author or project; other phrase and structure suggestions are advisory. Preserve quotations, code, literal terms, inventories, checklists, questionnaires, intentional punctuation, necessary uncertainty and domain terminology. A flagged phrase can be retained with a reason. Zero highlights and numeric scores are not publication gates. Never invent metrics, experiences, opinions or failures to satisfy a style marker.\n\n## When This Skill Applies\n\n- Generating any prose, documentation, or written content\n- Reviewing or editing existing documents\n- User mentions \"AI detection\", \"writing quality\", \"authentic voice\"\n- User asks to \"make it sound more natural\" or \"less robotic\"\n- Creating marketing copy, documentation, or communications\n\n## Detection Categories\n\n### Legacy High-Priority Patterns (Review in Context)\n\nThese phrases can be uninformative in some contexts; none identifies content as AI-generated:\n\n1. **Corporate Buzzwords**: \"seamlessly integrates\", \"cutting-edge\", \"revolutionary\", \"next-generation\", \"comprehensive solution\"\n2. **Vague Intensifiers**: \"dramatically improves\", \"significantly enhances\", \"vastly superior\"\n3. **Formulaic Transitions**: \"Moreover,\", \"Furthermore,\", \"Additionally,\", \"In conclusion,\"\n4. **Performative Language**: \"aims to provide\", \"strives to achieve\", \"designed to enhance\"\n5. **Academic Passive**: \"It has been observed that...\", \"It can be argued that...\"\n\n### Structural Patterns (Flag When Overused)\n\n1. **Three-item lists**: \"reliable, scalable, and secure\"\n2. **Em-dash overuse**: Multiple em-dashes in a paragraph\n3. **Identical paragraph structure**: Topic → 3 points → conclusion repeated\n4. **Balanced hedging**: \"While X has challenges, it also offers opportunities\"\n\n### Contextual Patterns (Check Frequency)\n\nReview frequency in the document and language; there is no universal acceptable ratio for these words:\n- manifest, revolutionary, next-generation\n- robust, scalable, comprehensive\n- synergy, leverage, utilize\n\n## Replacement Guidelines\n\n| Instead of | Use |\n|-----------|-----|\n| \"plays a crucial role\" | \"handles\" \u002F \"manages\" \u002F \"does\" |\n| \"seamlessly integrates\" | \"works with\" \u002F \"connects to\" |\n| \"cutting-edge\" | \"new\" \u002F \"recent\" \u002F specific tech name |\n| \"Moreover,\" | [just start the next sentence] |\n| \"comprehensive solution\" | [specific description of what it does] |\n| \"dramatically improves\" | [specific metric: \"reduces latency by 40%\"] |\n| \"robust\" | \"handles X requests\u002Fsecond\" \u002F \"99.9% uptime\" |\n\n## Editorial Features to Consider\n\nUse these only when relevant and supported by the supplied material:\n\n1. **Specific opinions**: \"I prefer X because...\" not \"X is preferred\"\n2. **Acknowledged trade-offs**: \"This approach sacrifices Y for Z\"\n3. **Real-world constraints**: \"Budget limited us to...\"\n4. **Uncertainty where appropriate**: \"We're not sure yet whether...\"\n5. **Varied sentence structure**: Mix short and long, different openings\n6. **Domain-specific vocabulary**: Use actual technical terms, not generic descriptions\n\n## Application Process\n\nWhen generating or reviewing content:\n\n1. **Scan** for phrase patterns and explicitly mandated style rules\n2. **Count** contextual pattern frequency\n3. **Check** structural variety\n4. **Suggest** edits grounded in the source; retain intentional phrasing with a reason\n5. **Verify** facts, author intent, uncertainty and protected content survive the edit\n\n## Examples\n\n### Before (Generic Wording)\n> The platform seamlessly integrates cutting-edge technology to dramatically improve workflow efficiency. Moreover, it plays a crucial role in enabling next-generation solutions. In conclusion, this comprehensive approach transforms how teams collaborate.\n\n### After (Specific Wording; Requires Supporting Facts)\n> The platform connects to existing tools through standard APIs. Initial tests show 40% faster task completion. Teams report fewer context switches between applications.\n\n## Script Reference\n\nThe Python `scripts\u002Fpattern_scanner.py` is a **legacy regex scanner**, not the contextual diagnostic implementation. It:\n- Counts pattern frequencies\n- Labels matches using legacy severity categories; these are advisory absent a user rule\n- Generates replacement suggestions\n- Preserves the deprecated numeric `authenticity_score` (0–100) and `grade` for compatibility, with a deprecation notice; neither measures authorship or publication readiness\n\nFor contextual programmatic review, use `WritingValidationEngine.diagnose(content, options)` or the exported `diagnoseWriting` API. Results include UTF-16 spans, context, explanations and reasoned exceptions. They carry `publicationGate: false`. The Python scanner does not implement these context or exception fields.\n\n## Integration\n\nThis skill works with:\n- `\u002Fwriting-validator` command for explicit validation\n- `writing-validator` agent for deep analysis\n- Content tasks when this skill is invoked; invocation is not proof of runtime integration\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fvoice-framework\u002FREADME.md — Voice framework for target style profiles\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Finstruction-comprehension.md — Parsing content requirements accurately\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002FREADME.md — SDLC framework context for documentation quality\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference for writing-related commands\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fresearch-before-decision.md — Research patterns before making writing recommendations\n",{"name":5,"version":47,"namespace":48,"platforms":49,"description":7},"1.0.0","aiwg",[50],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fwriting\u002Fskills\u002Fai-pattern-detection",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-14 10:46:34",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add jmagly\u002Faiwg --skill ai-pattern-detection",{"tool":67,"command":68},"bunx","bunx skills add jmagly\u002Faiwg --skill ai-pattern-detection",{"tool":70,"command":71},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill ai-pattern-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fwriting\u002Fskills\u002Fai-pattern-detection\u002FSKILL.md",true,[75,81],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fquick-patterns.md","REFERENCE","参考文档",1189,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fwriting\u002Fskills\u002Fai-pattern-detection\u002Freferences\u002Fquick-patterns.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fpattern_scanner.py","SCRIPT","脚本",7821,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fwriting\u002Fskills\u002Fai-pattern-detection\u002Fscripts\u002Fpattern_scanner.py",[88,116,140,146,153,167],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":95,"publishedAt":42},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[94],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":42},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,99,130,104,131,132,106,133,96,134,108,135,136,111,112,137,138,139],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":141,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":42},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[144],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[98,96,97,107,99,115,102,101,110,103,104,105,106,114,108,109,100,111,112,113],{"skillNo":147,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":152,"publishedAt":42},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[150,151],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[128,127,111,130,104,131,106,129,96,134,108,135,136,99,112,133,132,137,138,139],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":42},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,164,165,166],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":42},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[173],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,135,177,162],"pi","pi local","duplicate"]