[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WZ1DM4TSD1F476WK862H6B":3,"skill-same:01M6WZ1DM4TSD1F476WK862H6B":108},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":14,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":77,"install":78,"resources":91},"01M6WZ1DM4TSD1F476WK862H6B","artifact-management",null,"Create, retrieve, query, and update Artifacts — tangible deliverables\nproduced by the project. Use when storing or retrieving documents,\ndesigns, datasets, build outputs, slide decks, or any completed\ndeliverable that should be registered in the project catalog.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"management","artifact management","artifact","get","when","outputs","Existing","v1","event","keep","slide decks","id","documents","project","query","log","use","catalog","sqlite","artifacts","2026-11-10 10:12:30",false,"---\nname: artifact-management\ndescription: |\n  Create, retrieve, query, and update Artifacts — tangible deliverables\n  produced by the project. Use when storing or retrieving documents,\n  designs, datasets, build outputs, slide decks, or any completed\n  deliverable that should be registered in the project catalog.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv1\n    id: SKILL-artifact-management\n    version: \"1.0.0\"\n    created: 2026-04-11T00:00:00Z\n    category: processkit\n    layer: 2\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n      - skill: index-management\n        purpose: Query existing entities and keep the SQLite index fresh after writes.\n      - skill: id-management\n        purpose: Allocate unique entity identifiers via central ID generation.\n    provides:\n      primitives: [Artifact]\n      mcp_tools: [create_artifact, get_artifact, query_artifacts, update_artifact]\n---\n\n# Artifact Management\n\n## Intro\n\nArtifacts are tangible deliverables — documents, design files,\ndatasets, build outputs, slide decks, videos, or external URLs.\nUnlike Notes (thoughts in transit), Artifacts are completed\ndeliverables registered in the project catalog. Unlike WorkItems\n(units of tracked work), Artifacts have no state lifecycle — they\nexist or they don't.\n\nTwo storage patterns are equally valid:\n\n- **Self-hosted**: the artifact content is the Markdown body of the\n  entity file; `spec.location` may reference the file's own path or\n  be omitted. Use for documents that belong in the repository (PRDs,\n  runbooks, research reports, work instructions).\n- **Pointer**: the deliverable lives elsewhere (external URL, cloud\n  storage, build artifact); `spec.location` is the canonical address.\n  processkit stores only the metadata card.\n\n> **MCP server.** This skill ships a self-contained MCP server at\n> `mcp\u002Fserver.py` (PEP 723 script — requires `uv` and Python ≥ 3.10\n> on PATH). Agent harnesses reach its tools by reading a single MCP\n> config file at startup, so the contents of `mcp\u002Fmcp-config.json`\n> must be merged into the harness's MCP config and placed at the\n> harness-specific path before this skill is usable.\n\n## Overview\n\n### Artifact kinds\n\n`spec.kind` classifies the artifact:\n\n| kind       | When to use                                             |\n|------------|---------------------------------------------------------|\n| `document` | Prose documents — PRDs, runbooks, reports, guides       |\n| `design`   | Design files — Figma, Excalidraw, wireframes            |\n| `dataset`  | Structured data — CSV, JSON, Parquet                    |\n| `build`    | Compiled outputs — binaries, bundles, tarballs          |\n| `slides`   | Presentation decks — PPTX, PDF slide decks              |\n| `video`    | Recorded content — demos, walkthroughs                  |\n| `spec`     | Formal specifications — OpenAPI, JSON Schema, proto     |\n| `diagram`  | Architecture and flow diagrams                          |\n| `url`      | External web resources, dashboards, hosted tools        |\n| `other`    | Anything that doesn't fit the above                     |\n\n### When to create an Artifact\n\nCreate an Artifact when:\n\n- A deliverable is complete enough to reference and share.\n- Something produced by the project should be discoverable later\n  (a report, a shipped binary, an approved design).\n- A Note has been promoted to a finished document.\n- A work item produced a document or design that should be cataloged.\n\nDo **not** create Artifacts for in-progress work — use a WorkItem\nor a Note while the thing is still being made.\n\n### Creating\n\n1. Choose `kind` from the table above.\n2. Write a short, descriptive `name`.\n3. Set `location` for pointer artifacts (URL, path, bucket key).\n   Omit or set to the entity file path for self-hosted artifacts.\n4. Set `produced_by` to the WorkItem or Process ID that produced it.\n5. Set `owner` to the responsible Actor ID.\n6. Add `tags` for retrieval (topic, project, format, etc.).\n7. Write the file to `context\u002Fartifacts\u002FART-\u003Cid>.md`.\n8. Log `artifact.created`.\n\n### Querying\n\nCommon queries via `query_artifacts`:\n\n- All artifacts of a given kind (e.g., all `document` artifacts)\n- All artifacts owned by an actor\n- All artifacts tagged with a given tag\n- Full-text search via `index-management`\n\n### Updating\n\nUse `update_artifact` to revise metadata (new version, updated\nlocation, changed owner). To replace the body content of a\nself-hosted artifact, update the Markdown body via `update_artifact`\nor by editing the file directly followed by reindex.\n\n## Gotchas\n\nAgent-specific failure modes:\n\n- **Creating an Artifact for in-progress work.** An Artifact is a\n  completed deliverable. If the thing isn't done yet, use a WorkItem\n  (for tracked work) or a Note (for an idea still forming). Premature\n  Artifact registration pollutes the catalog with incomplete items.\n- **Omitting `location` for pointer artifacts.** If the content lives\n  outside the repository (a URL, a cloud bucket path, a release\n  binary), `location` is the only way to find it. Omitting it makes\n  the catalog entry useless as a pointer.\n- **Duplicate registration.** Before `create_artifact`, run\n  `query_artifacts` and check for an existing entry with the same\n  name or location. Duplicates create confusion about which entry is\n  canonical.\n- **Using Artifact for ephemeral build outputs.** Not every build\n  artifact needs a catalog entry. Register the ones that matter for\n  the release, for compliance, or for future reference. Registering\n  every intermediate build output creates noise.\n- **Forgetting `produced_by`.** Linking the artifact back to the\n  WorkItem or Process that produced it is cheap and makes the\n  catalog navigable. Always set it when the provenance is known.\n\n## Full reference\n\n### Full field list\n\nSee `src\u002Fcontext\u002Fschemas\u002Fartifact.yaml` for the authoritative schema.\n\n| Field         | Required | Description                                           |\n|---------------|----------|-------------------------------------------------------|\n| `name`        | yes      | Human-readable name                                   |\n| `kind`        | yes      | Subtype (see table above)                             |\n| `location`    | no*      | Path, URL, or storage key (* required for pointers)   |\n| `format`      | no       | File format or MIME type (e.g. `pdf`, `image\u002Fpng`)    |\n| `version`     | no       | Version identifier for the artifact                   |\n| `checksum`    | no       | Hash for integrity verification                       |\n| `owner`       | no       | Actor ID responsible for the artifact                 |\n| `produced_by` | no       | Entity ID (WorkItem, Process) that produced this      |\n| `produced_at` | no       | ISO 8601 datetime when the artifact was produced      |\n| `tags`        | no       | Freeform tags for retrieval                           |\n\n### Note vs Artifact decision rule\n\n| State                           | Use       |\n|---------------------------------|-----------|\n| Idea, half-formed thought       | Note      |\n| In-progress document            | Note or WorkItem body |\n| Finished, shareable deliverable | Artifact  |\n| External resource to reference  | Artifact (pointer) |\n\n### Relationship to WorkItems\n\nA WorkItem is the unit of work that produces an Artifact. Link the\ntwo via `spec.produced_by` on the Artifact (pointing to the WorkItem\nID). This gives a navigable trail from deliverable back to the work\nthat created it.\n","# Artifact Management\n\n## Intro\n\nArtifacts are tangible deliverables — documents, design files,\ndatasets, build outputs, slide decks, videos, or external URLs.\nUnlike Notes (thoughts in transit), Artifacts are completed\ndeliverables registered in the project catalog. Unlike WorkItems\n(units of tracked work), Artifacts have no state lifecycle — they\nexist or they don't.\n\nTwo storage patterns are equally valid:\n\n- **Self-hosted**: the artifact content is the Markdown body of the\n  entity file; `spec.location` may reference the file's own path or\n  be omitted. Use for documents that belong in the repository (PRDs,\n  runbooks, research reports, work instructions).\n- **Pointer**: the deliverable lives elsewhere (external URL, cloud\n  storage, build artifact); `spec.location` is the canonical address.\n  processkit stores only the metadata card.\n\n> **MCP server.** This skill ships a self-contained MCP server at\n> `mcp\u002Fserver.py` (PEP 723 script — requires `uv` and Python ≥ 3.10\n> on PATH). Agent harnesses reach its tools by reading a single MCP\n> config file at startup, so the contents of `mcp\u002Fmcp-config.json`\n> must be merged into the harness's MCP config and placed at the\n> harness-specific path before this skill is usable.\n\n## Overview\n\n### Artifact kinds\n\n`spec.kind` classifies the artifact:\n\n| kind       | When to use                                             |\n|------------|---------------------------------------------------------|\n| `document` | Prose documents — PRDs, runbooks, reports, guides       |\n| `design`   | Design files — Figma, Excalidraw, wireframes            |\n| `dataset`  | Structured data — CSV, JSON, Parquet                    |\n| `build`    | Compiled outputs — binaries, bundles, tarballs          |\n| `slides`   | Presentation decks — PPTX, PDF slide decks              |\n| `video`    | Recorded content — demos, walkthroughs                  |\n| `spec`     | Formal specifications — OpenAPI, JSON Schema, proto     |\n| `diagram`  | Architecture and flow diagrams                          |\n| `url`      | External web resources, dashboards, hosted tools        |\n| `other`    | Anything that doesn't fit the above                     |\n\n### When to create an Artifact\n\nCreate an Artifact when:\n\n- A deliverable is complete enough to reference and share.\n- Something produced by the project should be discoverable later\n  (a report, a shipped binary, an approved design).\n- A Note has been promoted to a finished document.\n- A work item produced a document or design that should be cataloged.\n\nDo **not** create Artifacts for in-progress work — use a WorkItem\nor a Note while the thing is still being made.\n\n### Creating\n\n1. Choose `kind` from the table above.\n2. Write a short, descriptive `name`.\n3. Set `location` for pointer artifacts (URL, path, bucket key).\n   Omit or set to the entity file path for self-hosted artifacts.\n4. Set `produced_by` to the WorkItem or Process ID that produced it.\n5. Set `owner` to the responsible Actor ID.\n6. Add `tags` for retrieval (topic, project, format, etc.).\n7. Write the file to `context\u002Fartifacts\u002FART-\u003Cid>.md`.\n8. Log `artifact.created`.\n\n### Querying\n\nCommon queries via `query_artifacts`:\n\n- All artifacts of a given kind (e.g., all `document` artifacts)\n- All artifacts owned by an actor\n- All artifacts tagged with a given tag\n- Full-text search via `index-management`\n\n### Updating\n\nUse `update_artifact` to revise metadata (new version, updated\nlocation, changed owner). To replace the body content of a\nself-hosted artifact, update the Markdown body via `update_artifact`\nor by editing the file directly followed by reindex.\n\n## Gotchas\n\nAgent-specific failure modes:\n\n- **Creating an Artifact for in-progress work.** An Artifact is a\n  completed deliverable. If the thing isn't done yet, use a WorkItem\n  (for tracked work) or a Note (for an idea still forming). Premature\n  Artifact registration pollutes the catalog with incomplete items.\n- **Omitting `location` for pointer artifacts.** If the content lives\n  outside the repository (a URL, a cloud bucket path, a release\n  binary), `location` is the only way to find it. Omitting it makes\n  the catalog entry useless as a pointer.\n- **Duplicate registration.** Before `create_artifact`, run\n  `query_artifacts` and check for an existing entry with the same\n  name or location. Duplicates create confusion about which entry is\n  canonical.\n- **Using Artifact for ephemeral build outputs.** Not every build\n  artifact needs a catalog entry. Register the ones that matter for\n  the release, for compliance, or for future reference. Registering\n  every intermediate build output creates noise.\n- **Forgetting `produced_by`.** Linking the artifact back to the\n  WorkItem or Process that produced it is cheap and makes the\n  catalog navigable. Always set it when the provenance is known.\n\n## Full reference\n\n### Full field list\n\nSee `src\u002Fcontext\u002Fschemas\u002Fartifact.yaml` for the authoritative schema.\n\n| Field         | Required | Description                                           |\n|---------------|----------|-------------------------------------------------------|\n| `name`        | yes      | Human-readable name                                   |\n| `kind`        | yes      | Subtype (see table above)                             |\n| `location`    | no*      | Path, URL, or storage key (* required for pointers)   |\n| `format`      | no       | File format or MIME type (e.g. `pdf`, `image\u002Fpng`)    |\n| `version`     | no       | Version identifier for the artifact                   |\n| `checksum`    | no       | Hash for integrity verification                       |\n| `owner`       | no       | Actor ID responsible for the artifact                 |\n| `produced_by` | no       | Entity ID (WorkItem, Process) that produced this      |\n| `produced_at` | no       | ISO 8601 datetime when the artifact was produced      |\n| `tags`        | no       | Freeform tags for retrieval                           |\n\n### Note vs Artifact decision rule\n\n| State                           | Use       |\n|---------------------------------|-----------|\n| Idea, half-formed thought       | Note      |\n| In-progress document            | Note or WorkItem body |\n| Finished, shareable deliverable | Artifact  |\n| External resource to reference  | Artifact (pointer) |\n\n### Relationship to WorkItems\n\nA WorkItem is the unit of work that produces an Artifact. Link the\ntwo via `spec.produced_by` on the Artifact (pointing to the WorkItem\nID). This gives a navigable trail from deliverable back to the work\nthat created it.\n",{"name":5,"metadata":44,"description":70},{"processkit":45},{"id":46,"uses":47,"layer":57,"created":58,"version":59,"category":60,"provides":61,"apiVersion":69},"SKILL-artifact-management",[48,51,54],{"skill":49,"purpose":50},"event-log","Log events to keep the audit trail accurate after every write.",{"skill":52,"purpose":53},"index-management","Query existing entities and keep the SQLite index fresh after writes.",{"skill":55,"purpose":56},"id-management","Allocate unique entity identifiers via central ID generation.",2,1775865600000,"1.0.0","processkit",{"mcp_tools":62,"primitives":67},[63,64,65,66],"create_artifact","get_artifact","query_artifacts","update_artifact",[68],"Artifact","processkit.projectious.work\u002Fv1","Create, retrieve, query, and update Artifacts — tangible deliverables\nproduced by the project. Use when storing or retrieving documents,\ndesigns, datasets, build outputs, slide decks, or any completed\ndeliverable that should be registered in the project catalog.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add projectious-work\u002Fprocesskit --skill artifact-management",{"tool":84,"command":85},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill artifact-management",{"tool":87,"command":88},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill artifact-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management\u002FSKILL.md",true,[92,98,102],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"mcp\u002Fmcp-config.json","REFERENCE","参考文档",221,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management\u002Fmcp\u002Fmcp-config.json",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"mcp\u002FSERVER.md",1230,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management\u002Fmcp\u002FSERVER.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"mcp\u002Fserver.py","SCRIPT","脚本",9553,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.17.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fartifact-management\u002Fmcp\u002Fserver.py",[109,134,154,172,188,206],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":39},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[19,121,122,123,124,125,126,127,128,129,111,22,130,131,26,132,133],"skill management","create","update","package","alpha","work","list","manage","ontology","as","manifests","skill package","transition",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":39},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[140],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[19,142,143,144,145,146,125,126,147,148,128,149,150,151,22,152,153],"schema","schema management","MCP","workflows","validation","generated","rebuild","contracts","wed","deterministic","contract","mode",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":39},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[19,161,162,122,123,163,125,126,34,164,165,33,22,166,27,167,168,169,170,171],"proposition","proposition management","index","world","record","creation","interface","updates","facts","claims","WSJF",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":39},"01M6X5KMQ83QN9M6MPWZM7344F","ontology-management","Manage generated v1 ontology entities that do not require a dedicated domain server.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fontology-management\u002FSKILL.md",[],[19,129,179,122,125,180,181,147,182,34,128,183,184,22,185,28,27,186,26,187],"ontology management","lifecycle","archive","roadmap","do","domain","iteration","measurement","generic",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":39},"01M6X5KCY2DN3SM21RERSFNEBT","okf-compatibility","Import, export, and validate conformant Open Knowledge Format bundles.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fokf-compatibility\u002FSKILL.md",[],[195,196,197,198,125,199,200,201,126,202,203,204,205],"okf","compatibility","okf compatibility","validate","open","knowledge","format","export","bundles","bundle","import",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":212,"publishedAt":39},"01M6X5JA8S5PNGJVFW4EQY8T83","capability-management","Manage versioned Capability entities and their governed lifecycle.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcapability-management\u002FSKILL.md",[],[19,213,214,122,123,163,125,180,126,127,34,215,128,165,22,28,27,167,216,133],"capability","capability management","queries","changes"]