{
  "name": "pendo-analytics — 6 skills",
  "slug": "source-skills-eb5e15e65ebc11ce04c0b9b9",
  "type": "skills",
  "category": "developer-tools",
  "example": false,
  "evidence_state": "pinned_source_listing",
  "stamp": "Pinned source listing — machine-checked",
  "summary": "Pinned source declarations and file hashes were listed.",
  "outcome": "Listed 6 skill declarations. Ran 13 git commands; each one's exit status and output hash is in commands.json. Scope: acquisition and static inspection.",
  "rule_results": [
    "The retained source tree matches its acquisition manifest.",
    "Declared skill names (listing.json): account-health; app-health; data-informed-planning; feature-adoption; feedback-analysis; replay-triage"
  ],
  "task": "What declarations and files are present in this pinned source?",
  "setup": "Git blob acquisition followed by static source inspection.",
  "limitations": "Scope: acquisition and static inspection. Command results: commands.json.",
  "source_url": "https://github.com/pendo-io/claude-pendo-plugin.git",
  "documentation_url": "https://github.com/pendo-io/claude-pendo-plugin.git",
  "commit": "a0f85260c61b93c4511f59545612323a41c3f845",
  "tree_sha256": "bb3435a291da54b92223d3a1a5d1e2805b9b7f9dbe4e44a6768a8096eff68b12",
  "file_sha256": {
    "plugins/pendo-analytics/.claude-plugin/plugin.json": "d41955c0fd63649ad31eb81323c90028d545fd3f0db4f85705caca41bd79bbb4",
    "plugins/pendo-analytics/skills/account-health/SKILL.md": "3f3fccd7a0c3909b61737078b888642a01e206b889d026bc49ded20c73d4032e",
    "plugins/pendo-analytics/skills/app-health/SKILL.md": "34637b981674eaf0b840e485b1d5f1db894fadb5f3c80fced44583b924fe9e4b",
    "plugins/pendo-analytics/skills/data-informed-planning/SKILL.md": "cac13ce444aa51d9b8822f20492a61f7ba0ac35971cddd5bc8bd894e4d24c7a8",
    "plugins/pendo-analytics/skills/data-informed-planning/classifier.md": "aa925f9532a478cf2df3a6ea9b2853e3ec9b9e9a0804f05f3107c41a05b9e4b1",
    "plugins/pendo-analytics/skills/feature-adoption/SKILL.md": "75a6a65a45c7743a7ede9e5364d04f9cdc8abc61c9363f1bfcbc9c3fcea38af5",
    "plugins/pendo-analytics/skills/feedback-analysis/SKILL.md": "cba01ae1b6667c33fbd8986a9b40db8ad1061e76aae6899765280b32455226d3",
    "plugins/pendo-analytics/skills/replay-triage/SKILL.md": "5f33342d62c353b5ed9cb8b32b26eb460fb58dacc71f8b98e7c21ff3ae587fc6"
  },
  "lockfiles": [
    "LOCK.json"
  ],
  "utc_date": "2026-10-19T09:09:10Z",
  "source_date": "2026-10-16",
  "discovered_date": "2026-10-16",
  "retested_date": "2026-10-19",
  "reviewed_date": "2026-10-19",
  "published_date": "2026-10-19",
  "modified_date": "2026-10-19",
  "reviewer": "machine pipeline",
  "harness_version": "toolwitness harness at commit 69d02e93b32bf6864548627356e41d579498e06d",
  "claude_code_version": "Not applicable: static source inspection (commands.json).",
  "model_id": "Not applicable: static source inspection (commands.json).",
  "scanner_version": "Not applicable: static source inspection.",
  "rulepack_version": "Not applicable: static source inspection.",
  "agents": [],
  "disclaimer": "This record lists declarations and file hashes from a pinned source tree. Git command results from acquisition and static inspection are retained in commands.json. Scope: acquisition and static inspection. It is not a security or quality verdict. Changed bytes are outside this record.",
  "commands": [
    "Ran 13 git commands; each one's exit status and output hash is in commands.json. Scope: acquisition and static inspection."
  ],
  "prompt_list": [
    "Not applicable: static source inspection (commands.json)."
  ],
  "history": [
    "2026-10-19T09:09:10Z: pinned source inspection"
  ],
  "application": {
    "name": "pendo-analytics — 6 skills",
    "softwareVersion": "a0f85260c61b93c4511f59545612323a41c3f845",
    "applicationCategory": "DeveloperApplication",
    "operatingSystem": "Not exercised"
  },
  "artifacts": {
    "transcript": "Ran 13 git commands; each one's exit status and output hash is in commands.json. Scope: acquisition and static inspection.",
    "sinkhole_log": "Not applicable: static source inspection (commands.json).",
    "canary_log": "Not applicable: static source inspection (commands.json).",
    "scanner_output": "Not applicable: static source inspection (commands.json).",
    "normalized_text": "{\n  \"listing\": {\n    \"skills\": [\n      {\n        \"path\": \"plugins/pendo-analytics/skills/account-health/SKILL.md\",\n        \"name\": \"account-health\",\n        \"description\": \"Prepare for a customer call by synthesizing engagement, sentiment, and feedback from Pendo analytics. Use this skill whenever someone asks about account health, wants to prepare for a customer call, needs an account health report, asks about engagement or usage for a specific customer, or wants a summary of how an account is doing. Also trigger when users mention preparing for a QBR, checking on a customer, or reviewing an account before a meeting — even if they don't say \\\"account health\\\" explicitly.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/account-health/SKILL.md\": \"3f3fccd7a0c3909b61737078b888642a01e206b889d026bc49ded20c73d4032e\"\n        }\n      },\n      {\n        \"path\": \"plugins/pendo-analytics/skills/app-health/SKILL.md\",\n        \"name\": \"app-health\",\n        \"description\": \"Generate a shareable health report for one application, summarizing engagement, acquisition, retention, average time, stickiness, frustration signals, and survey scores into a verdict and next steps. Use this skill whenever someone asks how healthy an app is, wants an app health report, wants an overall picture of how an application is doing, or asks about an app's engagement, retention, stickiness, or friction at the application level — even if they don't say \\\"app health\\\" explicitly. This is app-level (a whole application), not account-level — for a single customer account use account-health, and for a single feature use feature-adoption.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/app-health/SKILL.md\": \"34637b981674eaf0b840e485b1d5f1db894fadb5f3c80fced44583b924fe9e4b\"\n        }\n      },\n      {\n        \"path\": \"plugins/pendo-analytics/skills/data-informed-planning/SKILL.md\",\n        \"name\": \"data-informed-planning\",\n        \"description\": \"Use when planning a product feature, fix, or prioritization task where Pendo usage data, signals, issues, or customer feedback could ground the plan in real product behavior — e.g. \\\"plan a fix for the pricing-page dropoff\\\", \\\"what should I build next\\\", \\\"improve the welcome flow\\\". Skip for pure code refactors, infra, or tooling work.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/data-informed-planning/SKILL.md\": \"cac13ce444aa51d9b8822f20492a61f7ba0ac35971cddd5bc8bd894e4d24c7a8\",\n          \"plugins/pendo-analytics/skills/data-informed-planning/classifier.md\": \"aa925f9532a478cf2df3a6ea9b2853e3ec9b9e9a0804f05f3107c41a05b9e4b1\"\n        }\n      },\n      {\n        \"path\": \"plugins/pendo-analytics/skills/feature-adoption/SKILL.md\",\n        \"name\": \"feature-adoption\",\n        \"description\": \"Analyze feature adoption rates, identify power users vs laggards, and track adoption trends using Pendo analytics. Use this skill whenever someone asks about feature adoption, feature usage, who's using a feature, adoption rates, feature rollout progress, or wants to understand how a specific feature is performing. Also trigger when users mention tracking a feature launch, finding champions or power users of a feature, identifying accounts that haven't adopted a feature, comparing adoption across segments, or analyzing usage trends over time — even if they don't say \\\"adoption\\\" explicitly. If someone asks \\\"who's using X\\\" or \\\"how is feature Y doing\\\", this is the right skill.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/feature-adoption/SKILL.md\": \"75a6a65a45c7743a7ede9e5364d04f9cdc8abc61c9363f1bfcbc9c3fcea38af5\"\n        }\n      },\n      {\n        \"path\": \"plugins/pendo-analytics/skills/feedback-analysis/SKILL.md\",\n        \"name\": \"feedback-analysis\",\n        \"description\": \"Analyze customer feedback using Pendo's feedback tools — cluster themes, extract insights, and surface churn/frustration risks. Use whenever the user asks about feedback trends, top complaints, feature requests, Voice of the Customer, churn risks, or what customers are saying about a topic or account. Triggers on phrases like \\\"feedback report\\\", \\\"what are customers asking for\\\", \\\"any red flags in sentiment\\\", or \\\"what's the feedback looking like\\\". Requires Pendo connector.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/feedback-analysis/SKILL.md\": \"cba01ae1b6667c33fbd8986a9b40db8ad1061e76aae6899765280b32455226d3\"\n        }\n      },\n      {\n        \"path\": \"plugins/pendo-analytics/skills/replay-triage/SKILL.md\",\n        \"name\": \"replay-triage\",\n        \"description\": \"Triage issues captured in a Pendo session replay by fetching devlogs, mapping errors to the local codebase, proposing fixes, and prompting for a pull request. Accepts either a replay URL directly or a ticket reference (e.g. Jira key or URL, GitHub issue URL, etc.) and will pull the replay link from the ticket. Use whenever someone hands off a user-reported bug — via a replay link or a ticket that contains one — and asks to investigate, diagnose, debug, triage, or fix it. Requires Pendo connector; uses whatever ticketing MCP or CLI is available (Atlassian, `gh`, etc.) when a ticket is supplied.\",\n        \"files\": {\n          \"plugins/pendo-analytics/skills/replay-triage/SKILL.md\": \"5f33342d62c353b5ed9cb8b32b26eb460fb58dacc71f8b98e7c21ff3ae587fc6\"\n        }\n      }\n    ],\n    \"hooks\": [],\n    \"executions\": []\n  }\n}"
  },
  "review_input": {
    "identity_artifact": "identity.json",
    "evidence_sha256": {
      "LOCK.json": "6a5874cb732ff045813d637c5266893ebd57f8ce91a4394a96217ddb5f999c59",
      "commands.json": "6256354911a92ce9879ba7b0b32a4006c5ef3286fda64e8263f5bad9005f898e",
      "complete.json": "91b504b43905fdc009504d516c45eea831f39a1995b9e7d69987c9756c936d6f",
      "identity.json": "f69a0ea29f14c3b3d446577ef77bafa6bfaf52b0c09b73ea2ef13bee3bfd0cb0",
      "listing.json": "e9a38324adbb00f488d85db769a9f06d1abb81bb1f6cbf288e9424f9928f525e",
      "selection.json": "0ee6cf5e2f4ac80ffc4bfc9e72e290a9fb8ed9071f6f87aa9ccbfb1f0280b786"
    },
    "claims": [
      {
        "id": "acquired",
        "field": "summary",
        "text": "Pinned source declarations and file hashes were listed.",
        "sources": [
          "LOCK.json",
          "listing.json",
          "commands.json"
        ]
      },
      {
        "id": "listed",
        "field": "outcome",
        "text": "Listed 6 skill declarations. Ran 13 git commands; each one's exit status and output hash is in commands.json. Scope: acquisition and static inspection.",
        "sources": [
          "LOCK.json",
          "listing.json",
          "commands.json"
        ]
      },
      {
        "id": "tree",
        "field": "rule_results.0",
        "text": "The retained source tree matches its acquisition manifest.",
        "sources": [
          "LOCK.json",
          "listing.json",
          "commands.json"
        ]
      },
      {
        "id": "declared",
        "field": "rule_results.1",
        "text": "Declared skill names (listing.json): account-health; app-health; data-informed-planning; feature-adoption; feedback-analysis; replay-triage",
        "sources": [
          "LOCK.json",
          "listing.json",
          "commands.json"
        ]
      }
    ]
  },
  "review": {
    "kind": "machine-checked",
    "date": "2026-10-19",
    "reviewed_sha256": "d970fd6c9754be2ed634cc360abd894f5f53ac4af82ce1cc77fcc117feae3d86",
    "gates": "4c206e3d6df9beba5f0fb901261975489ea9adaa8cbc79135bf4a0a54a1d40b5",
    "codex": "0b9cfe249aef991af37d7393d30d57ae611e66746f0d31aa4272a70b9a546b80",
    "grok": "23115dd5cccbc678aa0e1f19f5a29c2b0939d47ce3104704354afad94eb720a0",
    "summary": "Deterministic gates passed; every claim rebuilt from evidence with a reviewed template; Grok reported no standing refutation."
  }
}