[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPQ84XBEMTEZDCKM56YR3H":3,"skill-same:01M6NPQ84XBEMTEZDCKM56YR3H":121},{"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":76,"commitSha":77,"skillDirectory":78,"forksCount":14,"repositoryHtmlUrl":79,"repositoryHomepageUrl":80,"ownerHtmlUrl":81,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":82,"install":83,"resources":96},"01M6NPQ84XBEMTEZDCKM56YR3H","repo-management",null,"Reconcile repository issues, pull requests, merge requests, local git state, commits, and pushes across GitHub, GitLab, Gitea, Forgejo, Codeberg, Bitbucket, Azure DevOps, and SourceHut.","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\u002Fdevops\u002Frepo-management\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],"repo management","management","repo","branch","inspect","scope","local","across","reconciliation","bitbucket","pull requests","work","plan","issues","run","gitlab","azure devops","merge","commit","change","2026-11-10 10:12:30",false,"---\nname: repo-management\ndescription: >\n  Reconcile repository issues, pull requests, merge requests, local git\n  state, commits, and pushes across GitHub, GitLab, Gitea, Forgejo,\n  Codeberg, Bitbucket, Azure DevOps, and SourceHut.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-repo-management\n    version: \"1.0.0\"\n    created: 2026-05-15T00:00:00Z\n    category: devops\n    layer: null\n    provides:\n      primitives: []\n      mcp_tools:\n        - detect_repo_provider\n        - inspect_repo_state\n        - list_repo_issues\n        - list_repo_change_requests\n        - plan_repo_reconcile\n        - resolve_repo_issue\n        - merge_change_request\n        - commit_local_changes\n        - push_current_branch\n        - run_repo_reconcile\n      assets: []\n    commands:\n      - name: pk-repo-reconcile\n        args: \"scope (optional: all, issues, prs, local, push)\"\n        description: \"Plan and apply guarded repository reconciliation across issues, change requests, local commits, and pushes.\"\n---\n\n# Repo Management\n\n## Intro\n\n`repo-management` gives agents a provider-neutral workflow for routine\nrepository stewardship: inspect open issues and change requests, plan\nsafe actions, merge only ready work, commit local changes, and push.\nUse it when the user asks to check all open issues or PRs, clean up a\nrepo, reconcile repository state, merge ready work, commit and push, or\nperform repo-maintenance across providers.\n\n## Overview\n\nThe default workflow is plan-first and guarded:\n\n1. Call `detect_repo_provider(project_root, remote)` to identify the\n   remote platform and available local CLI.\n2. Call `inspect_repo_state(project_root)` to inspect branch, dirty\n   state, upstream, ahead\u002Fbehind status, remotes, and provider support.\n3. Call `list_repo_issues()` and `list_repo_change_requests()` for the\n   current provider when supported.\n4. Call `plan_repo_reconcile(scope)` to build a concrete action plan.\n5. Apply only actions that pass the safety rules below. Use\n   `run_repo_reconcile(dry_run=false)` for guarded batch work, or call\n   the narrow mutating tools directly.\n\nWhen the task involves branch policy, review judgment, or release work,\nalso follow the local `git-workflow`, `code-review`, and\n`release-semver` skill guidance.\n\n`\u002Fpk-repo-reconcile` is the user command for the same workflow. Without\nextra arguments it means `scope=all`: local git state, open issues,\nopen change requests, and push readiness. Users may narrow it with\n`issues`, `prs`, `local`, or `push`.\n\n### Provider support\n\n| Provider | Detection | Read support | Mutating support |\n|---|---|---|---|\n| GitHub | `github.com` remotes | `gh issue list`, `gh pr list` | issue comments\u002Fclose, PR merge, commit, push |\n| GitLab | `gitlab.com` or `REPO_PROVIDER=gitlab` | capability report, local git | local commit\u002Fpush only |\n| Gitea | `REPO_PROVIDER=gitea` | capability report, local git | local commit\u002Fpush only |\n| Forgejo \u002F Codeberg | `codeberg.org` or `REPO_PROVIDER=forgejo` | capability report, local git | local commit\u002Fpush only |\n| Bitbucket Cloud | `bitbucket.org` remotes | capability report, local git | local commit\u002Fpush only |\n| Azure DevOps | `dev.azure.com` or `visualstudio.com` remotes | capability report, local git | local commit\u002Fpush only |\n| SourceHut | `git.sr.ht` remotes | capability report, local git | local commit\u002Fpush only |\n\nUnsupported provider actions must return structured evidence instead\nof pretending the work is complete. Agents should still commit and push\nlocal changes through git when the repository policy allows it.\n\n### MCP tools\n\n| Tool | Purpose |\n|---|---|\n| `detect_repo_provider(project_root, remote)` | Detect remote host, owner\u002Frepo, provider, and local CLI availability. |\n| `inspect_repo_state(project_root, include_remote)` | Inspect branch, dirty state, upstream, ahead\u002Fbehind, remotes, and provider capabilities. |\n| `list_repo_issues(state, limit)` | List open issues when the provider adapter supports it. |\n| `list_repo_change_requests(state, limit)` | List open PRs\u002FMRs\u002Fchange requests when supported. |\n| `plan_repo_reconcile(scope, dry_run)` | Produce the action plan and blockers without mutating. |\n| `resolve_repo_issue(id, resolution, comment, close, confirmation)` | Comment and optionally close a supported issue. |\n| `merge_change_request(id, method, auto_queue, confirmation)` | Merge or queue a supported ready change request. |\n| `commit_local_changes(paths, message, checks)` | Run optional checks, stage paths, and commit local changes. |\n| `push_current_branch(remote, branch)` | Push the current branch to its remote. |\n| `run_repo_reconcile(dry_run, max_items, commit_message, push)` | Apply the guarded batch workflow. |\n\n## Gotchas\n\n- **Do not close issues without evidence.** A close action needs a\n  linked merged change, a duplicate reference, a clear no-repro\n  disposition, or explicit user instruction.\n- **Do not merge drafts or WIP change requests.** Draft state is a hard\n  blocker even if checks are green.\n- **Do not bypass branch protection.** Never force-push, override\n  required reviews, skip required checks, or bypass merge queues.\n- **Do not assume GitHub-only behavior.** Detect the provider first and\n  return unsupported evidence for adapters that are not configured.\n- **Do not treat listing as resolving.** If issues or change requests\n  remain open, report the plan or blocker that remains.\n- **Do not push unrelated local work blindly.** Inspect `git status`\n  and commit only the intended paths or the current complete worktree\n  when the user asked for all local changes.\n- **Do not run mutating batch actions without a dry-run plan.**\n  `run_repo_reconcile(dry_run=false)` should report the plan it applied\n  and every command result.\n- **Do not hide external auth failures.** Missing `gh`, `glab`, `tea`,\n  `bb`, `az`, or `hut` authentication is an actionable blocker, not a\n  successful no-op.\n- **Do not assume a reused gateway sees newly exported credentials.** A\n  long-lived daemon cannot inherit later shell environment changes. Configure\n  an owner-only token file for refreshable GitHub CLI authentication.\n\n## Full reference\n\n### Safety policy\n\nThe skill is deliberately conservative:\n\n- No force pushes.\n- No direct API bypass of provider protection rules.\n- No draft\u002FWIP merge.\n- No issue close without a comment or explicit resolution evidence.\n- Mutating issue and merge tools require exact confirmation tokens:\n  `close-issue:\u003Cid>` and `merge-change-request:\u003Cid>`.\n- Provider-specific actions are serialized by the caller; batch tools\n  return per-action evidence.\n\n### Scope names\n\n`plan_repo_reconcile()` and `\u002Fpk-repo-reconcile` accept these scopes:\n\n| Scope | Includes |\n|---|---|\n| `all` | local, push, issues, and change requests |\n| `local` | dirty state and commit readiness |\n| `push` | ahead\u002Fbehind and push readiness |\n| `issues` | open issue listing and resolution candidates |\n| `prs` | open pull requests, merge requests, or provider change requests |\n| `change-requests` | Alias for `prs` |\n\n### Provider notes\n\nGitHub is the first fully mutating adapter because the `gh` CLI is\ncommon in aibox environments and enforces provider-side checks. GitLab,\nGitea, Forgejo\u002FCodeberg, Bitbucket Cloud, Azure DevOps, and SourceHut\nare first-class provider identities in the schema and detection layer;\ntheir remote issue and change-request mutation paths return\n`unsupported` until the matching local CLI or API credential contract is\nimplemented.\n\n### Long-lived gateway GitHub authentication\n\nThe gateway daemon and direct stdio servers continue to support normal `gh`\nauthentication through `GH_TOKEN`, `GITHUB_TOKEN`, `GH_ENTERPRISE_TOKEN`,\n`GITHUB_ENTERPRISE_TOKEN`, and the GitHub CLI config or keyring.\n\nFor a long-lived daemon that must observe token rotation without a restart,\nset `PROCESSKIT_GITHUB_TOKEN_FILE` to a regular file owned by the gateway user\nwith mode `0600`. The file must contain only the token. GitHub Enterprise may\nuse `PROCESSKIT_GITHUB_ENTERPRISE_TOKEN_FILE` instead. The file is read\nimmediately before every `gh` call and injected only into that child process.\nDirect token environment variables take precedence.\n\nToken values are never added to MCP arguments, command results, diagnostics,\nthe gateway catalog, or tracked MCP configuration. A shared daemon has one\nGitHub identity; use isolated daemons when clients require separate identities.\n","# Repo Management\n\n## Intro\n\n`repo-management` gives agents a provider-neutral workflow for routine\nrepository stewardship: inspect open issues and change requests, plan\nsafe actions, merge only ready work, commit local changes, and push.\nUse it when the user asks to check all open issues or PRs, clean up a\nrepo, reconcile repository state, merge ready work, commit and push, or\nperform repo-maintenance across providers.\n\n## Overview\n\nThe default workflow is plan-first and guarded:\n\n1. Call `detect_repo_provider(project_root, remote)` to identify the\n   remote platform and available local CLI.\n2. Call `inspect_repo_state(project_root)` to inspect branch, dirty\n   state, upstream, ahead\u002Fbehind status, remotes, and provider support.\n3. Call `list_repo_issues()` and `list_repo_change_requests()` for the\n   current provider when supported.\n4. Call `plan_repo_reconcile(scope)` to build a concrete action plan.\n5. Apply only actions that pass the safety rules below. Use\n   `run_repo_reconcile(dry_run=false)` for guarded batch work, or call\n   the narrow mutating tools directly.\n\nWhen the task involves branch policy, review judgment, or release work,\nalso follow the local `git-workflow`, `code-review`, and\n`release-semver` skill guidance.\n\n`\u002Fpk-repo-reconcile` is the user command for the same workflow. Without\nextra arguments it means `scope=all`: local git state, open issues,\nopen change requests, and push readiness. Users may narrow it with\n`issues`, `prs`, `local`, or `push`.\n\n### Provider support\n\n| Provider | Detection | Read support | Mutating support |\n|---|---|---|---|\n| GitHub | `github.com` remotes | `gh issue list`, `gh pr list` | issue comments\u002Fclose, PR merge, commit, push |\n| GitLab | `gitlab.com` or `REPO_PROVIDER=gitlab` | capability report, local git | local commit\u002Fpush only |\n| Gitea | `REPO_PROVIDER=gitea` | capability report, local git | local commit\u002Fpush only |\n| Forgejo \u002F Codeberg | `codeberg.org` or `REPO_PROVIDER=forgejo` | capability report, local git | local commit\u002Fpush only |\n| Bitbucket Cloud | `bitbucket.org` remotes | capability report, local git | local commit\u002Fpush only |\n| Azure DevOps | `dev.azure.com` or `visualstudio.com` remotes | capability report, local git | local commit\u002Fpush only |\n| SourceHut | `git.sr.ht` remotes | capability report, local git | local commit\u002Fpush only |\n\nUnsupported provider actions must return structured evidence instead\nof pretending the work is complete. Agents should still commit and push\nlocal changes through git when the repository policy allows it.\n\n### MCP tools\n\n| Tool | Purpose |\n|---|---|\n| `detect_repo_provider(project_root, remote)` | Detect remote host, owner\u002Frepo, provider, and local CLI availability. |\n| `inspect_repo_state(project_root, include_remote)` | Inspect branch, dirty state, upstream, ahead\u002Fbehind, remotes, and provider capabilities. |\n| `list_repo_issues(state, limit)` | List open issues when the provider adapter supports it. |\n| `list_repo_change_requests(state, limit)` | List open PRs\u002FMRs\u002Fchange requests when supported. |\n| `plan_repo_reconcile(scope, dry_run)` | Produce the action plan and blockers without mutating. |\n| `resolve_repo_issue(id, resolution, comment, close, confirmation)` | Comment and optionally close a supported issue. |\n| `merge_change_request(id, method, auto_queue, confirmation)` | Merge or queue a supported ready change request. |\n| `commit_local_changes(paths, message, checks)` | Run optional checks, stage paths, and commit local changes. |\n| `push_current_branch(remote, branch)` | Push the current branch to its remote. |\n| `run_repo_reconcile(dry_run, max_items, commit_message, push)` | Apply the guarded batch workflow. |\n\n## Gotchas\n\n- **Do not close issues without evidence.** A close action needs a\n  linked merged change, a duplicate reference, a clear no-repro\n  disposition, or explicit user instruction.\n- **Do not merge drafts or WIP change requests.** Draft state is a hard\n  blocker even if checks are green.\n- **Do not bypass branch protection.** Never force-push, override\n  required reviews, skip required checks, or bypass merge queues.\n- **Do not assume GitHub-only behavior.** Detect the provider first and\n  return unsupported evidence for adapters that are not configured.\n- **Do not treat listing as resolving.** If issues or change requests\n  remain open, report the plan or blocker that remains.\n- **Do not push unrelated local work blindly.** Inspect `git status`\n  and commit only the intended paths or the current complete worktree\n  when the user asked for all local changes.\n- **Do not run mutating batch actions without a dry-run plan.**\n  `run_repo_reconcile(dry_run=false)` should report the plan it applied\n  and every command result.\n- **Do not hide external auth failures.** Missing `gh`, `glab`, `tea`,\n  `bb`, `az`, or `hut` authentication is an actionable blocker, not a\n  successful no-op.\n- **Do not assume a reused gateway sees newly exported credentials.** A\n  long-lived daemon cannot inherit later shell environment changes. Configure\n  an owner-only token file for refreshable GitHub CLI authentication.\n\n## Full reference\n\n### Safety policy\n\nThe skill is deliberately conservative:\n\n- No force pushes.\n- No direct API bypass of provider protection rules.\n- No draft\u002FWIP merge.\n- No issue close without a comment or explicit resolution evidence.\n- Mutating issue and merge tools require exact confirmation tokens:\n  `close-issue:\u003Cid>` and `merge-change-request:\u003Cid>`.\n- Provider-specific actions are serialized by the caller; batch tools\n  return per-action evidence.\n\n### Scope names\n\n`plan_repo_reconcile()` and `\u002Fpk-repo-reconcile` accept these scopes:\n\n| Scope | Includes |\n|---|---|\n| `all` | local, push, issues, and change requests |\n| `local` | dirty state and commit readiness |\n| `push` | ahead\u002Fbehind and push readiness |\n| `issues` | open issue listing and resolution candidates |\n| `prs` | open pull requests, merge requests, or provider change requests |\n| `change-requests` | Alias for `prs` |\n\n### Provider notes\n\nGitHub is the first fully mutating adapter because the `gh` CLI is\ncommon in aibox environments and enforces provider-side checks. GitLab,\nGitea, Forgejo\u002FCodeberg, Bitbucket Cloud, Azure DevOps, and SourceHut\nare first-class provider identities in the schema and detection layer;\ntheir remote issue and change-request mutation paths return\n`unsupported` until the matching local CLI or API credential contract is\nimplemented.\n\n### Long-lived gateway GitHub authentication\n\nThe gateway daemon and direct stdio servers continue to support normal `gh`\nauthentication through `GH_TOKEN`, `GITHUB_TOKEN`, `GH_ENTERPRISE_TOKEN`,\n`GITHUB_ENTERPRISE_TOKEN`, and the GitHub CLI config or keyring.\n\nFor a long-lived daemon that must observe token rotation without a restart,\nset `PROCESSKIT_GITHUB_TOKEN_FILE` to a regular file owned by the gateway user\nwith mode `0600`. The file must contain only the token. GitHub Enterprise may\nuse `PROCESSKIT_GITHUB_ENTERPRISE_TOKEN_FILE` instead. The file is read\nimmediately before every `gh` call and injected only into that child process.\nDirect token environment variables take precedence.\n\nToken values are never added to MCP arguments, command results, diagnostics,\nthe gateway catalog, or tracked MCP configuration. A shared daemon has one\nGitHub identity; use isolated daemons when clients require separate identities.\n",{"name":5,"metadata":49,"description":75},{"processkit":50},{"id":51,"layer":6,"created":52,"version":53,"category":54,"commands":55,"provides":60,"apiVersion":74},"SKILL-repo-management",1778803200000,"1.0.0","devops",[56],{"args":57,"name":58,"description":59},"scope (optional: all, issues, prs, local, push)","pk-repo-reconcile","Plan and apply guarded repository reconciliation across issues, change requests, local commits, and pushes.",{"assets":61,"mcp_tools":62,"primitives":73},[],[63,64,65,66,67,68,69,70,71,72],"detect_repo_provider","inspect_repo_state","list_repo_issues","list_repo_change_requests","plan_repo_reconcile","resolve_repo_issue","merge_change_request","commit_local_changes","push_current_branch","run_repo_reconcile",[],"processkit.projectious.work\u002Fv2","Reconcile repository issues, pull requests, merge requests, local git state, commits, and pushes across GitHub, GitLab, Gitea, Forgejo, Codeberg, Bitbucket, Azure DevOps, and SourceHut.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-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":84,"prompt":94,"zipAvailable":95},[85,88,91],{"tool":86,"command":87},"npx","npx skills add projectious-work\u002Fprocesskit --skill repo-management",{"tool":89,"command":90},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill repo-management",{"tool":92,"command":93},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill repo-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002FSKILL.md",true,[97,103,107,111,117],{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"commands\u002Fpk-repo-reconcile.md","REFERENCE","参考文档",285,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002Fcommands\u002Fpk-repo-reconcile.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"mcp\u002Fmcp-config.json",209,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002Fmcp\u002Fmcp-config.json",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"mcp\u002FSERVER.md",1922,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002Fmcp\u002FSERVER.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"mcp\u002Fserver.py","SCRIPT","脚本",28866,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002Fmcp\u002Fserver.py",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Ftest_repo_management.py",6978,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Frepo-management\u002Fscripts\u002Ftest_repo_management.py",[122,129,136,142,164,184],{"skillNo":123,"name":124,"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":125,"categories":126,"keywords":127,"publishedAt":128},"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":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":128},"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":137,"name":138,"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":139,"categories":140,"keywords":141,"publishedAt":128},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":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",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,150,151,152,153,154,35,155,156,157,158,159,144,160,161,162,163],"skill management","ontology","v1","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":171,"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",[170],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,25,174,175,176,177,178,179,180,181,182,35,156,157,159,183],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"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",[],[191,25,192,193,153,194,195,196,35,156,197,198,158,199,159,200,201,202,203,204],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]