[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPP7ZNVCQJTN93QVY611V7":3,"skill-same:01M6NPP7ZNVCQJTN93QVY611V7":94},{"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":62,"commitSha":63,"skillDirectory":64,"forksCount":14,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6NPP7ZNVCQJTN93QVY611V7","metrics-management",null,"Manage metric specifications and observations: quantified measures the\nproject cares about (velocity, error rates, lead time, NPS). Use when\ndefining or recording a quantitative measure: team velocity, error rate,\nlead time, customer satisfaction score.","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\u002Fmetrics-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"metrics","metrics management","management","artifact","customer","observations","recording","event","error","keep","project","time","team","velocity","manage","log","devops","use","audit","work","2026-11-10 10:12:30",false,"---\nname: metrics-management\ndescription: |\n  Manage metric specifications and observations: quantified measures the\n  project cares about (velocity, error rates, lead time, NPS). Use when\n  defining or recording a quantitative measure: team velocity, error rate,\n  lead time, customer satisfaction score.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-metrics-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: devops\n    layer: 4\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n    provides:\n      primitives: [Artifact, LogEntry]\n      templates: [metric-spec]\n---\n\n# Metrics Management\n\n## Intro\n\nA metric specification is an Artifact with `kind: metric-spec` that names a\nquantified measure the project cares about. Examples: team velocity per\nsprint, p99 latency, release frequency, error rate, customer NPS.\n\n## Overview\n\n### Metric spec vs observation\n\nA metric-spec Artifact defines *what is measured*. Individual readings are\nLogEntries (`event_type: metric.recorded`) or external time-series data.\nprocesskit stores the definition, not the time series.\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Artifact\nmetadata:\n  id: ART-velocity-metric-spec\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: velocity\n  kind: metric-spec\n  description: \"Story points completed per sprint.\"\n  unit: points\n  direction: higher-is-better\n  measurement: >\n    Sum of spec.estimate.value for WorkItems with spec.state=done in the\n    sprint's SCOPE.\n  target: 40\n  tolerance: \"±20%\"\n  cadence: sprint\n  owner: ACTOR-tech-lead\n---\n```\n\n### Recording observations\n\nIndividual measurements are LogEntries:\n\n```yaml\nkind: LogEntry\nspec:\n  event_type: metric.recorded\n  timestamp: 2026-04-14T17:00:00Z\n  actor: ACTOR-claude\n  subject: ART-velocity-metric-spec\n  subject_kind: Artifact\n  summary: \"Sprint 42 velocity: 38 points\"\n  details:\n    value: 38\n    scope: SCOPE-sprint-42\n```\n\nThe index MCP server joins metric-spec Artifacts with their LogEntry\nobservations to produce time series.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Defining a metric spec without a measurement source.** \"We want to\n  improve velocity\" is not a metric spec; \"Story points completed per\n  sprint, measured from `query_workitems(state=done, scope=sprint-N)`\"\n  is. Without a source, the metric can't be measured and becomes\n  decoration.\n- **Setting target values without a baseline.** \"Reduce error rate\n  by 50%\" is meaningless if you don't know the current rate.\n  Always record the baseline when the metric spec is created, and update\n  it explicitly when you reset goals.\n- **Confusing leading vs lagging indicators.** A leading indicator\n  predicts future outcomes (PR review turnaround time); a lagging\n  indicator measures past outcomes (incidents per quarter). Don't\n  optimize a lagging indicator if a leading one is available —\n  feedback loops are slower.\n- **Metrics without owner or cadence.** \"Who looks at this and how\n  often\" is part of the metric definition, not an afterthought.\n  Unowned metrics rot.\n- **Storing measurement values inline in the metric spec.**\n  Metric-spec artifacts define what is measured, not the measurements\n  themselves. Time-series values belong in an external store\n  (Prometheus, BigQuery, ...); the metric spec references the\n  store, not the data.\n- **Vanity metrics that don't drive decisions.** \"Total LOC\", \"PR\n  count\", \"tickets closed\" sound impressive but don't predict\n  anything actionable. If knowing the number wouldn't change what\n  you do next, it's vanity — drop it.\n- **Hand-waving \"trending up\" without numbers.** When asked about\n  a metric's status, fetch the actual value from the source the\n  metric spec points at; don't synthesize a trend from memory.\n\n## Full reference\n\n### Fields\n\n| Field         | Type     | Notes                                               |\n|---------------|----------|-----------------------------------------------------|\n| `name`        | string   | kebab-case identifier                               |\n| `description` | string   | What this metric measures                           |\n| `unit`        | string   | `points` \u002F `ms` \u002F `%` \u002F `count` \u002F etc.              |\n| `direction`   | enum     | `higher-is-better` \u002F `lower-is-better` \u002F `target`   |\n| `measurement` | string   | How to compute the value                            |\n| `target`      | any      | Desired value (number or string)                    |\n| `tolerance`   | string   | Acceptable deviation from target                    |\n| `cadence`     | string   | How often it's measured                             |\n| `owner`       | string   | Actor ID responsible for the metric                 |\n| `active`      | bool     | `false` = no longer tracked                         |\n\n### Vanity metrics\n\nAvoid metrics that always trend up just by activity (commits per week, lines\nof code) — they reward effort, not outcome. Favor metrics that can get\nworse when the project is unhealthy: lead time, defect rate, customer\nsatisfaction, mean-time-to-recovery.\n\n### Metrics vs goals\n\nA goal is a desired future state recorded in a Scope's `spec.goals`. A metric\nspec is the quantitative thing the goal is measured by. One goal may reference\nmultiple metric specs; one metric spec may inform multiple goals.\n","# Metrics Management\n\n## Intro\n\nA metric specification is an Artifact with `kind: metric-spec` that names a\nquantified measure the project cares about. Examples: team velocity per\nsprint, p99 latency, release frequency, error rate, customer NPS.\n\n## Overview\n\n### Metric spec vs observation\n\nA metric-spec Artifact defines *what is measured*. Individual readings are\nLogEntries (`event_type: metric.recorded`) or external time-series data.\nprocesskit stores the definition, not the time series.\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Artifact\nmetadata:\n  id: ART-velocity-metric-spec\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: velocity\n  kind: metric-spec\n  description: \"Story points completed per sprint.\"\n  unit: points\n  direction: higher-is-better\n  measurement: >\n    Sum of spec.estimate.value for WorkItems with spec.state=done in the\n    sprint's SCOPE.\n  target: 40\n  tolerance: \"±20%\"\n  cadence: sprint\n  owner: ACTOR-tech-lead\n---\n```\n\n### Recording observations\n\nIndividual measurements are LogEntries:\n\n```yaml\nkind: LogEntry\nspec:\n  event_type: metric.recorded\n  timestamp: 2026-04-14T17:00:00Z\n  actor: ACTOR-claude\n  subject: ART-velocity-metric-spec\n  subject_kind: Artifact\n  summary: \"Sprint 42 velocity: 38 points\"\n  details:\n    value: 38\n    scope: SCOPE-sprint-42\n```\n\nThe index MCP server joins metric-spec Artifacts with their LogEntry\nobservations to produce time series.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Defining a metric spec without a measurement source.** \"We want to\n  improve velocity\" is not a metric spec; \"Story points completed per\n  sprint, measured from `query_workitems(state=done, scope=sprint-N)`\"\n  is. Without a source, the metric can't be measured and becomes\n  decoration.\n- **Setting target values without a baseline.** \"Reduce error rate\n  by 50%\" is meaningless if you don't know the current rate.\n  Always record the baseline when the metric spec is created, and update\n  it explicitly when you reset goals.\n- **Confusing leading vs lagging indicators.** A leading indicator\n  predicts future outcomes (PR review turnaround time); a lagging\n  indicator measures past outcomes (incidents per quarter). Don't\n  optimize a lagging indicator if a leading one is available —\n  feedback loops are slower.\n- **Metrics without owner or cadence.** \"Who looks at this and how\n  often\" is part of the metric definition, not an afterthought.\n  Unowned metrics rot.\n- **Storing measurement values inline in the metric spec.**\n  Metric-spec artifacts define what is measured, not the measurements\n  themselves. Time-series values belong in an external store\n  (Prometheus, BigQuery, ...); the metric spec references the\n  store, not the data.\n- **Vanity metrics that don't drive decisions.** \"Total LOC\", \"PR\n  count\", \"tickets closed\" sound impressive but don't predict\n  anything actionable. If knowing the number wouldn't change what\n  you do next, it's vanity — drop it.\n- **Hand-waving \"trending up\" without numbers.** When asked about\n  a metric's status, fetch the actual value from the source the\n  metric spec points at; don't synthesize a trend from memory.\n\n## Full reference\n\n### Fields\n\n| Field         | Type     | Notes                                               |\n|---------------|----------|-----------------------------------------------------|\n| `name`        | string   | kebab-case identifier                               |\n| `description` | string   | What this metric measures                           |\n| `unit`        | string   | `points` \u002F `ms` \u002F `%` \u002F `count` \u002F etc.              |\n| `direction`   | enum     | `higher-is-better` \u002F `lower-is-better` \u002F `target`   |\n| `measurement` | string   | How to compute the value                            |\n| `target`      | any      | Desired value (number or string)                    |\n| `tolerance`   | string   | Acceptable deviation from target                    |\n| `cadence`     | string   | How often it's measured                             |\n| `owner`       | string   | Actor ID responsible for the metric                 |\n| `active`      | bool     | `false` = no longer tracked                         |\n\n### Vanity metrics\n\nAvoid metrics that always trend up just by activity (commits per week, lines\nof code) — they reward effort, not outcome. Favor metrics that can get\nworse when the project is unhealthy: lead time, defect rate, customer\nsatisfaction, mean-time-to-recovery.\n\n### Metrics vs goals\n\nA goal is a desired future state recorded in a Scope's `spec.goals`. A metric\nspec is the quantitative thing the goal is measured by. One goal may reference\nmultiple metric specs; one metric spec may inform multiple goals.\n",{"name":5,"metadata":44,"description":61},{"processkit":45},{"id":46,"uses":47,"layer":51,"created":52,"version":53,"category":35,"provides":54,"apiVersion":60},"SKILL-metrics-management",[48],{"skill":49,"purpose":50},"event-log","Log events to keep the audit trail accurate after every write.",4,1775433600000,"1.0.0",{"templates":55,"primitives":57},[56],"metric-spec",[58,59],"Artifact","LogEntry","processkit.projectious.work\u002Fv2","Manage metric specifications and observations: quantified measures the\nproject cares about (velocity, error rates, lead time, NPS). Use when\ndefining or recording a quantitative measure: team velocity, error rate,\nlead time, customer satisfaction score.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fdevops\u002Fmetrics-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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add projectious-work\u002Fprocesskit --skill metrics-management",{"tool":75,"command":76},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill metrics-management",{"tool":78,"command":79},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill metrics-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fmetrics-management\u002FSKILL.md",true,[83,89],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Fmetric-spec.yaml","ASSET","资产文件",307,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fmetrics-management\u002Fassets\u002Fmetric-spec.yaml",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":14,"sourceHtmlUrl":93},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fmetrics-management\u002Fscripts\u002F.gitkeep",[95,102,109,115,140,160],{"skillNo":96,"name":97,"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":98,"categories":99,"keywords":100,"publishedAt":101},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":101},"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":110,"name":111,"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":112,"categories":113,"keywords":114,"publishedAt":101},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":126,"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",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[21,127,128,129,130,131,38,132,133,33,134,135,117,136,137,138,139],"skill management","ontology","v1","create","as","transition","get","update","alpha","list","package","skill package","manifests",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"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",[146],{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},[148,149,21,150,151,152,153,154,155,156,157,158,38,133,33,135,159],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"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",[],[167,21,168,169,130,170,171,172,38,133,173,26,134,174,135,175,176,177,178,34],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","query","facts"]