[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BZRSFFCRJ9N2F5ENPRE4MH":3,"skill-same:01M6BZRSFFCRJ9N2F5ENPRE4MH":264},{"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":23,"linkOnly":24,"markdownContent":25,"markdownBody":26,"frontMatter":27,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":33,"ownerHtmlUrl":34,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M6BZRSFFCRJ9N2F5ENPRE4MH","text.humanize",null,"Remove AI-style writing patterns from text to sound more natural and human","causify-ai\u002Fhelpers","causify-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121828442?v=4","01M6BZFTHW2MQR7FWK8CDW0DRA","Causify.AI","01M6BZFTPJ193AB5N089Z82HQG",155,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftext.humanize\u002FSKILL.md",[],[19,20,21,22],"text","text humanize","writing","haiku","2026-11-10 10:12:30",false,"---\ndescription: Remove AI-style writing patterns from text to sound more natural and human\nmodel: haiku\n---\n\n# Goal\n\n- Change text with recognizable AI mannerisms (hedging, dramatic pivots, cliched\n  transitions) and clean up AI-written content that's factually correct but tonally\n  flat\n\n# What This Skill Preserves\n- Author's opinions, arguments, and claims\n- Document structure and organization\n- Paragraph and section order\n- Core meaning and facts\n- Intentional stylistic choices (fragments, unconventional punctuation, etc.)\n\n# Workflow\n\n## Core Principles\n- Edit, don't rewrite: clean up pattern slop, preserve voice, opinions,\n  structure, and meaning\n- Apply systematically: check all 19 rules below; skip only if the rule doesn't\n  apply to the text\n- Use judgment on conflicts: if a rule break serves the writing (e.g., a\n  well-placed em dash for effect), keep it\n- Change nothing else: don't reorder paragraphs, add ideas, rephrase core\n  arguments, or alter facts\n\n## Pattern Checklist\nScan for these AI markers before applying detailed rules:\n\n- Overused Words and Jargon\n  - Grandiose: \"vital\", \"pivotal\", \"groundbreaking\", \"robust\", \"comprehensive\",\n    \"nuanced\", \"multifaceted\", \"transformative\"\n  - AI vocabulary: \"delve\", \"leverage\" (verb), \"reimagine\", \"empower\", \"unpack\",\n    \"synergy\"\n- Filler and Hedges\n  - \"It's worth noting that\", \"It's important to remember\", \"It should be\n    noted\", \"Interestingly enough\"\n  - \"Something we've observed\", \"This is where X really shines\"\n- Theatrical Transitions and Pivots\n  - Throat-clearing: \"Let's dive in\", \"Let's unpack\", \"In this article, we'll\"\n  - Dramatic pivots: \"But here's the thing\", \"Here's the catch\", \"Here's what\n    most people miss\"\n  - Overused connectors: \"Furthermore\", \"Moreover\", \"Additionally\", \"In addition\n    to the above\"\n  - Rhetorical openers: \"So what does this mean for you?\", \"Why does this\n    matter?\"\n- Structural Patterns\n  - Gift-wrapped endings: \"In summary\", \"In conclusion\", \"Ultimately\", \"At the\n    end of the day\", \"Moving forward\"\n  - Exhaustive lists: 7-10 items when 3-4 would suffice\n  - Passive voice clusters: 2+ passive sentences in a row\n  - Corrective antithesis: \"Not X. But Y.\" setup-payoff constructions\n- Meta-Language and Vagueness\n  - Meta-verbs: \"highlights\", \"underscores\", \"emphasizes\", \"showcases\",\n    \"illustrates\"\n  - Vague attribution: \"some experts say\", \"widely covered\", \"significant\n    attention\"\n  - Copy-paste metaphors: same metaphor repeated word-for-word 3+ times\n\n## Rules\n\n### Rule 1: Em Dashes\n- Remove excessive em dashes (—)\n- Rewrite using commas, full stops, or restructure the sentence\n- One or two in a long piece is fine; three or more is a pattern worth fixing\n\n### Rule 2: Corrective Antithesis\n- Remove \"Not X. But Y.\" constructions where you set up something the reader\n  never assumed, then correct it for drama\n- Bad: \"This isn't because they don't trust the technology. It's because they\n  can't predict it.\"\n- Good: \"They trust the technology fine. What they can't do is predict it.\"\n\n### Rule 3: Dramatic Pivot Phrases\n- Remove theatrical pivots: \"But here's the thing\", \"Here's the catch\", \"Here's\n  the bind\", \"Here's what most people miss\"\n- Fold the point into the sentence naturally\n- Bad: \"The patterns are valuable. But here's the bind: building a tool cost\n  more than most could justify.\"\n- Good: \"The patterns are valuable but building a tool to capture them cost more\n  than most could justify.\"\n\n### Rule 4: Soft Hedging Language\n- Cut filler hedges; just say the thing\n- Remove: \"It's worth noting that\", \"Something we've observed\", \"This is where X\n  really shines\", \"It's important to remember\", \"It should be noted\",\n  \"Interestingly enough\"\n- Bad: \"It's worth noting that this approach has shown some promising results in\n  certain contexts.\"\n- Good: \"This approach works.\"\n\n### Rule 5: Overused Transition Words\n- Cut or vary \"Furthermore\", \"Moreover\", \"Additionally\", \"In addition to the\n  above\" when chained together\n- Real writers use them sparingly\n- Bad: \"The system is fast. Furthermore, it is reliable. Moreover, it is easy to\n  use. Additionally, it integrates well.\"\n- Good: \"The system is fast, reliable, easy to use, and integrates without\n  friction.\"\n\n### Rule 6: AI Vocabulary\n- Replace words AI overuses with plain alternatives\n  - \"delve\" -> explore, look at, examine\n  - \"leverage\" (verb) -> use, apply, rely on\n  - \"robust\" -> strong, solid, reliable\n  - \"comprehensive\" -> thorough, complete, full\n  - \"nuanced\" -> subtle, layered, specific\n  - \"multifaceted\" -> complex, varied\n  - \"transformative\" -> significant, major\n  - \"unpack\" -> explain, break down\n  - \"reimagine\" -> rethink, redesign\n  - \"empower\" -> let, help, enable\n\n### Rule 7: Meta-Verbs\n- Don't say something \"highlights\", \"underscores\", \"emphasizes\", \"showcases\", or\n  \"illustrates\" a point\n- Explain what it actually shows\n- Bad: \"This underscores the importance of clear communication.\"\n- Good: \"Clear communication matters here.\"\n\n### Rule 8: Passive Voice Clusters\n- Flag sequences of two or more passive constructions in a row\n- Rewrite at least one in active voice to restore momentum\n- Bad: \"The report was reviewed by the team. Errors were identified. Changes\n  were recommended.\"\n- Good: \"The team reviewed the report, found errors, and recommended changes.\"\n\n### Rule 9: Rhetorical Section Openers\n- Cut rhetorical questions used as transitions (\"So what does this mean for\n  you?\", \"Why does this matter?\")\n- State the answer directly or remove entirely\n- Bad: \"So what does this mean for your team? It means you need to rethink your\n  process.\"\n- Good: \"Your team needs to rethink its process.\"\n\n### Rule 10: Staccato Rhythm\n- Break up runs of short, punchy sentences that stack without variation\n- Combine some; lengthen others\n- Let rhythm follow the thinking, not a drumbeat\n- Bad: \"Now, agents act. They send emails. They modify code. They book\n  appointments.\"\n- Good: \"Agents are starting to do real things now. They'll send an email on\n  your behalf or update a database, sometimes without you even realizing it\n  happened.\"\n\n### Rule 11: Cookie-Cutter Paragraphs\n- Vary paragraph length\n- If every paragraph is 3-4 sentences, break some into one-liners and let others\n  stretch\n- The shape on the page should look uneven, like real thinking\n\n### Rule 12: Gift-Wrapped Endings\n- Remove summary conclusions that restate the article's points\n- Cut: \"In summary\", \"In conclusion\", \"Ultimately\", \"Moving forward\", \"At the\n  end of the day\"\n- End with something specific, human, or unresolved\n- Bad: \"In summary, by focusing on clear communication, consistent feedback, and\n  mutual trust, teams can build stronger relationships.\"\n- Good: \"The best teams I've worked with never talked about trust. They just had\n  it.\"\n\n### Rule 13: Throat-Clearing Intros\n- Remove: \"Let's explore\", \"Let's unpack\", \"Let's dive in\", \"Let's break it\n  down\", \"In this article, we'll\"\n- Just start; the best first sentence puts the reader in the middle of something\n- Bad: \"In this article, we'll explore the hidden costs of micromanagement\n  Let's dive in.\"\n- Good: \"I micromanaged someone last Tuesday.\"\n\n### Rule 14: Exhaustive Lists\n- Trim bullet lists that run to 7-10 items when 3-4 would cover the essential\n  points\n- Long lists signal AI comprehensiveness, not human judgment\n- Cut the weakest items\n\n### Rule 15: Perfect Punctuation\n- Don't correct every grammar \"mistake\" if it sounds more natural broken\n  - Fragments are fine\n  - Starting with \"And\" or \"But\" is fine\n  - A comma splice can stay if it reads well\n- If the draft has personality in its punctuation, keep it\n\n### Rule 16: Copy-Paste Metaphors\n- If the same metaphor or phrase appears more than twice, vary the language\n- Use a pronoun, rephrase it, or trust the reader to remember\n- Never repeat a metaphor word-for-word three times\n- Bad: \"Trust is like a battery. When the trust battery is full... But when the\n  trust battery runs low... To recharge the trust battery...\"\n- Good: \"Trust is like a battery. When it's full, you barely think about it. But\n  let it drain and suddenly every interaction needs a charger.\"\n\n### Rule 17: Overexplaining the Obvious\n- Cut sentences that explain things the reader already understands\n- If you've made a clear point, don't re-explain how it works\n- Bad: \"Trust is earned over time. You give people small tasks, observe how they\n  handle them, then gradually expand their responsibilities.\"\n- Good: \"Trust is earned. Everyone knows this. The question is whether you're\n  actually giving people the chance to earn it.\"\n\n### Rule 18: Generic Examples\n- Flag examples that could apply to any company or product\n- If an example doesn't contain a specific, surprising, or insider detail, it's\n  filler\n- Either sharpen it or cut it\n- Bad: \"Take Slack, for example. By focusing on seamless team communication,\n  they transformed how modern workplaces collaborate.\"\n- Good: \"Slack solved the wrong problem brilliantly. Nobody needed another\n  messaging app, but everyone needed a place to dump links and pretend they'd\n  read them later.\"\n\n### Rule 19: Vague Attribution\n- Avoid vague references like \"some experts say\", \"widely covered\", \"significant\n  attention\"\n- Identify the actual critic, report, study, or author when possible\n- If you can't name the source, cut the claim\n\n## Save\n- Save the cleaned up text on top of the input file, without changing the format\n  but only the text\n\n# Verification\n- [ ] Confirm the file's structure, order, and meaning are unchanged\n- [ ] Confirm no AI markers listed in `## Pattern Checklist` remain\n","# Goal\n\n- Change text with recognizable AI mannerisms (hedging, dramatic pivots, cliched\n  transitions) and clean up AI-written content that's factually correct but tonally\n  flat\n\n# What This Skill Preserves\n- Author's opinions, arguments, and claims\n- Document structure and organization\n- Paragraph and section order\n- Core meaning and facts\n- Intentional stylistic choices (fragments, unconventional punctuation, etc.)\n\n# Workflow\n\n## Core Principles\n- Edit, don't rewrite: clean up pattern slop, preserve voice, opinions,\n  structure, and meaning\n- Apply systematically: check all 19 rules below; skip only if the rule doesn't\n  apply to the text\n- Use judgment on conflicts: if a rule break serves the writing (e.g., a\n  well-placed em dash for effect), keep it\n- Change nothing else: don't reorder paragraphs, add ideas, rephrase core\n  arguments, or alter facts\n\n## Pattern Checklist\nScan for these AI markers before applying detailed rules:\n\n- Overused Words and Jargon\n  - Grandiose: \"vital\", \"pivotal\", \"groundbreaking\", \"robust\", \"comprehensive\",\n    \"nuanced\", \"multifaceted\", \"transformative\"\n  - AI vocabulary: \"delve\", \"leverage\" (verb), \"reimagine\", \"empower\", \"unpack\",\n    \"synergy\"\n- Filler and Hedges\n  - \"It's worth noting that\", \"It's important to remember\", \"It should be\n    noted\", \"Interestingly enough\"\n  - \"Something we've observed\", \"This is where X really shines\"\n- Theatrical Transitions and Pivots\n  - Throat-clearing: \"Let's dive in\", \"Let's unpack\", \"In this article, we'll\"\n  - Dramatic pivots: \"But here's the thing\", \"Here's the catch\", \"Here's what\n    most people miss\"\n  - Overused connectors: \"Furthermore\", \"Moreover\", \"Additionally\", \"In addition\n    to the above\"\n  - Rhetorical openers: \"So what does this mean for you?\", \"Why does this\n    matter?\"\n- Structural Patterns\n  - Gift-wrapped endings: \"In summary\", \"In conclusion\", \"Ultimately\", \"At the\n    end of the day\", \"Moving forward\"\n  - Exhaustive lists: 7-10 items when 3-4 would suffice\n  - Passive voice clusters: 2+ passive sentences in a row\n  - Corrective antithesis: \"Not X. But Y.\" setup-payoff constructions\n- Meta-Language and Vagueness\n  - Meta-verbs: \"highlights\", \"underscores\", \"emphasizes\", \"showcases\",\n    \"illustrates\"\n  - Vague attribution: \"some experts say\", \"widely covered\", \"significant\n    attention\"\n  - Copy-paste metaphors: same metaphor repeated word-for-word 3+ times\n\n## Rules\n\n### Rule 1: Em Dashes\n- Remove excessive em dashes (—)\n- Rewrite using commas, full stops, or restructure the sentence\n- One or two in a long piece is fine; three or more is a pattern worth fixing\n\n### Rule 2: Corrective Antithesis\n- Remove \"Not X. But Y.\" constructions where you set up something the reader\n  never assumed, then correct it for drama\n- Bad: \"This isn't because they don't trust the technology. It's because they\n  can't predict it.\"\n- Good: \"They trust the technology fine. What they can't do is predict it.\"\n\n### Rule 3: Dramatic Pivot Phrases\n- Remove theatrical pivots: \"But here's the thing\", \"Here's the catch\", \"Here's\n  the bind\", \"Here's what most people miss\"\n- Fold the point into the sentence naturally\n- Bad: \"The patterns are valuable. But here's the bind: building a tool cost\n  more than most could justify.\"\n- Good: \"The patterns are valuable but building a tool to capture them cost more\n  than most could justify.\"\n\n### Rule 4: Soft Hedging Language\n- Cut filler hedges; just say the thing\n- Remove: \"It's worth noting that\", \"Something we've observed\", \"This is where X\n  really shines\", \"It's important to remember\", \"It should be noted\",\n  \"Interestingly enough\"\n- Bad: \"It's worth noting that this approach has shown some promising results in\n  certain contexts.\"\n- Good: \"This approach works.\"\n\n### Rule 5: Overused Transition Words\n- Cut or vary \"Furthermore\", \"Moreover\", \"Additionally\", \"In addition to the\n  above\" when chained together\n- Real writers use them sparingly\n- Bad: \"The system is fast. Furthermore, it is reliable. Moreover, it is easy to\n  use. Additionally, it integrates well.\"\n- Good: \"The system is fast, reliable, easy to use, and integrates without\n  friction.\"\n\n### Rule 6: AI Vocabulary\n- Replace words AI overuses with plain alternatives\n  - \"delve\" -> explore, look at, examine\n  - \"leverage\" (verb) -> use, apply, rely on\n  - \"robust\" -> strong, solid, reliable\n  - \"comprehensive\" -> thorough, complete, full\n  - \"nuanced\" -> subtle, layered, specific\n  - \"multifaceted\" -> complex, varied\n  - \"transformative\" -> significant, major\n  - \"unpack\" -> explain, break down\n  - \"reimagine\" -> rethink, redesign\n  - \"empower\" -> let, help, enable\n\n### Rule 7: Meta-Verbs\n- Don't say something \"highlights\", \"underscores\", \"emphasizes\", \"showcases\", or\n  \"illustrates\" a point\n- Explain what it actually shows\n- Bad: \"This underscores the importance of clear communication.\"\n- Good: \"Clear communication matters here.\"\n\n### Rule 8: Passive Voice Clusters\n- Flag sequences of two or more passive constructions in a row\n- Rewrite at least one in active voice to restore momentum\n- Bad: \"The report was reviewed by the team. Errors were identified. Changes\n  were recommended.\"\n- Good: \"The team reviewed the report, found errors, and recommended changes.\"\n\n### Rule 9: Rhetorical Section Openers\n- Cut rhetorical questions used as transitions (\"So what does this mean for\n  you?\", \"Why does this matter?\")\n- State the answer directly or remove entirely\n- Bad: \"So what does this mean for your team? It means you need to rethink your\n  process.\"\n- Good: \"Your team needs to rethink its process.\"\n\n### Rule 10: Staccato Rhythm\n- Break up runs of short, punchy sentences that stack without variation\n- Combine some; lengthen others\n- Let rhythm follow the thinking, not a drumbeat\n- Bad: \"Now, agents act. They send emails. They modify code. They book\n  appointments.\"\n- Good: \"Agents are starting to do real things now. They'll send an email on\n  your behalf or update a database, sometimes without you even realizing it\n  happened.\"\n\n### Rule 11: Cookie-Cutter Paragraphs\n- Vary paragraph length\n- If every paragraph is 3-4 sentences, break some into one-liners and let others\n  stretch\n- The shape on the page should look uneven, like real thinking\n\n### Rule 12: Gift-Wrapped Endings\n- Remove summary conclusions that restate the article's points\n- Cut: \"In summary\", \"In conclusion\", \"Ultimately\", \"Moving forward\", \"At the\n  end of the day\"\n- End with something specific, human, or unresolved\n- Bad: \"In summary, by focusing on clear communication, consistent feedback, and\n  mutual trust, teams can build stronger relationships.\"\n- Good: \"The best teams I've worked with never talked about trust. They just had\n  it.\"\n\n### Rule 13: Throat-Clearing Intros\n- Remove: \"Let's explore\", \"Let's unpack\", \"Let's dive in\", \"Let's break it\n  down\", \"In this article, we'll\"\n- Just start; the best first sentence puts the reader in the middle of something\n- Bad: \"In this article, we'll explore the hidden costs of micromanagement\n  Let's dive in.\"\n- Good: \"I micromanaged someone last Tuesday.\"\n\n### Rule 14: Exhaustive Lists\n- Trim bullet lists that run to 7-10 items when 3-4 would cover the essential\n  points\n- Long lists signal AI comprehensiveness, not human judgment\n- Cut the weakest items\n\n### Rule 15: Perfect Punctuation\n- Don't correct every grammar \"mistake\" if it sounds more natural broken\n  - Fragments are fine\n  - Starting with \"And\" or \"But\" is fine\n  - A comma splice can stay if it reads well\n- If the draft has personality in its punctuation, keep it\n\n### Rule 16: Copy-Paste Metaphors\n- If the same metaphor or phrase appears more than twice, vary the language\n- Use a pronoun, rephrase it, or trust the reader to remember\n- Never repeat a metaphor word-for-word three times\n- Bad: \"Trust is like a battery. When the trust battery is full... But when the\n  trust battery runs low... To recharge the trust battery...\"\n- Good: \"Trust is like a battery. When it's full, you barely think about it. But\n  let it drain and suddenly every interaction needs a charger.\"\n\n### Rule 17: Overexplaining the Obvious\n- Cut sentences that explain things the reader already understands\n- If you've made a clear point, don't re-explain how it works\n- Bad: \"Trust is earned over time. You give people small tasks, observe how they\n  handle them, then gradually expand their responsibilities.\"\n- Good: \"Trust is earned. Everyone knows this. The question is whether you're\n  actually giving people the chance to earn it.\"\n\n### Rule 18: Generic Examples\n- Flag examples that could apply to any company or product\n- If an example doesn't contain a specific, surprising, or insider detail, it's\n  filler\n- Either sharpen it or cut it\n- Bad: \"Take Slack, for example. By focusing on seamless team communication,\n  they transformed how modern workplaces collaborate.\"\n- Good: \"Slack solved the wrong problem brilliantly. Nobody needed another\n  messaging app, but everyone needed a place to dump links and pretend they'd\n  read them later.\"\n\n### Rule 19: Vague Attribution\n- Avoid vague references like \"some experts say\", \"widely covered\", \"significant\n  attention\"\n- Identify the actual critic, report, study, or author when possible\n- If you can't name the source, cut the claim\n\n## Save\n- Save the cleaned up text on top of the input file, without changing the format\n  but only the text\n\n# Verification\n- [ ] Confirm the file's structure, order, and meaning are unchanged\n- [ ] Confirm no AI markers listed in `## Pattern Checklist` remain\n",{"model":22,"description":7},"master","39143a859859181eff7e774457997b5278fd9e99",".claude\u002Fskills\u002Ftext.humanize",170,"https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers","https:\u002F\u002Fcausify.ai","https:\u002F\u002Fgithub.com\u002Fcausify-ai","2026-11-02 02:09:15",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add causify-ai\u002Fhelpers --skill text.humanize",{"tool":42,"command":43},"bunx","bunx skills add causify-ai\u002Fhelpers --skill text.humanize",{"tool":45,"command":46},"pnpm","pnpm dlx skills add causify-ai\u002Fhelpers --skill text.humanize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftext.humanize\u002FSKILL.md",true,[50,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,215,219,223,227,231,234,238,242,246,250,254,258],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"AGENTS.md","REFERENCE","参考文档",53953,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002FAGENTS.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"metadata.json",993,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Fmetadata.json",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"README.md",3897,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002FREADME.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"rules\u002F_sections.md",2052,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002F_sections.md",{"path":69,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":70,"sourceHtmlUrl":71},"rules\u002F_template.md",441,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002F_template.md",{"path":73,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":74,"sourceHtmlUrl":75},"rules\u002Fcrypto-approved-algorithms.md",764,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-approved-algorithms.md",{"path":77,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":78,"sourceHtmlUrl":79},"rules\u002Fcrypto-no-hardcoded-secrets.md",820,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-no-hardcoded-secrets.md",{"path":81,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":82,"sourceHtmlUrl":83},"rules\u002Fcrypto-no-secret-logging.md",1041,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-no-secret-logging.md",{"path":85,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":86,"sourceHtmlUrl":87},"rules\u002Fcrypto-provider-registration.md",724,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-provider-registration.md",{"path":89,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":90,"sourceHtmlUrl":91},"rules\u002Fcrypto-sign-canonical-bytes.md",1096,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-sign-canonical-bytes.md",{"path":93,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":94,"sourceHtmlUrl":95},"rules\u002Fcrypto-unique-iv-nonce.md",861,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fcrypto-unique-iv-nonce.md",{"path":97,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":98,"sourceHtmlUrl":99},"rules\u002Fdb-column-naming.md",627,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-column-naming.md",{"path":101,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":102,"sourceHtmlUrl":103},"rules\u002Fdb-distributed-unique-index.md",1968,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-distributed-unique-index.md",{"path":105,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":106,"sourceHtmlUrl":107},"rules\u002Fdb-index-naming.md",634,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-index-naming.md",{"path":109,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":110,"sourceHtmlUrl":111},"rules\u002Fdb-migration-base-overlay.md",3772,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-migration-base-overlay.md",{"path":113,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":114,"sourceHtmlUrl":115},"rules\u002Fdb-migration-immutable-after-apply.md",2046,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-migration-immutable-after-apply.md",{"path":117,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":118,"sourceHtmlUrl":119},"rules\u002Fdb-migration-locations-injection.md",2667,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-migration-locations-injection.md",{"path":121,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":122,"sourceHtmlUrl":123},"rules\u002Fdb-migration-parity.md",1151,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-migration-parity.md",{"path":125,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":126,"sourceHtmlUrl":127},"rules\u002Fdb-opengauss-dialect.md",813,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-opengauss-dialect.md",{"path":129,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":130,"sourceHtmlUrl":131},"rules\u002Fdb-opengauss-flyway-set-role.md",3350,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-opengauss-flyway-set-role.md",{"path":133,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":134,"sourceHtmlUrl":135},"rules\u002Fdb-table-naming.md",532,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdb-table-naming.md",{"path":137,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":138,"sourceHtmlUrl":139},"rules\u002Fdto-converter-mapstruct.md",816,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdto-converter-mapstruct.md",{"path":141,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":142,"sourceHtmlUrl":143},"rules\u002Fdto-internal-not-exposed.md",632,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdto-internal-not-exposed.md",{"path":145,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":146,"sourceHtmlUrl":147},"rules\u002Fdto-query-extends-pagequery.md",1021,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdto-query-extends-pagequery.md",{"path":149,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":150,"sourceHtmlUrl":151},"rules\u002Fdto-request-by-action.md",1144,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdto-request-by-action.md",{"path":153,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":154,"sourceHtmlUrl":155},"rules\u002Fdto-response-by-view.md",686,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fdto-response-by-view.md",{"path":157,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":158,"sourceHtmlUrl":159},"rules\u002Fentity-field-fill.md",873,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fentity-field-fill.md",{"path":161,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":162,"sourceHtmlUrl":163},"rules\u002Fentity-mapper-no-xml.md",1058,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fentity-mapper-no-xml.md",{"path":165,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":166,"sourceHtmlUrl":167},"rules\u002Fentity-tableid-assign-id.md",913,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fentity-tableid-assign-id.md",{"path":169,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":170,"sourceHtmlUrl":171},"rules\u002Fenvelope-bizexception-not-null.md",887,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fenvelope-bizexception-not-null.md",{"path":173,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":174,"sourceHtmlUrl":175},"rules\u002Fenvelope-error-code-format.md",862,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fenvelope-error-code-format.md",{"path":177,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":178,"sourceHtmlUrl":179},"rules\u002Fenvelope-factory-only.md",915,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fenvelope-factory-only.md",{"path":181,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":182,"sourceHtmlUrl":183},"rules\u002Fenvelope-field-types.md",1329,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fenvelope-field-types.md",{"path":185,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":186,"sourceHtmlUrl":187},"rules\u002Fenvelope-r-types.md",834,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fenvelope-r-types.md",{"path":189,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":190,"sourceHtmlUrl":191},"rules\u002Flayer-controller-auth-annotations.md",4239,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-controller-auth-annotations.md",{"path":193,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":194,"sourceHtmlUrl":195},"rules\u002Flayer-controller-no-entity.md",966,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-controller-no-entity.md",{"path":197,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":198,"sourceHtmlUrl":199},"rules\u002Flayer-cross-service-via-service.md",870,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-cross-service-via-service.md",{"path":201,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":202,"sourceHtmlUrl":203},"rules\u002Flayer-no-map-response.md",837,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-no-map-response.md",{"path":205,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":206,"sourceHtmlUrl":207},"rules\u002Flayer-no-silent-catch.md",876,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-no-silent-catch.md",{"path":209,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":210,"sourceHtmlUrl":211},"rules\u002Flayer-one-direction.md",1277,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-one-direction.md",{"path":213,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":170,"sourceHtmlUrl":214},"rules\u002Flayer-service-no-http.md","https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Flayer-service-no-http.md",{"path":216,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":217,"sourceHtmlUrl":218},"rules\u002Fnaming-class-suffix.md",1458,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-class-suffix.md",{"path":220,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":221,"sourceHtmlUrl":222},"rules\u002Fnaming-controller-methods.md",1378,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-controller-methods.md",{"path":224,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":225,"sourceHtmlUrl":226},"rules\u002Fnaming-enum-constants.md",731,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-enum-constants.md",{"path":228,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":229,"sourceHtmlUrl":230},"rules\u002Fnaming-package-layout.md",852,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-package-layout.md",{"path":232,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":174,"sourceHtmlUrl":233},"rules\u002Fnaming-service-mapper-methods.md","https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-service-mapper-methods.md",{"path":235,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":236,"sourceHtmlUrl":237},"rules\u002Fnaming-url.md",824,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fnaming-url.md",{"path":239,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":240,"sourceHtmlUrl":241},"rules\u002Fstack-auth-framework.md",2357,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fstack-auth-framework.md",{"path":243,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":244,"sourceHtmlUrl":245},"rules\u002Fstack-baseline.md",860,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fstack-baseline.md",{"path":247,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":248,"sourceHtmlUrl":249},"rules\u002Fstack-lambda-simple.md",1441,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fstack-lambda-simple.md",{"path":251,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":252,"sourceHtmlUrl":253},"rules\u002Fstack-lombok.md",692,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fstack-lombok.md",{"path":255,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":256,"sourceHtmlUrl":257},"rules\u002Fstack-module-readme.md",3439,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Frules\u002Fstack-module-readme.md",{"path":259,"resourceType":260,"resourceTypeDesc":261,"sizeBytes":262,"sourceHtmlUrl":263},"scripts\u002Fbuild.sh","SCRIPT","脚本",1522,"https:\u002F\u002Fgithub.com\u002FJinsYin\u002Fskills\u002Fblob\u002Fmaster\u002Fskills\u002Fspring-boot-best-practices\u002Fscripts\u002Fbuild.sh",[265,283,300,311,320,329],{"skillNo":266,"name":267,"nameZh":6,"description":268,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":269,"categories":270,"keywords":276,"publishedAt":23},"01M6C9ZMM0XSXCHHABMJ9XB1JB","tutorial_in_60_mins.propagate_docker_changes","Sync tutorial and class-project Docker files to match project_template","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftutorial_in_60_mins.propagate_docker_changes\u002FSKILL.md",[271],{"categoryNo":272,"categoryName":273,"taxonomyType":274,"taxonomyTypeDesc":275},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[277,278,279,280,22,281,282],"tutorial in 60 mins propagate docker changes","tutorial","docker","files","template","sync",{"skillNo":284,"name":285,"nameZh":6,"description":286,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":287,"categories":288,"keywords":292,"publishedAt":23},"01M6C9ZJK8QJ9FNCY39WVF3GMG","tutorial_in_60_mins.merge_markdown","Merge the content of a markdown file into a Jupyter notebook","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftutorial_in_60_mins.merge_markdown\u002FSKILL.md",[289],{"categoryNo":290,"categoryName":291,"taxonomyType":274,"taxonomyTypeDesc":275},"01JBSEEDCAT000000000000002","文档处理",[293,294,278,295,296,22,297,298,299],"merge","tutorial in 60 mins merge markdown","markdown","jupyter","file","content","jupyter notebook",{"skillNo":301,"name":302,"nameZh":6,"description":303,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":304,"categories":305,"keywords":306,"publishedAt":23},"01M6C9ZFYK13ZCT1E8BEEC4NG4","tutorial_in_60_mins.format","Format a directory to follow the \"Learn X in 60 Minutes\" tutorial conventions","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftutorial_in_60_mins.format\u002FSKILL.md",[],[307,278,308,309,310,22],"tutorial in 60 mins format","format","directory","learn",{"skillNo":312,"name":313,"nameZh":6,"description":314,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":315,"categories":316,"keywords":317,"publishedAt":23},"01M6C9ZDKXSBKNKX7M3X4W38G5","tutorial_in_60_mins.create","Create a tutorial directory for the Learn X in 60 Minutes conventions","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftutorial_in_60_mins.create\u002FSKILL.md",[],[318,278,319,309,310],"tutorial in 60 mins create","create",{"skillNo":321,"name":322,"nameZh":6,"description":323,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":324,"categories":325,"keywords":326,"publishedAt":23},"01M6BZS5Z0QE03WRS1TM3XJEY9","todo.reorg_in_progress","Reorganize ai_task_queue.md so in-progress tasks, not-started tasks, and mislabeled topic headers sit under the right H1 stage","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftodo.reorg_in_progress\u002FSKILL.md",[],[327,328],"todo reorg in progress","tasks",{"skillNo":330,"name":331,"nameZh":6,"description":332,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":333,"categories":334,"keywords":335,"publishedAt":23},"01M6BZS4CQZ6KK2KQ26SVB7QCS","todo.reorg_headers","Reorganize ai_task_queue.md .md so every H2 topic matches ALL TOPICS and every H3 task sits under the right topic, keeping its H1 stage","https:\u002F\u002Fgithub.com\u002Fcausify-ai\u002Fhelpers\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Ftodo.reorg_headers\u002FSKILL.md",[],[336],"todo reorg headers"]