{
  "schemaVersion": "1.0",
  "item": {
    "slug": "metrics",
    "name": "Metrics",
    "source": "tencent",
    "type": "skill",
    "category": "数据分析",
    "sourceUrl": "https://clawhub.ai/ivangdavila/metrics",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/metrics",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/metrics",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=metrics",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "automation-patterns.md",
      "data-quality.md",
      "formula-playbook.md",
      "memory-template.md",
      "metric-registry.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/metrics"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/metrics",
    "agentPageUrl": "https://openagent3.xyz/skills/metrics/agent",
    "manifestUrl": "https://openagent3.xyz/skills/metrics/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/metrics/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Setup",
        "body": "On first use, read setup.md for integration behavior and memory initialization."
      },
      {
        "title": "When to Use",
        "body": "Use this skill when the user needs to define, track, analyze, or report metrics for any domain such as social media, sales, product, operations, finance, or personal systems.\n\nThis skill structures metric definitions, computes reliable formulas, builds reusable report packs, and maintains scalable automation rules that can grow with the user over time."
      },
      {
        "title": "Architecture",
        "body": "Working memory lives in ~/metrics/. See memory-template.md for base structure and status behavior.\n\n~/metrics/\n├── memory.md              # HOT: goals, active metrics, reporting cadence\n├── registry/              # WARM: metric contracts and dimension dictionaries\n├── formulas/              # WARM: formula specs with version history\n├── reports/               # WARM: report outputs by cadence and stakeholder\n├── automations/           # WARM: scheduled checks and alert policies\n└── archive/               # COLD: retired metrics and old report cycles"
      },
      {
        "title": "Quick Reference",
        "body": "Load only the file needed for the current task to keep context focused.\n\nTopicFileSetup and integrationsetup.mdMemory schemamemory-template.mdMetric contract designmetric-registry.mdFormula design and governanceformula-playbook.mdReport cadences and templatesreporting-pack.mdAutomation and alerting patternsautomation-patterns.mdData validation and quality gatesdata-quality.md"
      },
      {
        "title": "1. Define a Metric Contract Before Any Calculation",
        "body": "Every metric must have one clear contract: business meaning, numerator, denominator, source tables, update latency, and owner.\n\nNever compute or compare metrics when the contract is missing or ambiguous."
      },
      {
        "title": "2. Separate Raw Signals from Derived Metrics",
        "body": "Raw events are evidence. Metrics are interpreted aggregates. Keep them separate.\n\nStore and reason in this order:\n\nRaw signal\nNormalized base metric\nDerived metric\nDecision recommendation"
      },
      {
        "title": "3. Use Dimensions to Scale, Not New One-Off Metrics",
        "body": "When users ask for \"the same metric but by X\", add a dimension instead of creating a duplicate metric.\n\nCommon high-value dimensions:\n\nTime grain\nSource/channel\nSegment/persona\nGeography\nProduct or workflow stage"
      },
      {
        "title": "4. Version Formulas and Annotate Breaking Changes",
        "body": "Formulas evolve. Comparability fails when formula changes are not tracked.\n\nFor every formula update, store:\n\nversion\nchange reason\nimpact expectation\nbackfill policy\nfirst report date with new logic"
      },
      {
        "title": "5. Reports Must Be Decision-Oriented",
        "body": "A report is incomplete unless each section ties to a decision owner and explicit next action.\n\nMinimum output block for every report:\n\nWhat changed\nWhy it changed\nWhat to do now\nWho owns the action\nWhen to review again"
      },
      {
        "title": "6. Automate Thresholds with Response Playbooks",
        "body": "Alerts without response rules create noise.\n\nEach threshold must include:\n\ntrigger condition\nseverity level\nowner\nfirst response action\nescalation condition"
      },
      {
        "title": "7. Prefer Reusable Reporting Packs Over Custom One-Offs",
        "body": "Build reusable templates for daily, weekly, monthly, and campaign reports so the system can scale across teams and domains.\n\nOnly create custom formats when a stakeholder decision cannot be served by existing packs."
      },
      {
        "title": "Common Traps",
        "body": "Mixing different metric definitions under one name -> trend lines become invalid.\nChanging formulas without version notes -> historical comparisons break silently.\nReporting totals without segment cuts -> root causes remain hidden.\nCreating too many vanity metrics -> operators lose focus on decision metrics.\nSending alerts without action ownership -> teams ignore notifications.\nAdding one-off dashboards for every request -> reporting system becomes unmaintainable."
      },
      {
        "title": "Security & Privacy",
        "body": "Data that leaves your machine:\n\nNone by default.\n\nData that stays local:\n\nMetrics context and definitions under ~/metrics/.\nFormula versions, report logs, and alert policies stored locally.\n\nThis skill does NOT:\n\nAccess files outside ~/metrics/ for memory storage.\nSend metrics to third-party APIs by default.\nCreate background automations without explicit user confirmation."
      },
      {
        "title": "Related Skills",
        "body": "Install with clawhub install <slug> if user confirms:\n\nanalytics — metric analysis patterns and interpretation workflows.\ndashboard — KPI visualization design and reporting layouts.\nreport — structured reporting outputs for stakeholders.\nsql — query generation for metric extraction pipelines.\nexcel-xlsx — spreadsheet-based metric operations and exports."
      },
      {
        "title": "Feedback",
        "body": "If useful: clawhub star metrics\nStay updated: clawhub sync"
      }
    ],
    "body": "Setup\n\nOn first use, read setup.md for integration behavior and memory initialization.\n\nWhen to Use\n\nUse this skill when the user needs to define, track, analyze, or report metrics for any domain such as social media, sales, product, operations, finance, or personal systems.\n\nThis skill structures metric definitions, computes reliable formulas, builds reusable report packs, and maintains scalable automation rules that can grow with the user over time.\n\nArchitecture\n\nWorking memory lives in ~/metrics/. See memory-template.md for base structure and status behavior.\n\n~/metrics/\n├── memory.md              # HOT: goals, active metrics, reporting cadence\n├── registry/              # WARM: metric contracts and dimension dictionaries\n├── formulas/              # WARM: formula specs with version history\n├── reports/               # WARM: report outputs by cadence and stakeholder\n├── automations/           # WARM: scheduled checks and alert policies\n└── archive/               # COLD: retired metrics and old report cycles\n\nQuick Reference\n\nLoad only the file needed for the current task to keep context focused.\n\nTopic\tFile\nSetup and integration\tsetup.md\nMemory schema\tmemory-template.md\nMetric contract design\tmetric-registry.md\nFormula design and governance\tformula-playbook.md\nReport cadences and templates\treporting-pack.md\nAutomation and alerting patterns\tautomation-patterns.md\nData validation and quality gates\tdata-quality.md\nCore Rules\n1. Define a Metric Contract Before Any Calculation\n\nEvery metric must have one clear contract: business meaning, numerator, denominator, source tables, update latency, and owner.\n\nNever compute or compare metrics when the contract is missing or ambiguous.\n\n2. Separate Raw Signals from Derived Metrics\n\nRaw events are evidence. Metrics are interpreted aggregates. Keep them separate.\n\nStore and reason in this order:\n\nRaw signal\nNormalized base metric\nDerived metric\nDecision recommendation\n3. Use Dimensions to Scale, Not New One-Off Metrics\n\nWhen users ask for \"the same metric but by X\", add a dimension instead of creating a duplicate metric.\n\nCommon high-value dimensions:\n\nTime grain\nSource/channel\nSegment/persona\nGeography\nProduct or workflow stage\n4. Version Formulas and Annotate Breaking Changes\n\nFormulas evolve. Comparability fails when formula changes are not tracked.\n\nFor every formula update, store:\n\nversion\nchange reason\nimpact expectation\nbackfill policy\nfirst report date with new logic\n5. Reports Must Be Decision-Oriented\n\nA report is incomplete unless each section ties to a decision owner and explicit next action.\n\nMinimum output block for every report:\n\nWhat changed\nWhy it changed\nWhat to do now\nWho owns the action\nWhen to review again\n6. Automate Thresholds with Response Playbooks\n\nAlerts without response rules create noise.\n\nEach threshold must include:\n\ntrigger condition\nseverity level\nowner\nfirst response action\nescalation condition\n7. Prefer Reusable Reporting Packs Over Custom One-Offs\n\nBuild reusable templates for daily, weekly, monthly, and campaign reports so the system can scale across teams and domains.\n\nOnly create custom formats when a stakeholder decision cannot be served by existing packs.\n\nCommon Traps\nMixing different metric definitions under one name -> trend lines become invalid.\nChanging formulas without version notes -> historical comparisons break silently.\nReporting totals without segment cuts -> root causes remain hidden.\nCreating too many vanity metrics -> operators lose focus on decision metrics.\nSending alerts without action ownership -> teams ignore notifications.\nAdding one-off dashboards for every request -> reporting system becomes unmaintainable.\nSecurity & Privacy\n\nData that leaves your machine:\n\nNone by default.\n\nData that stays local:\n\nMetrics context and definitions under ~/metrics/.\nFormula versions, report logs, and alert policies stored locally.\n\nThis skill does NOT:\n\nAccess files outside ~/metrics/ for memory storage.\nSend metrics to third-party APIs by default.\nCreate background automations without explicit user confirmation.\nRelated Skills\n\nInstall with clawhub install <slug> if user confirms:\n\nanalytics — metric analysis patterns and interpretation workflows.\ndashboard — KPI visualization design and reporting layouts.\nreport — structured reporting outputs for stakeholders.\nsql — query generation for metric extraction pipelines.\nexcel-xlsx — spreadsheet-based metric operations and exports.\nFeedback\nIf useful: clawhub star metrics\nStay updated: clawhub sync"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/metrics",
    "publisherUrl": "https://clawhub.ai/ivangdavila/metrics",
    "owner": "ivangdavila",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/metrics",
    "downloadUrl": "https://openagent3.xyz/downloads/metrics",
    "agentUrl": "https://openagent3.xyz/skills/metrics/agent",
    "manifestUrl": "https://openagent3.xyz/skills/metrics/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/metrics/agent.md"
  }
}