[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F347Q9400MHCS16M220MXJ":3,"skill-same:01M7F347Q9400MHCS16M220MXJ":59},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":48},"01M7F347Q9400MHCS16M220MXJ","graph-write",null,"Write, propose, commit, repair, and nudge Potpie Context Graph records safely.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpotpie\u002Fsub-skills\u002Fgraph-write\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: graph-write\ndescription: \"Write, propose, commit, repair, and nudge Potpie Context Graph\n  records safely.\"\nmetadata:\n  disco-role: operating\ndisable-model-invocation: true\nlicense: Apache 2.0\n---\n\n# Potpie graph write\n\nUse this sub-skill when the task is about adding durable memory, proposing graph mutations, committing plans, handling inbox items, running graph quality checks, or nudging agents from graph evidence.\n\n## Read this when\n\n- The user asks about `potpie record`, `potpie graph propose`, `potpie graph commit`, `potpie graph mutate`, `potpie graph mutation-template`, `potpie graph bulk apply`, `potpie graph import`, `potpie graph repair`, `potpie graph history`, `potpie graph inbox`, `potpie graph quality`, or `potpie graph nudge`.\n- A write fails because a mutation payload is malformed, a plan needs review, a plan expired, or verification did not pass.\n- You need to distinguish the canonical propose\u002Fcommit flow from the legacy `graph mutate` wrapper.\n\n## Do not use this for\n\n- Discovery-only reads: read `..\u002Fgraph-read\u002FSKILL.md`.\n- Pot\u002Fsource setup or default binding: read `..\u002Fworkspace-boundaries\u002FSKILL.md`.\n- Runtime\u002Fdaemon startup: read `..\u002Fruntime\u002FSKILL.md`.\n- Credential acquisition: read `..\u002Fauth-integrations\u002FSKILL.md`.\n\n## Operating procedure\n\n1. Prefer the canonical plan door: `graph propose` to validate and stage, then `graph commit` with explicit approval and verification as needed.\n2. Use `graph mutation-template` before authoring payloads when the DSL or entity label is uncertain.\n3. Keep mutations flat and retrieval-grade: durable descriptions, explicit scopes, source references, and no nested legacy wrappers unless the CLI specifically emits them.\n4. Use `graph inbox`, `graph quality`, `graph history`, and `graph inspect` to review pending, stale, or questionable graph state before applying more writes.\n5. Treat `record` as a convenient durable-memory write path and `graph nudge` as a bridge from graph evidence to agent guidance.\n\n## References\n\n- `references\u002Fworkflow.md` — write command matrix, flat mutation DSL, approval\u002Fverification, inbox, quality, bulk, and nudge flows.\n- `references\u002Ftroubleshooting.md` — malformed payloads, review gates, expired plans, bulk failures, inbox states, and quality repairs.\n\n## Verification notes\n\n- Safe native candidates include graph CLI contract, graph workbench plan\u002Finbox\u002Fquality tests, nudge service, apply-once, semantic mutation validation, semantic mutations, graph-plan compatibility, and graph-workbench ontology tests.\n- No accelerator backend is required for write-side CLI\u002Fcontract verification.\n","# Potpie graph write\n\nUse this sub-skill when the task is about adding durable memory, proposing graph mutations, committing plans, handling inbox items, running graph quality checks, or nudging agents from graph evidence.\n\n## Read this when\n\n- The user asks about `potpie record`, `potpie graph propose`, `potpie graph commit`, `potpie graph mutate`, `potpie graph mutation-template`, `potpie graph bulk apply`, `potpie graph import`, `potpie graph repair`, `potpie graph history`, `potpie graph inbox`, `potpie graph quality`, or `potpie graph nudge`.\n- A write fails because a mutation payload is malformed, a plan needs review, a plan expired, or verification did not pass.\n- You need to distinguish the canonical propose\u002Fcommit flow from the legacy `graph mutate` wrapper.\n\n## Do not use this for\n\n- Discovery-only reads: read `..\u002Fgraph-read\u002FSKILL.md`.\n- Pot\u002Fsource setup or default binding: read `..\u002Fworkspace-boundaries\u002FSKILL.md`.\n- Runtime\u002Fdaemon startup: read `..\u002Fruntime\u002FSKILL.md`.\n- Credential acquisition: read `..\u002Fauth-integrations\u002FSKILL.md`.\n\n## Operating procedure\n\n1. Prefer the canonical plan door: `graph propose` to validate and stage, then `graph commit` with explicit approval and verification as needed.\n2. Use `graph mutation-template` before authoring payloads when the DSL or entity label is uncertain.\n3. Keep mutations flat and retrieval-grade: durable descriptions, explicit scopes, source references, and no nested legacy wrappers unless the CLI specifically emits them.\n4. Use `graph inbox`, `graph quality`, `graph history`, and `graph inspect` to review pending, stale, or questionable graph state before applying more writes.\n5. Treat `record` as a convenient durable-memory write path and `graph nudge` as a bridge from graph evidence to agent guidance.\n\n## References\n\n- `references\u002Fworkflow.md` — write command matrix, flat mutation DSL, approval\u002Fverification, inbox, quality, bulk, and nudge flows.\n- `references\u002Ftroubleshooting.md` — malformed payloads, review gates, expired plans, bulk failures, inbox states, and quality repairs.\n\n## Verification notes\n\n- Safe native candidates include graph CLI contract, graph workbench plan\u002Finbox\u002Fquality tests, nudge service, apply-once, semantic mutation validation, semantic mutations, graph-plan compatibility, and graph-workbench ontology tests.\n- No accelerator backend is required for write-side CLI\u002Fcontract verification.\n",{"name":5,"license":24,"metadata":25,"description":7,"disable-model-invocation":27},"Apache 2.0",{"disco-role":26},"operating",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fpotpie\u002Fsub-skills\u002Fgraph-write",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":27},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill graph-write",{"tool":42,"command":43},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill graph-write",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill graph-write","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpotpie\u002Fsub-skills\u002Fgraph-write\u002FSKILL.md",[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ftroubleshooting.md","REFERENCE","参考文档",3139,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpotpie\u002Fsub-skills\u002Fgraph-write\u002Freferences\u002Ftroubleshooting.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fworkflow.md",3980,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpotpie\u002Fsub-skills\u002Fgraph-write\u002Freferences\u002Fworkflow.md",[60,68,73,80,87,94],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":64,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]