[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C1RGRYQCBNE2SV4TMT7MHX":3,"skill-same:01M6C1RGRYQCBNE2SV4TMT7MHX":76},{"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":28,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6C1RGRYQCBNE2SV4TMT7MHX","forensics-report",null,"Generate forensic investigation report","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\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fforensics-report\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"report","forensics","forensics report","triage","generate","reporting","investigation","format","full","investigation report","output","path","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: forensics-report\nplatforms: [all]\ndescription: Generate forensic investigation report\ncommandHint:\n  argumentHint: \"\u003Cforensics-path> [--format triage|full|executive] [--output path]\"\n  category: forensics-reporting\n---\n\n# \u002Fforensics-report\n\nCompile all forensic findings, analysis outputs, timelines, and IOC registers into a structured investigation report. Supports three report formats: triage summary for immediate response, full technical report for detailed review, and executive summary for leadership briefing.\n\n## Usage\n\n`\u002Fforensics-report \u003Cforensics-path> [options]`\n\n## Arguments\n\n| Argument | Required | Description |\n|----------|----------|-------------|\n| forensics-path | Yes | Path to investigation directory (e.g., `.aiwg\u002Fforensics\u002F`) |\n| --format | No | Report format: `triage`, `full`, `executive` (default: `full`) |\n| --output | No | Output path (default: `.aiwg\u002Fforensics\u002Freports\u002Fforensic-report.md`) |\n| --include | No | Specific sections to include: `timeline`, `ioc`, `evidence`, `remediation` |\n| --severity-threshold | No | Minimum finding severity to include: `low`, `medium`, `high` (default: `low`) |\n| --investigator | No | Investigator name for report attribution |\n| --case-id | No | Override case ID in report header |\n\n## Behavior\n\nWhen invoked, this command:\n\n1. **Collect Investigation Artifacts**\n   - Scan forensics directory for all completed outputs\n   - Load: triage summary, acquisition manifest, analysis findings, timeline, IOC register\n   - Identify missing sections and note gaps in coverage\n   - Record report generation timestamp\n\n2. **Severity Classification**\n   - Review all findings from analysis agents\n   - Classify each finding: CRITICAL, HIGH, MEDIUM, LOW, INFORMATIONAL\n   - Count findings by severity for executive dashboard\n   - Identify the most significant findings for report lead section\n\n3. **Executive Summary** (all formats)\n   - State incident classification (confirmed breach, suspected breach, false positive)\n   - Summarize attack scope: affected systems, accounts, data\n   - State attacker objectives and achieved goals (if determinable)\n   - List top 3-5 critical findings\n   - State immediate actions taken or required\n\n4. **Technical Findings Section** (triage and full formats)\n   - Structured finding table: ID, severity, title, affected asset, evidence reference\n   - Per-finding detail: description, evidence, MITRE ATT&CK mapping, recommendation\n   - Link each finding to source log lines or artifacts\n\n5. **Timeline Section** (full format)\n   - Include condensed attack timeline with key milestones\n   - Reference full timeline at `timeline\u002Fincident-timeline.md`\n   - State attacker dwell time and activity window\n\n6. **IOC Section** (full format)\n   - Embed IOC register summary\n   - Highlight immediately actionable IOCs (IPs to block, hashes to scan)\n   - Reference full IOC register for SIEM\u002Ffirewall import\n\n7. **Evidence Documentation** (full format)\n   - List all collected evidence artifacts with case IDs\n   - Include SHA-256 hashes for integrity verification\n   - Reference chain-of-custody log\n   - Note preservation status\n\n8. **Remediation Plan**\n   - Prioritized action list with severity-based ordering\n   - Short-term: immediate containment and eradication steps\n   - Medium-term: hardening and configuration changes\n   - Long-term: detection improvements and monitoring enhancements\n   - Assign suggested owner categories (security team, sysadmin, management)\n\n9. **Report Finalization**\n   - Write formatted report to output path\n   - Generate PDF-ready markdown with proper heading hierarchy\n   - Compute report integrity hash\n   - Update investigation state to `reporting-complete`\n\n## Report Formats\n\n| Format | Audience | Length | Sections |\n|--------|----------|--------|----------|\n| `triage` | First responders | 1-2 pages | Executive summary, critical findings, immediate actions |\n| `full` | Security team, legal | 10-20 pages | All sections: findings, timeline, IOCs, evidence, remediation |\n| `executive` | Leadership, board | 1 page | Business impact, incident classification, remediation summary |\n\n## Examples\n\n### Example 1: Full report\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F\n```\n\n### Example 2: Triage report for immediate response\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --format triage\n```\n\n### Example 3: Executive summary\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --format executive --output .aiwg\u002Fforensics\u002Freports\u002Fexec-summary.md\n```\n\n### Example 4: High and critical findings only\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --severity-threshold high\n```\n\n### Example 5: Include specific sections\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --include timeline,ioc,remediation\n```\n\n## Output\n\nArtifacts are saved to `.aiwg\u002Fforensics\u002Freports\u002F`:\n\n```\n.aiwg\u002Fforensics\u002Freports\u002F\n├── forensic-report.md            # Primary investigation report\n├── executive-summary.md          # Executive version (if requested)\n├── triage-report.md              # Triage version (if requested)\n└── report-metadata.yaml          # Generation metadata and integrity hash\n```\n\n### Sample Report Structure (full format)\n\n```markdown\n# Forensic Investigation Report\nCase ID: INV-2026-02-27-web01\nGenerated: 2026-02-27T15:01:44Z\nClassification: CONFIDENTIAL\n\n## Executive Summary\n\n**Incident Classification**: Confirmed Breach\n**Severity**: CRITICAL\n**Affected Systems**: web01.internal (192.168.1.50)\n**Attack Window**: 2026-02-26 22:14Z - 2026-02-27 02:15Z (4h 1m)\n**Attacker Objectives**: Persistent access, C2 implant installation\n**Data Impact**: Undetermined (investigation ongoing)\n\nKey Findings:\n1. [CRITICAL] Successful SSH brute force against account 'deploy'\n2. [CRITICAL] C2 implant installed via cron persistence (\u002Ftmp\u002F.update)\n3. [HIGH] Active C2 beacon to 185.220.101.42:4444\n4. [HIGH] Privilege escalation: deploy -> root via sudo\n5. [HIGH] Attacker IP 185.220.101.42 is known Tor exit node\n\n## Findings\n\n| ID   | Severity | Title                          | Asset  | MITRE         |\n|------|----------|--------------------------------|--------|---------------|\n| F-01 | CRITICAL | SSH brute force success        | web01  | T1110.001     |\n| F-02 | CRITICAL | Cron-based persistence         | web01  | T1053.003     |\n| F-03 | HIGH     | Active C2 connection           | web01  | T1071.001     |\n...\n\n## Remediation Plan\n\n### Immediate (0-24h)\n- [ ] Isolate web01 from network\n- [ ] Revoke 'deploy' account credentials\n- [ ] Block 185.220.101.42 at perimeter firewall\n- [ ] Remove \u002Ftmp\u002F.update and associated cron entry\n\n### Short-term (1-7 days)\n- [ ] Rotate all SSH keys on affected system\n- [ ] Audit all user accounts for unauthorized additions\n- [ ] Review and harden SSH daemon configuration\n...\n```\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fagents\u002Freporting-agent.md - Reporting Agent\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Ftemplates\u002Fforensic-report.md - Report template\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Ftemplates\u002Fforensic-report.md - Executive template\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fcommands\u002Fforensics-status.md - Investigation status\n","# \u002Fforensics-report\n\nCompile all forensic findings, analysis outputs, timelines, and IOC registers into a structured investigation report. Supports three report formats: triage summary for immediate response, full technical report for detailed review, and executive summary for leadership briefing.\n\n## Usage\n\n`\u002Fforensics-report \u003Cforensics-path> [options]`\n\n## Arguments\n\n| Argument | Required | Description |\n|----------|----------|-------------|\n| forensics-path | Yes | Path to investigation directory (e.g., `.aiwg\u002Fforensics\u002F`) |\n| --format | No | Report format: `triage`, `full`, `executive` (default: `full`) |\n| --output | No | Output path (default: `.aiwg\u002Fforensics\u002Freports\u002Fforensic-report.md`) |\n| --include | No | Specific sections to include: `timeline`, `ioc`, `evidence`, `remediation` |\n| --severity-threshold | No | Minimum finding severity to include: `low`, `medium`, `high` (default: `low`) |\n| --investigator | No | Investigator name for report attribution |\n| --case-id | No | Override case ID in report header |\n\n## Behavior\n\nWhen invoked, this command:\n\n1. **Collect Investigation Artifacts**\n   - Scan forensics directory for all completed outputs\n   - Load: triage summary, acquisition manifest, analysis findings, timeline, IOC register\n   - Identify missing sections and note gaps in coverage\n   - Record report generation timestamp\n\n2. **Severity Classification**\n   - Review all findings from analysis agents\n   - Classify each finding: CRITICAL, HIGH, MEDIUM, LOW, INFORMATIONAL\n   - Count findings by severity for executive dashboard\n   - Identify the most significant findings for report lead section\n\n3. **Executive Summary** (all formats)\n   - State incident classification (confirmed breach, suspected breach, false positive)\n   - Summarize attack scope: affected systems, accounts, data\n   - State attacker objectives and achieved goals (if determinable)\n   - List top 3-5 critical findings\n   - State immediate actions taken or required\n\n4. **Technical Findings Section** (triage and full formats)\n   - Structured finding table: ID, severity, title, affected asset, evidence reference\n   - Per-finding detail: description, evidence, MITRE ATT&CK mapping, recommendation\n   - Link each finding to source log lines or artifacts\n\n5. **Timeline Section** (full format)\n   - Include condensed attack timeline with key milestones\n   - Reference full timeline at `timeline\u002Fincident-timeline.md`\n   - State attacker dwell time and activity window\n\n6. **IOC Section** (full format)\n   - Embed IOC register summary\n   - Highlight immediately actionable IOCs (IPs to block, hashes to scan)\n   - Reference full IOC register for SIEM\u002Ffirewall import\n\n7. **Evidence Documentation** (full format)\n   - List all collected evidence artifacts with case IDs\n   - Include SHA-256 hashes for integrity verification\n   - Reference chain-of-custody log\n   - Note preservation status\n\n8. **Remediation Plan**\n   - Prioritized action list with severity-based ordering\n   - Short-term: immediate containment and eradication steps\n   - Medium-term: hardening and configuration changes\n   - Long-term: detection improvements and monitoring enhancements\n   - Assign suggested owner categories (security team, sysadmin, management)\n\n9. **Report Finalization**\n   - Write formatted report to output path\n   - Generate PDF-ready markdown with proper heading hierarchy\n   - Compute report integrity hash\n   - Update investigation state to `reporting-complete`\n\n## Report Formats\n\n| Format | Audience | Length | Sections |\n|--------|----------|--------|----------|\n| `triage` | First responders | 1-2 pages | Executive summary, critical findings, immediate actions |\n| `full` | Security team, legal | 10-20 pages | All sections: findings, timeline, IOCs, evidence, remediation |\n| `executive` | Leadership, board | 1 page | Business impact, incident classification, remediation summary |\n\n## Examples\n\n### Example 1: Full report\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F\n```\n\n### Example 2: Triage report for immediate response\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --format triage\n```\n\n### Example 3: Executive summary\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --format executive --output .aiwg\u002Fforensics\u002Freports\u002Fexec-summary.md\n```\n\n### Example 4: High and critical findings only\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --severity-threshold high\n```\n\n### Example 5: Include specific sections\n```bash\n\u002Fforensics-report .aiwg\u002Fforensics\u002F --include timeline,ioc,remediation\n```\n\n## Output\n\nArtifacts are saved to `.aiwg\u002Fforensics\u002Freports\u002F`:\n\n```\n.aiwg\u002Fforensics\u002Freports\u002F\n├── forensic-report.md            # Primary investigation report\n├── executive-summary.md          # Executive version (if requested)\n├── triage-report.md              # Triage version (if requested)\n└── report-metadata.yaml          # Generation metadata and integrity hash\n```\n\n### Sample Report Structure (full format)\n\n```markdown\n# Forensic Investigation Report\nCase ID: INV-2026-02-27-web01\nGenerated: 2026-02-27T15:01:44Z\nClassification: CONFIDENTIAL\n\n## Executive Summary\n\n**Incident Classification**: Confirmed Breach\n**Severity**: CRITICAL\n**Affected Systems**: web01.internal (192.168.1.50)\n**Attack Window**: 2026-02-26 22:14Z - 2026-02-27 02:15Z (4h 1m)\n**Attacker Objectives**: Persistent access, C2 implant installation\n**Data Impact**: Undetermined (investigation ongoing)\n\nKey Findings:\n1. [CRITICAL] Successful SSH brute force against account 'deploy'\n2. [CRITICAL] C2 implant installed via cron persistence (\u002Ftmp\u002F.update)\n3. [HIGH] Active C2 beacon to 185.220.101.42:4444\n4. [HIGH] Privilege escalation: deploy -> root via sudo\n5. [HIGH] Attacker IP 185.220.101.42 is known Tor exit node\n\n## Findings\n\n| ID   | Severity | Title                          | Asset  | MITRE         |\n|------|----------|--------------------------------|--------|---------------|\n| F-01 | CRITICAL | SSH brute force success        | web01  | T1110.001     |\n| F-02 | CRITICAL | Cron-based persistence         | web01  | T1053.003     |\n| F-03 | HIGH     | Active C2 connection           | web01  | T1071.001     |\n...\n\n## Remediation Plan\n\n### Immediate (0-24h)\n- [ ] Isolate web01 from network\n- [ ] Revoke 'deploy' account credentials\n- [ ] Block 185.220.101.42 at perimeter firewall\n- [ ] Remove \u002Ftmp\u002F.update and associated cron entry\n\n### Short-term (1-7 days)\n- [ ] Rotate all SSH keys on affected system\n- [ ] Audit all user accounts for unauthorized additions\n- [ ] Review and harden SSH daemon configuration\n...\n```\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fagents\u002Freporting-agent.md - Reporting Agent\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Ftemplates\u002Fforensic-report.md - Report template\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Ftemplates\u002Fforensic-report.md - Executive template\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fcommands\u002Fforensics-status.md - Investigation status\n",{"name":5,"namespace":46,"platforms":47,"commandHint":49,"description":7},"aiwg",[48],"all",{"category":50,"argumentHint":51},"forensics-reporting","\u003Cforensics-path> [--format triage|full|executive] [--output path]","main","a602706fc62ff1cfcb18001358ac39647b08acf5","agentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fforensics-report",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 00:33:10",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add jmagly\u002Faiwg --skill forensics-report",{"tool":68,"command":69},"bunx","bunx skills add jmagly\u002Faiwg --skill forensics-report",{"tool":71,"command":72},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill forensics-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fforensics-report\u002FSKILL.md",true,[],[77,105,129,135,142,156],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":84,"publishedAt":41},"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",[83],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":115,"publishedAt":41},"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",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,88,119,93,120,121,95,122,85,123,97,124,125,100,101,126,127,128],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":130,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":41},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,85,86,96,88,104,91,90,99,92,93,94,95,103,97,98,89,100,101,102],{"skillNo":136,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":141,"publishedAt":41},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[139,140],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[117,116,100,119,93,120,95,118,85,123,97,124,125,88,101,122,121,126,127,128],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":41},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[150,151,152,153,154,155],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":41},"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",[162],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[164,165,124,166,151],"pi","pi local","duplicate"]