BC heatmap-analyze
Ptengine Heatmap end-to-end analysis skill. Fetches real heatmap data via the user-installed `ptengine-cli` tool and runs AI-powered CRO behavior analysis using a 4-stage psychology model. REQUIREMENTS (skill does not install or provide these itself): - External tool: `ptengine-cli` — user must install from https://github.com/Kocoro-lab/ptengine-cli - Credentials: a Ptengine API key, configured by the user via `ptengine-cli config set` (stored at `~/.config/ptengine-cli/config.yaml`) or `PTENGINE_API_KEY` env var. The skill never reads, writes, or transmits the key itself — all credential handling is performed by `ptengine-cli`. - Config file read: `~/.config/ptengine-cli/config.yaml` is checked only for existence/`api_key:` presence, to decide whether configuration is needed. Its contents are not parsed or exfiltrated. Use this skill when the user wants to: analyze a webpage's heatmap data, understand user behavior on a page, compare audience segments, validate A/B test results, evaluate ad channel performance, analyze audience characteristics, find conversion barriers or opportunities, or optimize a landing page. Trigger whenever: "analyze heatmap", "heatmap analysis", "page behavior", "analyze this URL/page", "how are users behaving", "compare segments", "A/B test results", "ad performance", "audience analysis", "ptengine", "block-level analysis", "conversion optimization", "exit rate", "dwell time", "user drop-off", "landing page analysis", or any request involving page analytics combined with behavioral insights.
As a process C 60/100 · Has gaps — weak spots: result and completion, consistency, running it twice
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Dangerous commands
cmd-pipe-to-shellSKILL.md:44Downloads and executes remote code from an unrecognised host (pipe to shell) (negated — the text forbids it)- Does not install `ptengine-cli` for the user (no bundled installer, no `curl | sh`)
negated
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1551 chars, limit 1024 - note
description-budgetdescription takes 1551 of the ~15000-char shared budget for all skills
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (heatmap-analyze) differs from the folder (ptengine-heatmap-analyze)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 35 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 3214 tokens
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1550: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 16 example trigger phrases
- +4Structure: 22 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.