[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NQ7MJGF2C020HNWW5Q89CJ":3,"skill-same:01M6NQ7MJGF2C020HNWW5Q89CJ":130},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":80,"commitSha":81,"skillDirectory":82,"forksCount":14,"repositoryHtmlUrl":83,"repositoryHomepageUrl":84,"ownerHtmlUrl":85,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":86,"install":87,"resources":100},"01M6NQ7MJGF2C020HNWW5Q89CJ","actor-profile",null,"Create and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences\u002Fexpertise, or querying who does what.","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\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"actor profile","profile","project","Existing","event","keep","via","id","fresh","generation","get","ai agents","query","maintain","log","use","work","preferences","sqlite","create","2026-11-10 10:12:30",false,"---\nname: actor-profile\ndescription: |\n  Create and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences\u002Fexpertise, or querying who does what.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-actor-profile\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: processkit\n    layer: 1\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: [Actor]\n      mcp_tools:\n        - create_actor\n        - get_actor\n        - update_actor\n        - deactivate_actor\n        - list_actors\n      templates: [actor-human, actor-agent]\n---\n\n# Actor Profile Management\n\n## Intro\n\nActors are the entities that do things in the project — humans, AI agents, and\nservices. This skill creates and maintains their profiles: name, type, contact,\nexpertise, preferences, working style.\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 on\n> PATH). Agent harnesses reach its tools by reading a single MCP config\n> file at startup, so the contents of `mcp\u002Fmcp-config.json` must be merged\n> into the harness's MCP config and placed at the harness-specific path\n> before this skill is usable. If processkit was installed by an installer,\n> that wiring is the installer's responsibility; if processkit was\n> installed manually, the project owner must do it by hand.\n\n## Actor ID classes\n\nTwo accepted ID shapes for Actor entities (see `context\u002Fschemas\u002Factor.yaml`\n`spec.role_actor_ids` and `DEC-20260421_2036-SoundIvy-two-class-actor-ids`):\n\n**Role actor** — `ACTOR-\u003Ckebab-slug>`\n\nStable identifier for a durable team role filled by successive agents or\npeople (e.g. `ACTOR-product-manager`, `ACTOR-sr-architect`). Current\nallowlist (from `spec.role_actor_ids` in `actor.yaml`): `assistant`,\n`developer`, `jr-architect`, `jr-developer`, `jr-researcher`,\n`product-manager`,\n`sr-architect`, `sr-researcher`. Use when the actor represents a role, not\nan individual.\n\n**Identity actor** — `ACTOR-\u003CYYYYMMDD_HHMM>-\u003CWordPair>-\u003Cslug>`\n\nCanonical id-management format. Use for a specific individual, session, or\nhistorical figure (owner, legacy backfill, session-specific agent). Example:\n`ACTOR-20260421_0144-ThriftyOtter-owner`.\n\n**Adding a role to the allowlist**\n\nRequires amending `spec.role_actor_ids` in `context\u002Fschemas\u002Factor.yaml`\n(and its `src\u002F` mirror). This is a cross-cutting schema change — record a\nDecisionRecord explaining why the new role is needed before making the\nchange. pk-doctor will ERROR on any `ACTOR-\u003Cslug>` ID whose slug is not in\nthe allowlist.\n\n## Overview\n\n### When to create an Actor\n\nCreate an Actor entity the first time a person or agent participates in a\nway the project needs to remember:\n- Someone gets assigned a WorkItem → create their Actor if missing.\n- An agent starts making decisions → create its Actor.\n- A service account performs automated actions → create its Actor.\n\nDo **not** promote every mention of a person into an Actor. Actors are for\ncollaborators with ongoing involvement, not for every name that appears in a\ncommit message.\n\n### Actor types\n\n| type         | Example                                     |\n|--------------|---------------------------------------------|\n| `human`      | Project members, reviewers, stakeholders    |\n| `ai-agent`   | Claude, Copilot, Aider, Cursor, custom MCP  |\n| `service`    | GitHub Actions, CI bots, deploy pipelines   |\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Actor\nmetadata:\n  id: ACTOR-alice\n  created: 2026-04-06T00:00:00Z\nspec:\n  type: human\n  name: \"Alice Chen\"\n  email: alice@example.com\n  expertise: [backend, databases, rust]\n  preferences:\n    commit_style: conventional\n    timezone: Europe\u002FBerlin\n  active: true\n---\n\nOptional Markdown body — bio, context, working-style notes.\n```\n\n### Workflow\n\n1. Pick an ID: `ACTOR-\u003Cshort-name>` where short-name is memorable and unique.\n2. Set `type` (human \u002F ai-agent \u002F service).\n3. Fill in `name` + contact (email for humans; nothing for agents; service\n   account identifier for services).\n4. Record `expertise` as a tag list — used by assignment skills.\n5. Write the Actor file to `context\u002Factors\u002F`.\n6. Log a `LogEntry` with `event_type: actor.created`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Creating an Actor for every name mentioned in a commit or\n  comment.** Actors are for collaborators with ongoing involvement,\n  not for every string that looks like a name. If the person doesn't\n  have at least one upcoming WorkItem, decision, or Binding pointing\n  at them, don't create the Actor yet.\n- **Putting personal or sensitive information in a public Actor file.**\n  Personal context (relationship dynamics, private preferences,\n  personal contact info) belongs in `context\u002Fowner\u002Fprivate\u002F...` with\n  `privacy: user-private`, not in the Actor entity which defaults to\n  project-visible. Check the privacy field on the entity before\n  writing sensitive content.\n- **Setting `type` wrong.** `human` \u002F `ai-agent` \u002F `service` aren't\n  cosmetic — other skills filter on type (e.g., to send a Slack ping\n  only to humans, or to auto-promote service-account actions). Wrong\n  type causes silent miscategorization downstream.\n- **Updating an Actor when the relationship is what changed.** If\n  Alice's role on the project changed, that's a new Binding (or\n  ending the old one), NOT an update to her Actor. The Actor is\n  who she IS; the Binding is what she's DOING.\n- **Reusing a name as an ID for two distinct people.** Two\n  collaborators named \"Alice\" need distinct Actor IDs\n  (`ACTOR-alice-pm` vs `ACTOR-alice-eng`). The ID is forever; the\n  display name is mutable. Disambiguate at creation time, not later.\n- **Hallucinating Actor IDs when other skills reference them.** If\n  workitem-management is asked to assign a workitem to \"Bob\", look\n  up `ACTOR-bob` (or all `ACTOR-bob-*`) via `index-management` first.\n  Inventing an ID like `ACTOR-bob` without verifying creates a\n  dangling reference that breaks at the next index validation.\n- **Forgetting to log `actor.created`.** Use `event-log` after every\n  Actor creation. The audit trail tracks \"who joined when\", and\n  skipping the log makes \"when did Alice start working on this?\"\n  unanswerable.\n\n## Full reference\n\n### Fields\n\n| Field           | Type              | Notes                                                     |\n|-----------------|-------------------|-----------------------------------------------------------|\n| `type`          | enum              | `human` \u002F `ai-agent` \u002F `service`                          |\n| `name`          | string            | Display name. For agents: model name + version.           |\n| `email`         | string            | Optional. Human actors only.                              |\n| `handle`        | string            | Optional. GitHub handle, Slack user, etc.                 |\n| `expertise`     | list[string]      | Tags used by assignment suggestions.                      |\n| `roles`         | list[string]      | Role IDs. For scoped roles prefer a Binding over this.    |\n| `preferences`   | map               | Free-form. See conventional keys below.                   |\n| `active`        | bool              | `false` = profile preserved but no new work assigned.     |\n| `joined_at`     | datetime          | When they became part of the project.                     |\n| `left_at`       | datetime          | When they stopped (sets `active: false`).                  |\n\n### Conventional preference keys\n\n- `commit_style`: `conventional` \u002F `freeform`\n- `timezone`: IANA name\n- `review_style`: `strict` \u002F `pragmatic` \u002F `light`\n- `communication`: `async` \u002F `sync` \u002F `mixed`\n- `languages`: human languages for communication\n\nThese are conventions, not enforced. Projects may add any preferences they like.\n\n### Scoped roles: use a Binding, not the `roles` field\n\n`spec.roles` is a shortcut for \"Alice is a developer\" when that's true\neverywhere in the project. If \"Alice is the tech lead for Project X but a\nregular developer everywhere else\", use a Binding entity instead:\n\n```yaml\nkind: Binding\nspec:\n  type: role-assignment\n  subject: ACTOR-alice\n  target: ROLE-tech-lead\n  scope: SCOPE-project-x\n```\n\nSee `skills\u002Fbinding-management` for details.\n\n### Deactivation, not deletion\n\nWhen an actor leaves the project, set `active: false` and `left_at`. Do not\ndelete the file — historical LogEntries and Bindings reference it. Queries\nfor \"current team\" should filter by `active: true`.\n\n### Privacy considerations\n\nActor files are checked into git and visible to everyone with repo access.\nDo not put sensitive contact info (phone, home address) in Actor files.\nKeep email optional — agents and services do not need one.\n","# Actor Profile Management\n\n## Intro\n\nActors are the entities that do things in the project — humans, AI agents, and\nservices. This skill creates and maintains their profiles: name, type, contact,\nexpertise, preferences, working style.\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 on\n> PATH). Agent harnesses reach its tools by reading a single MCP config\n> file at startup, so the contents of `mcp\u002Fmcp-config.json` must be merged\n> into the harness's MCP config and placed at the harness-specific path\n> before this skill is usable. If processkit was installed by an installer,\n> that wiring is the installer's responsibility; if processkit was\n> installed manually, the project owner must do it by hand.\n\n## Actor ID classes\n\nTwo accepted ID shapes for Actor entities (see `context\u002Fschemas\u002Factor.yaml`\n`spec.role_actor_ids` and `DEC-20260421_2036-SoundIvy-two-class-actor-ids`):\n\n**Role actor** — `ACTOR-\u003Ckebab-slug>`\n\nStable identifier for a durable team role filled by successive agents or\npeople (e.g. `ACTOR-product-manager`, `ACTOR-sr-architect`). Current\nallowlist (from `spec.role_actor_ids` in `actor.yaml`): `assistant`,\n`developer`, `jr-architect`, `jr-developer`, `jr-researcher`,\n`product-manager`,\n`sr-architect`, `sr-researcher`. Use when the actor represents a role, not\nan individual.\n\n**Identity actor** — `ACTOR-\u003CYYYYMMDD_HHMM>-\u003CWordPair>-\u003Cslug>`\n\nCanonical id-management format. Use for a specific individual, session, or\nhistorical figure (owner, legacy backfill, session-specific agent). Example:\n`ACTOR-20260421_0144-ThriftyOtter-owner`.\n\n**Adding a role to the allowlist**\n\nRequires amending `spec.role_actor_ids` in `context\u002Fschemas\u002Factor.yaml`\n(and its `src\u002F` mirror). This is a cross-cutting schema change — record a\nDecisionRecord explaining why the new role is needed before making the\nchange. pk-doctor will ERROR on any `ACTOR-\u003Cslug>` ID whose slug is not in\nthe allowlist.\n\n## Overview\n\n### When to create an Actor\n\nCreate an Actor entity the first time a person or agent participates in a\nway the project needs to remember:\n- Someone gets assigned a WorkItem → create their Actor if missing.\n- An agent starts making decisions → create its Actor.\n- A service account performs automated actions → create its Actor.\n\nDo **not** promote every mention of a person into an Actor. Actors are for\ncollaborators with ongoing involvement, not for every name that appears in a\ncommit message.\n\n### Actor types\n\n| type         | Example                                     |\n|--------------|---------------------------------------------|\n| `human`      | Project members, reviewers, stakeholders    |\n| `ai-agent`   | Claude, Copilot, Aider, Cursor, custom MCP  |\n| `service`    | GitHub Actions, CI bots, deploy pipelines   |\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Actor\nmetadata:\n  id: ACTOR-alice\n  created: 2026-04-06T00:00:00Z\nspec:\n  type: human\n  name: \"Alice Chen\"\n  email: alice@example.com\n  expertise: [backend, databases, rust]\n  preferences:\n    commit_style: conventional\n    timezone: Europe\u002FBerlin\n  active: true\n---\n\nOptional Markdown body — bio, context, working-style notes.\n```\n\n### Workflow\n\n1. Pick an ID: `ACTOR-\u003Cshort-name>` where short-name is memorable and unique.\n2. Set `type` (human \u002F ai-agent \u002F service).\n3. Fill in `name` + contact (email for humans; nothing for agents; service\n   account identifier for services).\n4. Record `expertise` as a tag list — used by assignment skills.\n5. Write the Actor file to `context\u002Factors\u002F`.\n6. Log a `LogEntry` with `event_type: actor.created`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Creating an Actor for every name mentioned in a commit or\n  comment.** Actors are for collaborators with ongoing involvement,\n  not for every string that looks like a name. If the person doesn't\n  have at least one upcoming WorkItem, decision, or Binding pointing\n  at them, don't create the Actor yet.\n- **Putting personal or sensitive information in a public Actor file.**\n  Personal context (relationship dynamics, private preferences,\n  personal contact info) belongs in `context\u002Fowner\u002Fprivate\u002F...` with\n  `privacy: user-private`, not in the Actor entity which defaults to\n  project-visible. Check the privacy field on the entity before\n  writing sensitive content.\n- **Setting `type` wrong.** `human` \u002F `ai-agent` \u002F `service` aren't\n  cosmetic — other skills filter on type (e.g., to send a Slack ping\n  only to humans, or to auto-promote service-account actions). Wrong\n  type causes silent miscategorization downstream.\n- **Updating an Actor when the relationship is what changed.** If\n  Alice's role on the project changed, that's a new Binding (or\n  ending the old one), NOT an update to her Actor. The Actor is\n  who she IS; the Binding is what she's DOING.\n- **Reusing a name as an ID for two distinct people.** Two\n  collaborators named \"Alice\" need distinct Actor IDs\n  (`ACTOR-alice-pm` vs `ACTOR-alice-eng`). The ID is forever; the\n  display name is mutable. Disambiguate at creation time, not later.\n- **Hallucinating Actor IDs when other skills reference them.** If\n  workitem-management is asked to assign a workitem to \"Bob\", look\n  up `ACTOR-bob` (or all `ACTOR-bob-*`) via `index-management` first.\n  Inventing an ID like `ACTOR-bob` without verifying creates a\n  dangling reference that breaks at the next index validation.\n- **Forgetting to log `actor.created`.** Use `event-log` after every\n  Actor creation. The audit trail tracks \"who joined when\", and\n  skipping the log makes \"when did Alice start working on this?\"\n  unanswerable.\n\n## Full reference\n\n### Fields\n\n| Field           | Type              | Notes                                                     |\n|-----------------|-------------------|-----------------------------------------------------------|\n| `type`          | enum              | `human` \u002F `ai-agent` \u002F `service`                          |\n| `name`          | string            | Display name. For agents: model name + version.           |\n| `email`         | string            | Optional. Human actors only.                              |\n| `handle`        | string            | Optional. GitHub handle, Slack user, etc.                 |\n| `expertise`     | list[string]      | Tags used by assignment suggestions.                      |\n| `roles`         | list[string]      | Role IDs. For scoped roles prefer a Binding over this.    |\n| `preferences`   | map               | Free-form. See conventional keys below.                   |\n| `active`        | bool              | `false` = profile preserved but no new work assigned.     |\n| `joined_at`     | datetime          | When they became part of the project.                     |\n| `left_at`       | datetime          | When they stopped (sets `active: false`).                  |\n\n### Conventional preference keys\n\n- `commit_style`: `conventional` \u002F `freeform`\n- `timezone`: IANA name\n- `review_style`: `strict` \u002F `pragmatic` \u002F `light`\n- `communication`: `async` \u002F `sync` \u002F `mixed`\n- `languages`: human languages for communication\n\nThese are conventions, not enforced. Projects may add any preferences they like.\n\n### Scoped roles: use a Binding, not the `roles` field\n\n`spec.roles` is a shortcut for \"Alice is a developer\" when that's true\neverywhere in the project. If \"Alice is the tech lead for Project X but a\nregular developer everywhere else\", use a Binding entity instead:\n\n```yaml\nkind: Binding\nspec:\n  type: role-assignment\n  subject: ACTOR-alice\n  target: ROLE-tech-lead\n  scope: SCOPE-project-x\n```\n\nSee `skills\u002Fbinding-management` for details.\n\n### Deactivation, not deletion\n\nWhen an actor leaves the project, set `active: false` and `left_at`. Do not\ndelete the file — historical LogEntries and Bindings reference it. Queries\nfor \"current team\" should filter by `active: true`.\n\n### Privacy considerations\n\nActor files are checked into git and visible to everyone with repo access.\nDo not put sensitive contact info (phone, home address) in Actor files.\nKeep email optional — agents and services do not need one.\n",{"name":5,"metadata":49,"description":79},{"processkit":50},{"id":51,"uses":52,"layer":62,"created":63,"version":64,"category":65,"provides":66,"apiVersion":78},"SKILL-actor-profile",[53,56,59],{"skill":54,"purpose":55},"event-log","Log events to keep the audit trail accurate after every write.",{"skill":57,"purpose":58},"index-management","Query existing entities and keep the SQLite index fresh after writes.",{"skill":60,"purpose":61},"id-management","Allocate unique entity identifiers via central ID generation.",1,1775433600000,"1.0.0","processkit",{"mcp_tools":67,"templates":73,"primitives":76},[68,69,70,71,72],"create_actor","get_actor","update_actor","deactivate_actor","list_actors",[74,75],"actor-human","actor-agent",[77],"Actor","processkit.projectious.work\u002Fv2","Create and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences\u002Fexpertise, or querying who does what.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile","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":88,"prompt":98,"zipAvailable":99},[89,92,95],{"tool":90,"command":91},"npx","npx skills add projectious-work\u002Fprocesskit --skill actor-profile",{"tool":93,"command":94},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill actor-profile",{"tool":96,"command":97},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill actor-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002FSKILL.md",true,[101,107,111,117,121,127],{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"assets\u002Factor-agent.yaml","ASSET","资产文件",259,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fassets\u002Factor-agent.yaml",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"assets\u002Factor-human.yaml",294,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fassets\u002Factor-human.yaml",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"mcp\u002Fmcp-config.json","REFERENCE","参考文档",209,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fmcp\u002Fmcp-config.json",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"mcp\u002FSERVER.md",1407,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fmcp\u002FSERVER.md",{"path":122,"resourceType":123,"resourceTypeDesc":124,"sizeBytes":125,"sourceHtmlUrl":126},"mcp\u002Fserver.py","SCRIPT","脚本",10910,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fmcp\u002Fserver.py",{"path":128,"resourceType":123,"resourceTypeDesc":124,"sizeBytes":14,"sourceHtmlUrl":129},"scripts\u002F.gitkeep","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Factor-profile\u002Fscripts\u002F.gitkeep",[131,138,145,151,172,192],{"skillNo":132,"name":133,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":137},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":137},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":137},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":44},"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",[157],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,160,161,162,43,163,40,164,34,165,166,167,153,168,169,170,171],"management","skill management","ontology","v1","as","transition","manage","update","alpha","list","package","skill package","manifests",{"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":179,"publishedAt":44},"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",[178],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[180,181,159,182,183,184,185,186,187,188,189,190,40,34,165,167,191],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":44},"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",[],[199,159,200,201,43,202,203,204,40,34,205,28,166,206,167,207,208,36,209,38],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","facts"]