[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75E21K899VM2KAW8K3M995H":3,"skill-same:01M75E21K899VM2KAW8K3M995H":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75E21K899VM2KAW8K3M995H","graph-evolution",null,"Compares Trailmark code graphs at two source code snapshots (git commits, tags, or directories) to surface security-relevant structural changes. Detects new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications that text diffs miss. Use when comparing code between commits or tags, analyzing structural evolution, detecting attack surface growth, reviewing what changed between audit snapshots, or finding security-relevant changes that text diffs miss.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgraph-evolution\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: graph-evolution\ndescription: >\n  Compares Trailmark code graphs at two source code snapshots (git commits,\n  tags, or directories) to surface security-relevant structural changes.\n  Detects new attack paths, complexity shifts, blast radius growth, taint\n  propagation changes, and privilege boundary modifications that text diffs\n  miss. Use when comparing code between commits or tags, analyzing structural\n  evolution, detecting attack surface growth, reviewing what changed between\n  audit snapshots, or finding security-relevant changes that text diffs miss.\n---\n\n# Graph Evolution\n\nBuilds Trailmark code graphs at two source snapshots and computes a\nstructural diff. Surfaces security-relevant changes that text-level\ndiffs miss: new attack paths, complexity shifts, blast radius growth,\ntaint propagation changes, and privilege boundary modifications.\n\n## When to Use\n\n- Comparing two git refs to understand what structurally changed\n- Auditing a range of commits for security-relevant evolution\n- Detecting new attack paths created by code changes\n- Finding functions whose blast radius or complexity grew silently\n- Identifying taint propagation changes across refactors\n- Pre-release structural comparison (tag-to-tag or branch-to-branch)\n\n## When NOT to Use\n\n- Line-level code review (use `differential-review` for text-diff analysis)\n- Single-snapshot analysis (use the `trailmark` skill directly)\n- Diagram generation from a single snapshot (use the `diagramming-code` skill)\n- Mutation testing triage (use the `genotoxic` skill)\n\n## Rationalizations to Reject\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"We just need the structural diff, skip pre-analysis\" | Without pre-analysis, you miss taint changes, blast radius growth, and privilege boundary shifts | Run `engine.preanalysis()` on both snapshots |\n| \"Text diff covers what changed\" | Text diffs miss new attack paths, transitive complexity shifts, and subgraph membership changes | Use structural diff to complement text diff |\n| \"Only added nodes matter\" | Removed security functions and shifted privilege boundaries are equally dangerous | Review removals and modifications, not just additions |\n| \"Low-severity structural changes can be ignored\" | INFO-level changes (dead code removal) can mask removed security checks | Classify every change, review removals for replaced functionality |\n| \"One snapshot's graph is enough for comparison\" | Single-snapshot analysis can't detect evolution — you need both before and after | Always build and export both graphs |\n| \"Tool isn't installed, I'll compare manually\" | Manual comparison misses what graph analysis catches | Install trailmark first |\n\n---\n\n## Prerequisites\n\n**trailmark** must be installed. If `uv run trailmark` fails, run:\n\n```bash\nuv pip install trailmark\n```\n\n**DO NOT** fall back to \"manual comparison\" or reading source files as a\nsubstitute for running trailmark. The tool must be installed and used\nprogrammatically. If installation fails, report the error.\n\n---\n\n## Quick Start\n\n```bash\n# Compare two git refs (e.g., tags, branches, commits)\n# 1. Build graphs at each snapshot\n# 2. Run pre-analysis on both\n# 3. Compute structural diff\n# 4. Generate report\n\n# Step-by-step: see Workflow below\n```\n\n---\n\n## Decision Tree\n\n```\n├─ Need to understand what each metric means?\n│  └─ Read: references\u002Fevolution-metrics.md\n│\n├─ Need the report output format?\n│  └─ Read: references\u002Freport-format.md\n│\n├─ Already have two graph JSON exports?\n│  └─ Jump to Phase 3 (run graph_diff.py directly)\n│\n└─ Starting from two git refs?\n   └─ Start at Phase 1\n```\n\n---\n\n## Workflow\n\n```\nGraph Evolution Progress:\n- [ ] Phase 1: Create snapshots (git worktrees)\n- [ ] Phase 2: Build graphs + pre-analysis on both snapshots\n- [ ] Phase 3: Compute structural diff\n- [ ] Phase 4: Interpret diff and generate report\n- [ ] Phase 5: Clean up worktrees\n```\n\n### Phase 1: Create Snapshots\n\nUse git worktrees to get clean copies of each ref without disturbing\nthe working tree.\n\n```bash\n# Create temp directories for worktrees\nBEFORE_DIR=$(mktemp -d)\nAFTER_DIR=$(mktemp -d)\n\n# Create worktrees (run from repo root)\ngit worktree add \"$BEFORE_DIR\" {before_ref}\ngit worktree add \"$AFTER_DIR\" {after_ref}\n```\n\nIf comparing two directories instead of git refs, skip this phase and\nuse the directory paths directly in Phase 2.\n\n### Phase 2: Build Graphs and Run Pre-Analysis\n\nBuild Trailmark graphs for both snapshots and run pre-analysis on each.\nPre-analysis computes blast radius, taint propagation, privilege\nboundaries, and entrypoint enumeration.\n\n```python\nimport json\nfrom trailmark.query.api import QueryEngine\n\ndef build_and_export(target_dir, language, output_path):\n    \"\"\"Build graph, run pre-analysis, export JSON.\"\"\"\n    engine = QueryEngine.from_directory(target_dir, language=language)\n    engine.preanalysis()\n    json_str = engine.to_json()\n    with open(output_path, \"w\") as f:\n        f.write(json_str)\n    return engine.summary()\n\nimport tempfile, os\nwork_dir = tempfile.mkdtemp(prefix=\"trailmark_evolution_\")\nbefore_json = os.path.join(work_dir, \"before_graph.json\")\nafter_json = os.path.join(work_dir, \"after_graph.json\")\n\nbefore_summary = build_and_export(\n    \"{before_dir}\", \"{lang}\", before_json\n)\nafter_summary = build_and_export(\n    \"{after_dir}\", \"{lang}\", after_json\n)\n```\n\nVerify both graphs built successfully by checking the summary output.\nIf either fails, check that the language parameter matches the codebase\nand that trailmark supports all file types present.\n\n### Phase 3: Compute Structural Diff\n\nRun the diff script on the two exported JSON files (using the same\n`work_dir` from Phase 2):\n\n```bash\nuv run {baseDir}\u002Fscripts\u002Fgraph_diff.py \\\n    --before \"{before_json}\" \\\n    --after \"{after_json}\" > \"{work_dir}\u002Fevolution_diff.json\"\n```\n\nThe output JSON contains:\n\n| Key | Contents |\n|-----|----------|\n| `summary_delta` | Changes in node\u002Fedge\u002Fentrypoint counts |\n| `nodes.added` | New functions, classes, methods |\n| `nodes.removed` | Deleted functions, classes, methods |\n| `nodes.modified` | Functions with changed CC, params, return type, span |\n| `edges.added` | New call\u002Finheritance\u002Fimport relationships |\n| `edges.removed` | Deleted relationships |\n| `subgraphs` | Per-subgraph membership changes (tainted, high_blast_radius, etc.) |\n\n### Phase 4: Interpret Diff and Generate Report\n\nRead the diff JSON and generate a security-focused markdown report.\nSee [references\u002Freport-format.md](references\u002Freport-format.md) for\nthe full template.\n\n**Interpretation priorities (highest to lowest):**\n\n1. **New tainted paths** — nodes entering the `tainted` subgraph,\n   especially if they also appear in added edges targeting sensitive\n   functions\n2. **Privilege boundary changes** — new or removed trust transitions\n3. **Attack surface growth** — new entrypoints, especially\n   `untrusted_external`\n4. **Blast radius increases** — nodes entering `high_blast_radius`\n5. **Complexity spikes** — CC increases > 3 on tainted or\n   entrypoint-reachable nodes\n6. **Structural additions** — new nodes and edges (review needed)\n7. **Structural removals** — verify removed security functions were\n   replaced\n\nCross-reference structural changes with `git diff {before_ref}..{after_ref}`\nto add source-level context to findings.\n\n**Severity classification:**\n\n| Severity | Structural Signal |\n|----------|------------------|\n| CRITICAL | New tainted path to sensitive function, removed auth boundary |\n| HIGH | New entrypoint + high blast radius, large CC increase on tainted node |\n| MEDIUM | New trust-boundary-crossing edges, moderate CC increase |\n| LOW | Added nodes without entrypoint reachability |\n| INFO | Dead code removal, complexity reductions |\n\nFor detailed metric definitions, see\n[references\u002Fevolution-metrics.md](references\u002Fevolution-metrics.md).\n\n### Phase 5: Clean Up\n\nRemove git worktrees after the report is written:\n\n```bash\ngit worktree remove \"{before_dir}\"\ngit worktree remove \"{after_dir}\"\n```\n\n---\n\n## Diff Script Reference\n\n```\nuv run {baseDir}\u002Fscripts\u002Fgraph_diff.py [OPTIONS]\n```\n\n| Argument | Default | Description |\n|----------|---------|-------------|\n| `--before` | required | Path to the \"before\" graph JSON |\n| `--after` | required | Path to the \"after\" graph JSON |\n| `--indent` | `2` | JSON output indentation |\n\nInput format: Trailmark JSON exports from `engine.to_json()`.\nOutput: JSON structural diff to stdout.\n\n---\n\n## Quality Checklist\n\nBefore delivering the report:\n\n- [ ] Both graphs built successfully (check summaries)\n- [ ] Pre-analysis ran on both snapshots\n- [ ] Structural diff computed (non-empty diff JSON)\n- [ ] All subgraph changes interpreted (tainted, blast radius, etc.)\n- [ ] Critical findings include evidence (node IDs, edge diffs)\n- [ ] Severity levels assigned to all findings\n- [ ] Source-level context added via git diff cross-reference\n- [ ] Worktrees cleaned up (or temp dirs removed)\n- [ ] Report written to `GRAPH_EVOLUTION_*.md`\n\n---\n\n## Integration\n\n**trailmark skill:**\nPhase 2 uses the trailmark API for graph building and pre-analysis.\nAll trailmark query patterns work on either snapshot's engine.\n\n**differential-review skill:**\nUse graph-evolution for structural analysis, differential-review for\nline-level code review. The two are complementary — graph-evolution\nfinds attack paths that text diffs miss, while differential-review\nprovides git blame context and micro-adversarial analysis.\n\n**genotoxic skill:**\nIf graph-evolution reveals new high-CC tainted nodes, feed them to\ngenotoxic for mutation testing triage.\n\n**diagramming-code skill:**\nGenerate before\u002Fafter diagrams to visualize structural changes.\nUse `call-graph` or `data-flow` diagrams focused on changed nodes.\n\n---\n\n## Supporting Documentation\n\n- **[references\u002Fevolution-metrics.md](references\u002Fevolution-metrics.md)** —\n  What each structural metric means and why it matters for security\n- **[references\u002Freport-format.md](references\u002Freport-format.md)** —\n  Report template, severity classification, and example findings\n","# Graph Evolution\n\nBuilds Trailmark code graphs at two source snapshots and computes a\nstructural diff. Surfaces security-relevant changes that text-level\ndiffs miss: new attack paths, complexity shifts, blast radius growth,\ntaint propagation changes, and privilege boundary modifications.\n\n## When to Use\n\n- Comparing two git refs to understand what structurally changed\n- Auditing a range of commits for security-relevant evolution\n- Detecting new attack paths created by code changes\n- Finding functions whose blast radius or complexity grew silently\n- Identifying taint propagation changes across refactors\n- Pre-release structural comparison (tag-to-tag or branch-to-branch)\n\n## When NOT to Use\n\n- Line-level code review (use `differential-review` for text-diff analysis)\n- Single-snapshot analysis (use the `trailmark` skill directly)\n- Diagram generation from a single snapshot (use the `diagramming-code` skill)\n- Mutation testing triage (use the `genotoxic` skill)\n\n## Rationalizations to Reject\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"We just need the structural diff, skip pre-analysis\" | Without pre-analysis, you miss taint changes, blast radius growth, and privilege boundary shifts | Run `engine.preanalysis()` on both snapshots |\n| \"Text diff covers what changed\" | Text diffs miss new attack paths, transitive complexity shifts, and subgraph membership changes | Use structural diff to complement text diff |\n| \"Only added nodes matter\" | Removed security functions and shifted privilege boundaries are equally dangerous | Review removals and modifications, not just additions |\n| \"Low-severity structural changes can be ignored\" | INFO-level changes (dead code removal) can mask removed security checks | Classify every change, review removals for replaced functionality |\n| \"One snapshot's graph is enough for comparison\" | Single-snapshot analysis can't detect evolution — you need both before and after | Always build and export both graphs |\n| \"Tool isn't installed, I'll compare manually\" | Manual comparison misses what graph analysis catches | Install trailmark first |\n\n---\n\n## Prerequisites\n\n**trailmark** must be installed. If `uv run trailmark` fails, run:\n\n```bash\nuv pip install trailmark\n```\n\n**DO NOT** fall back to \"manual comparison\" or reading source files as a\nsubstitute for running trailmark. The tool must be installed and used\nprogrammatically. If installation fails, report the error.\n\n---\n\n## Quick Start\n\n```bash\n# Compare two git refs (e.g., tags, branches, commits)\n# 1. Build graphs at each snapshot\n# 2. Run pre-analysis on both\n# 3. Compute structural diff\n# 4. Generate report\n\n# Step-by-step: see Workflow below\n```\n\n---\n\n## Decision Tree\n\n```\n├─ Need to understand what each metric means?\n│  └─ Read: references\u002Fevolution-metrics.md\n│\n├─ Need the report output format?\n│  └─ Read: references\u002Freport-format.md\n│\n├─ Already have two graph JSON exports?\n│  └─ Jump to Phase 3 (run graph_diff.py directly)\n│\n└─ Starting from two git refs?\n   └─ Start at Phase 1\n```\n\n---\n\n## Workflow\n\n```\nGraph Evolution Progress:\n- [ ] Phase 1: Create snapshots (git worktrees)\n- [ ] Phase 2: Build graphs + pre-analysis on both snapshots\n- [ ] Phase 3: Compute structural diff\n- [ ] Phase 4: Interpret diff and generate report\n- [ ] Phase 5: Clean up worktrees\n```\n\n### Phase 1: Create Snapshots\n\nUse git worktrees to get clean copies of each ref without disturbing\nthe working tree.\n\n```bash\n# Create temp directories for worktrees\nBEFORE_DIR=$(mktemp -d)\nAFTER_DIR=$(mktemp -d)\n\n# Create worktrees (run from repo root)\ngit worktree add \"$BEFORE_DIR\" {before_ref}\ngit worktree add \"$AFTER_DIR\" {after_ref}\n```\n\nIf comparing two directories instead of git refs, skip this phase and\nuse the directory paths directly in Phase 2.\n\n### Phase 2: Build Graphs and Run Pre-Analysis\n\nBuild Trailmark graphs for both snapshots and run pre-analysis on each.\nPre-analysis computes blast radius, taint propagation, privilege\nboundaries, and entrypoint enumeration.\n\n```python\nimport json\nfrom trailmark.query.api import QueryEngine\n\ndef build_and_export(target_dir, language, output_path):\n    \"\"\"Build graph, run pre-analysis, export JSON.\"\"\"\n    engine = QueryEngine.from_directory(target_dir, language=language)\n    engine.preanalysis()\n    json_str = engine.to_json()\n    with open(output_path, \"w\") as f:\n        f.write(json_str)\n    return engine.summary()\n\nimport tempfile, os\nwork_dir = tempfile.mkdtemp(prefix=\"trailmark_evolution_\")\nbefore_json = os.path.join(work_dir, \"before_graph.json\")\nafter_json = os.path.join(work_dir, \"after_graph.json\")\n\nbefore_summary = build_and_export(\n    \"{before_dir}\", \"{lang}\", before_json\n)\nafter_summary = build_and_export(\n    \"{after_dir}\", \"{lang}\", after_json\n)\n```\n\nVerify both graphs built successfully by checking the summary output.\nIf either fails, check that the language parameter matches the codebase\nand that trailmark supports all file types present.\n\n### Phase 3: Compute Structural Diff\n\nRun the diff script on the two exported JSON files (using the same\n`work_dir` from Phase 2):\n\n```bash\nuv run {baseDir}\u002Fscripts\u002Fgraph_diff.py \\\n    --before \"{before_json}\" \\\n    --after \"{after_json}\" > \"{work_dir}\u002Fevolution_diff.json\"\n```\n\nThe output JSON contains:\n\n| Key | Contents |\n|-----|----------|\n| `summary_delta` | Changes in node\u002Fedge\u002Fentrypoint counts |\n| `nodes.added` | New functions, classes, methods |\n| `nodes.removed` | Deleted functions, classes, methods |\n| `nodes.modified` | Functions with changed CC, params, return type, span |\n| `edges.added` | New call\u002Finheritance\u002Fimport relationships |\n| `edges.removed` | Deleted relationships |\n| `subgraphs` | Per-subgraph membership changes (tainted, high_blast_radius, etc.) |\n\n### Phase 4: Interpret Diff and Generate Report\n\nRead the diff JSON and generate a security-focused markdown report.\nSee [references\u002Freport-format.md](references\u002Freport-format.md) for\nthe full template.\n\n**Interpretation priorities (highest to lowest):**\n\n1. **New tainted paths** — nodes entering the `tainted` subgraph,\n   especially if they also appear in added edges targeting sensitive\n   functions\n2. **Privilege boundary changes** — new or removed trust transitions\n3. **Attack surface growth** — new entrypoints, especially\n   `untrusted_external`\n4. **Blast radius increases** — nodes entering `high_blast_radius`\n5. **Complexity spikes** — CC increases > 3 on tainted or\n   entrypoint-reachable nodes\n6. **Structural additions** — new nodes and edges (review needed)\n7. **Structural removals** — verify removed security functions were\n   replaced\n\nCross-reference structural changes with `git diff {before_ref}..{after_ref}`\nto add source-level context to findings.\n\n**Severity classification:**\n\n| Severity | Structural Signal |\n|----------|------------------|\n| CRITICAL | New tainted path to sensitive function, removed auth boundary |\n| HIGH | New entrypoint + high blast radius, large CC increase on tainted node |\n| MEDIUM | New trust-boundary-crossing edges, moderate CC increase |\n| LOW | Added nodes without entrypoint reachability |\n| INFO | Dead code removal, complexity reductions |\n\nFor detailed metric definitions, see\n[references\u002Fevolution-metrics.md](references\u002Fevolution-metrics.md).\n\n### Phase 5: Clean Up\n\nRemove git worktrees after the report is written:\n\n```bash\ngit worktree remove \"{before_dir}\"\ngit worktree remove \"{after_dir}\"\n```\n\n---\n\n## Diff Script Reference\n\n```\nuv run {baseDir}\u002Fscripts\u002Fgraph_diff.py [OPTIONS]\n```\n\n| Argument | Default | Description |\n|----------|---------|-------------|\n| `--before` | required | Path to the \"before\" graph JSON |\n| `--after` | required | Path to the \"after\" graph JSON |\n| `--indent` | `2` | JSON output indentation |\n\nInput format: Trailmark JSON exports from `engine.to_json()`.\nOutput: JSON structural diff to stdout.\n\n---\n\n## Quality Checklist\n\nBefore delivering the report:\n\n- [ ] Both graphs built successfully (check summaries)\n- [ ] Pre-analysis ran on both snapshots\n- [ ] Structural diff computed (non-empty diff JSON)\n- [ ] All subgraph changes interpreted (tainted, blast radius, etc.)\n- [ ] Critical findings include evidence (node IDs, edge diffs)\n- [ ] Severity levels assigned to all findings\n- [ ] Source-level context added via git diff cross-reference\n- [ ] Worktrees cleaned up (or temp dirs removed)\n- [ ] Report written to `GRAPH_EVOLUTION_*.md`\n\n---\n\n## Integration\n\n**trailmark skill:**\nPhase 2 uses the trailmark API for graph building and pre-analysis.\nAll trailmark query patterns work on either snapshot's engine.\n\n**differential-review skill:**\nUse graph-evolution for structural analysis, differential-review for\nline-level code review. The two are complementary — graph-evolution\nfinds attack paths that text diffs miss, while differential-review\nprovides git blame context and micro-adversarial analysis.\n\n**genotoxic skill:**\nIf graph-evolution reveals new high-CC tainted nodes, feed them to\ngenotoxic for mutation testing triage.\n\n**diagramming-code skill:**\nGenerate before\u002Fafter diagrams to visualize structural changes.\nUse `call-graph` or `data-flow` diagrams focused on changed nodes.\n\n---\n\n## Supporting Documentation\n\n- **[references\u002Fevolution-metrics.md](references\u002Fevolution-metrics.md)** —\n  What each structural metric means and why it matters for security\n- **[references\u002Freport-format.md](references\u002Freport-format.md)** —\n  Report template, severity classification, and example findings\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fgraph-evolution",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill graph-evolution",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill graph-evolution",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill graph-evolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgraph-evolution\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fevolution-metrics.md","REFERENCE","参考文档",5205,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgraph-evolution\u002Freferences\u002Fevolution-metrics.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Freport-format.md",4340,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgraph-evolution\u002Freferences\u002Freport-format.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fgraph_diff.py","SCRIPT","脚本",7845,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fgraph-evolution\u002Fscripts\u002Fgraph_diff.py",[63,70,77,86,93,100],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]