[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CB0X3SFCGDM48B5Q31V42R":3,"skill-same:01M6CB0X3SFCGDM48B5Q31V42R":96},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6CB0X3SFCGDM48B5Q31V42R","soul-apply",null,"Apply a SOUL.md identity to content generation, incorporating worldview, opinions, and character","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\u002Futils\u002Fskills\u002Fsoul-apply\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"soul apply","soul","apply","identity","content","character","generation","SOUL.md","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: soul-apply\nplatforms: [all]\ndescription: Apply a SOUL.md identity to content generation, incorporating worldview, opinions, and character\n\n---\n\n# soul-apply\n\nApply a SOUL.md identity to content generation — deeper than voice-apply, incorporating worldview, opinions, and character.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"apply soul\" → voice enforcement via SOUL.md\n- \"write in our voice\" → soul-based writing\n\n## Behavior\n\nWhen triggered, this skill applies the loaded SOUL.md to any content generation task. Unlike `\u002Fvoice-apply` which adjusts writing style (tone, formality, sentence structure), `\u002Fsoul-apply` incorporates the agent's identity — worldview shapes arguments, opinions influence recommendations, vocabulary infuses the text, and boundaries constrain what gets said.\n\n### Application Layers\n\n| Layer | What Changes | Source Section |\n|-------|-------------|----------------|\n| **Worldview** | How arguments are framed, what's treated as axiomatic | Worldview |\n| **Opinions** | Which positions are taken on debatable topics | Opinions |\n| **Vocabulary** | Which terms are used and their specific meanings | Vocabulary |\n| **Boundaries** | What the agent won't say or recommend | Boundaries |\n| **Tensions** | Where the agent acknowledges complexity | Tensions |\n| **Tone** | How confident, direct, or warm the output feels | Who I Am + Pet Peeves |\n\n### Application Process\n\n1. **Load soul file** — `.\u002FSOUL.md`, `.\u002F.aiwg\u002FSOUL.md`, or specified path\n2. **Load per-agent soul** if active agent has a companion `.soul.md`\n3. **Internalize identity** — not as rules to follow, but as character to inhabit\n4. **Generate content** with soul actively shaping:\n   - Arguments derived from worldview, not generic reasoning\n   - Opinions stated where relevant, not hedged away\n   - Vocabulary used naturally, not forced\n   - Boundaries respected silently (no meta-commentary about what was avoided)\n   - Tensions acknowledged when the topic touches contradictions\n5. **Verify output** against soul — would this person actually write this?\n\n### Application Modes\n\n#### Explicit Mode\n\nUser invokes `\u002Fsoul-apply` with specific content:\n\n```\n\u002Fsoul-apply \"Write a recommendation for our database migration strategy\"\n```\n\nThe soul shapes the recommendation — e.g., if the soul values simplicity, it might recommend PostgreSQL over a microservices data mesh.\n\n#### Passive Mode\n\nWhen soul enforcement is enabled via `\u002Fsoul-enable`, the soul is passively applied to all content generation. `\u002Fsoul-apply` is the explicit version of what the enforcement rule does implicitly.\n\n#### Revision Mode\n\nApply soul to existing content:\n\n```\n\u002Fsoul-apply --revise .\u002Fdocs\u002Farchitecture-decision.md\n```\n\nRewrites the document to reflect the soul's worldview, opinions, and voice while preserving the factual content.\n\n### What Soul Application Looks Like\n\n**Without soul** (generic):\n```\nWe should consider using microservices for this project. There are several\napproaches to consider, each with trade-offs. The team should evaluate\nwhat works best for their specific situation.\n```\n\n**With soul** (engineer who values simplicity):\n```\nStart with a monolith. Most teams split too early, and you'll spend more\ntime on service boundaries than on the actual problem. If you hit a genuine\nscaling bottleneck — not a hypothetical one — extract that specific piece.\nA well-structured monolith beats a distributed monolith with network latency\nevery time.\n```\n\n**Without soul** (generic code review):\n```\nThis function could benefit from some refactoring. Consider breaking it\ninto smaller pieces for better readability and testability.\n```\n\n**With soul** (skeptical engineer):\n```\nThis function is 40 lines and does one thing. That's fine. Don't split it\ninto three functions that each need the same context passed through parameters.\nThe current version is readable at 3 AM — splitting it would make it harder\nto follow, not easier.\n```\n\n## Parameters\n\n| Flag | Description |\n|------|-------------|\n| `--soul \u003Cpath>` | Use a specific soul file (default: auto-detect) |\n| `--revise \u003Cpath>` | Revise existing content through the soul |\n| `--compare` | Show before\u002Fafter comparison |\n| `--intensity \u003Clow\\|medium\\|high>` | How strongly the soul shapes output (default: medium) |\n\n### Intensity Levels\n\n| Level | Behavior |\n|-------|----------|\n| `low` | Subtle influence — vocabulary and tone shift, opinions only when directly relevant |\n| `medium` | Clear character — worldview shapes framing, opinions stated naturally, vocabulary consistent |\n| `high` | Full character — strong opinions, distinctive voice, boundaries enforced, contradictions surfaced |\n\n## Integration\n\n### With Voice Framework\n\nWhen both soul and voice profile are active:\n- **Soul** controls *what* is said (opinions, worldview, boundaries)\n- **Voice** controls *how* it sounds (sentence structure, formality, tone scales)\n- If they conflict, soul takes precedence on content; voice takes precedence on syntax\n\n### With soul-enable\n\nWhen enforcement is active, `\u002Fsoul-apply` is redundant for new content — the soul is already being applied. Use `\u002Fsoul-apply` for:\n- Explicit revision of existing content\n- Switching between soul files mid-session\n- Testing soul application before enabling enforcement\n\n### Verification\n\nAfter application, the output should pass the soul prediction test:\n> \"Would someone who read the SOUL.md predict this output came from this persona?\"\n\nIf not, the soul may be too vague — recommend `\u002Fsoul-enhance`.\n\n## Examples\n\n```bash\n# Apply soul to a content generation task\n\u002Fsoul-apply \"Write a post about why we chose PostgreSQL\"\n\n# Revise existing content through the soul\n\u002Fsoul-apply --revise docs\u002Farchitecture-decision.md\n\n# Apply with high intensity (strong character)\n\u002Fsoul-apply --intensity high \"Review this PR's architectural approach\"\n\n# Use a specific soul file\n\u002Fsoul-apply --soul .claude\u002Fagents\u002Fsecurity-auditor.soul.md \"Assess this auth flow\"\n\n# Compare before\u002Fafter\n\u002Fsoul-apply --revise --compare docs\u002Fteam-practices.md\n```\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fvoice-framework\u002Fskills\u002Fvoice-apply\u002FSKILL.md — Voice application (complementary)\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fsoul-enforcement.md — Passive enforcement rule\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Fskills\u002Fsoul-create\u002FSKILL.md — Soul creation\n- @$AIWG_ROOT\u002Fdocs\u002Fsoul-md-guide.md — Integration guide\n- #437 — SOUL.md compatibility issue (Phase 2)\n","# soul-apply\n\nApply a SOUL.md identity to content generation — deeper than voice-apply, incorporating worldview, opinions, and character.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"apply soul\" → voice enforcement via SOUL.md\n- \"write in our voice\" → soul-based writing\n\n## Behavior\n\nWhen triggered, this skill applies the loaded SOUL.md to any content generation task. Unlike `\u002Fvoice-apply` which adjusts writing style (tone, formality, sentence structure), `\u002Fsoul-apply` incorporates the agent's identity — worldview shapes arguments, opinions influence recommendations, vocabulary infuses the text, and boundaries constrain what gets said.\n\n### Application Layers\n\n| Layer | What Changes | Source Section |\n|-------|-------------|----------------|\n| **Worldview** | How arguments are framed, what's treated as axiomatic | Worldview |\n| **Opinions** | Which positions are taken on debatable topics | Opinions |\n| **Vocabulary** | Which terms are used and their specific meanings | Vocabulary |\n| **Boundaries** | What the agent won't say or recommend | Boundaries |\n| **Tensions** | Where the agent acknowledges complexity | Tensions |\n| **Tone** | How confident, direct, or warm the output feels | Who I Am + Pet Peeves |\n\n### Application Process\n\n1. **Load soul file** — `.\u002FSOUL.md`, `.\u002F.aiwg\u002FSOUL.md`, or specified path\n2. **Load per-agent soul** if active agent has a companion `.soul.md`\n3. **Internalize identity** — not as rules to follow, but as character to inhabit\n4. **Generate content** with soul actively shaping:\n   - Arguments derived from worldview, not generic reasoning\n   - Opinions stated where relevant, not hedged away\n   - Vocabulary used naturally, not forced\n   - Boundaries respected silently (no meta-commentary about what was avoided)\n   - Tensions acknowledged when the topic touches contradictions\n5. **Verify output** against soul — would this person actually write this?\n\n### Application Modes\n\n#### Explicit Mode\n\nUser invokes `\u002Fsoul-apply` with specific content:\n\n```\n\u002Fsoul-apply \"Write a recommendation for our database migration strategy\"\n```\n\nThe soul shapes the recommendation — e.g., if the soul values simplicity, it might recommend PostgreSQL over a microservices data mesh.\n\n#### Passive Mode\n\nWhen soul enforcement is enabled via `\u002Fsoul-enable`, the soul is passively applied to all content generation. `\u002Fsoul-apply` is the explicit version of what the enforcement rule does implicitly.\n\n#### Revision Mode\n\nApply soul to existing content:\n\n```\n\u002Fsoul-apply --revise .\u002Fdocs\u002Farchitecture-decision.md\n```\n\nRewrites the document to reflect the soul's worldview, opinions, and voice while preserving the factual content.\n\n### What Soul Application Looks Like\n\n**Without soul** (generic):\n```\nWe should consider using microservices for this project. There are several\napproaches to consider, each with trade-offs. The team should evaluate\nwhat works best for their specific situation.\n```\n\n**With soul** (engineer who values simplicity):\n```\nStart with a monolith. Most teams split too early, and you'll spend more\ntime on service boundaries than on the actual problem. If you hit a genuine\nscaling bottleneck — not a hypothetical one — extract that specific piece.\nA well-structured monolith beats a distributed monolith with network latency\nevery time.\n```\n\n**Without soul** (generic code review):\n```\nThis function could benefit from some refactoring. Consider breaking it\ninto smaller pieces for better readability and testability.\n```\n\n**With soul** (skeptical engineer):\n```\nThis function is 40 lines and does one thing. That's fine. Don't split it\ninto three functions that each need the same context passed through parameters.\nThe current version is readable at 3 AM — splitting it would make it harder\nto follow, not easier.\n```\n\n## Parameters\n\n| Flag | Description |\n|------|-------------|\n| `--soul \u003Cpath>` | Use a specific soul file (default: auto-detect) |\n| `--revise \u003Cpath>` | Revise existing content through the soul |\n| `--compare` | Show before\u002Fafter comparison |\n| `--intensity \u003Clow\\|medium\\|high>` | How strongly the soul shapes output (default: medium) |\n\n### Intensity Levels\n\n| Level | Behavior |\n|-------|----------|\n| `low` | Subtle influence — vocabulary and tone shift, opinions only when directly relevant |\n| `medium` | Clear character — worldview shapes framing, opinions stated naturally, vocabulary consistent |\n| `high` | Full character — strong opinions, distinctive voice, boundaries enforced, contradictions surfaced |\n\n## Integration\n\n### With Voice Framework\n\nWhen both soul and voice profile are active:\n- **Soul** controls *what* is said (opinions, worldview, boundaries)\n- **Voice** controls *how* it sounds (sentence structure, formality, tone scales)\n- If they conflict, soul takes precedence on content; voice takes precedence on syntax\n\n### With soul-enable\n\nWhen enforcement is active, `\u002Fsoul-apply` is redundant for new content — the soul is already being applied. Use `\u002Fsoul-apply` for:\n- Explicit revision of existing content\n- Switching between soul files mid-session\n- Testing soul application before enabling enforcement\n\n### Verification\n\nAfter application, the output should pass the soul prediction test:\n> \"Would someone who read the SOUL.md predict this output came from this persona?\"\n\nIf not, the soul may be too vague — recommend `\u002Fsoul-enhance`.\n\n## Examples\n\n```bash\n# Apply soul to a content generation task\n\u002Fsoul-apply \"Write a post about why we chose PostgreSQL\"\n\n# Revise existing content through the soul\n\u002Fsoul-apply --revise docs\u002Farchitecture-decision.md\n\n# Apply with high intensity (strong character)\n\u002Fsoul-apply --intensity high \"Review this PR's architectural approach\"\n\n# Use a specific soul file\n\u002Fsoul-apply --soul .claude\u002Fagents\u002Fsecurity-auditor.soul.md \"Assess this auth flow\"\n\n# Compare before\u002Fafter\n\u002Fsoul-apply --revise --compare docs\u002Fteam-practices.md\n```\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Fvoice-framework\u002Fskills\u002Fvoice-apply\u002FSKILL.md — Voice application (complementary)\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fsoul-enforcement.md — Passive enforcement rule\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Fskills\u002Fsoul-create\u002FSKILL.md — Soul creation\n- @$AIWG_ROOT\u002Fdocs\u002Fsoul-md-guide.md — Integration guide\n- #437 — SOUL.md compatibility issue (Phase 2)\n",{"name":5,"namespace":37,"platforms":38,"description":7},"aiwg",[39],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Futils\u002Fskills\u002Fsoul-apply",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-12 21:57:33",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jmagly\u002Faiwg --skill soul-apply",{"tool":56,"command":57},"bunx","bunx skills add jmagly\u002Faiwg --skill soul-apply",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill soul-apply","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Futils\u002Fskills\u002Fsoul-apply\u002FSKILL.md",true,[64,70,74,78,82,88,92],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Falgorithms.md","REFERENCE","参考文档",10038,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Falgorithms.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fcallbacks.md",15631,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fcallbacks.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcustom_environments.md",13729,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fcustom_environments.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fvectorized_envs.md",14789,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Freferences\u002Fvectorized_envs.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fcustom_env_template.py","SCRIPT","脚本",9350,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Fcustom_env_template.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fevaluate_agent.py",7335,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Fevaluate_agent.py",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Ftrain_rl_agent.py",5123,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fstable-baselines3\u002Fscripts\u002Ftrain_rl_agent.py",[97,125,149,155,162,176],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":32},"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",[103],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":32},"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",[131,134],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[136,137,138,108,139,113,140,141,115,142,105,143,117,144,145,120,121,146,147,148],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":150,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":32},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[107,105,106,116,108,124,111,110,119,112,113,114,115,123,117,118,109,120,121,122],{"skillNo":156,"name":127,"nameZh":6,"description":128,"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":161,"publishedAt":32},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[159,160],{"categoryNo":132,"categoryName":133,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[137,136,120,139,113,140,115,138,105,143,117,144,145,108,121,142,141,146,147,148],{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":32},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[170,171,172,173,174,175],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":32},"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",[182],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[184,185,144,186,171],"pi","pi local","duplicate"]