instrument
Skill0 starsChanged 3 months agoMITView on GitHub
Add an explicitly approved ClickTrail event or integration using a metadata allowlist and consent-aware lifecycle. Use when the user asks to instrument a page, conversion, sale, form, or application event.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- ADWilkinson/astacktheir own version, first seen Nov 8, 2026
- Alfred-Lau/skillstheir own version, first seen Oct 20, 2026
- tessaryai/tessarytheir own version, first seen Sep 10, 2026
- monoscope-tech/skillstheir own version, first seen Jun 11, 2026
- vanities/skillstheir own version, first seen Jun 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- tessaryai/tessary★ 20same name
- monoscope-tech/skills★ 4same name
- Alfred-Lau/skills★ 1same name
- ADWilkinson/astack★ 0same name
- vanities/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- auditSkill
- click-tracking-auditSkill
- setupSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Do not begin when the event name, field allowlist, consent contract, or target files are unknown.
- Very specific: line 12
Read project instructions, existing tracking code, and ../../references/clicktrail-safety-contract.md.
- Distinctive: line 20
Keep attribution informational.
- Distinctive: line 22
Add behavior tests proving denial produces no persistence/delivery and withdrawal clears owned state and queues.
- Distinctive: line 24
Run the host project's tests, typecheck, lint, and build.
- Distinctive: line 27
Stop on the first unexpected mutation or live network request.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Instrument an approved event
Do not begin when the event name, field allowlist, consent contract, or target files are unknown.
- Read project instructions, existing tracking code, and
../../references/clicktrail-safety-contract.md. - State the exact files, event name, fields, consent condition, and test changes.
- Get approval for that mutation set.
- Reuse the host's ClickTrail client and event taxonomy. Do not add a second client, direct vendor SDK, or hardcoded analytics call.
- Build the payload from an explicit allowlist. Never pass form objects, request
objects, cookies, user profiles, arbitrary
data, or spread caller input. - Keep attribution informational. Trusted context must control tenant and site routing.
- Add behavior tests proving denial produces no persistence/delivery and withdrawal clears owned state and queues.
- Run the host project's tests, typecheck, lint, and build. Report any skipped check and why.
Stop on the first unexpected mutation or live network request.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.