agentleFS
Sign inStart free
vizuhvizuh/clicktrail-claude-plugin/skills/audit/SKILL.md

audit

Skill0 starsChanged 3 months agoMITView on GitHub

Audit an existing ClickTrail or attribution implementation for consent, PII, unsafe destinations, tenant spoofing, trust-boundary errors, and missing tests. Use for tracking reviews, privacy checks, or pre-release audits.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 32 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read project instructions, tracking docs, manifests, and the integration entry points.

    line 10
  2. Distinctive:

    Check that trusted host configuration wins over caller-controlled attribution.

    line 15
  3. Distinctive:

    Check server destinations for public credential-free HTTPS enforcement.

    line 16
  4. Distinctive:

    Check payloads against a concrete allowlist.

    line 17
  5. Distinctive:

    Check tests for observable consent-denial, withdrawal-erasure, redaction, SSRF, delivery-failure, and tenant-collision behavior.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 176 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit ClickTrail

Remain read-only. Do not install packages, edit files, or call live endpoints.

  1. Read project instructions, tracking docs, manifests, and the integration entry points.
  2. Read ../../references/clicktrail-safety-contract.md.
  3. Trace startup, capture, persistence, delivery, withdrawal, stop, and retry paths. Inspect every caller of shared constructors or serializers.
  4. Check that trusted host configuration wins over caller-controlled attribution.
  5. Check server destinations for public credential-free HTTPS enforcement.
  6. Check payloads against a concrete allowlist. Treat arbitrary objects and raw passthrough as findings even when current callers appear safe.
  7. Check tests for observable consent-denial, withdrawal-erasure, redaction, SSRF, delivery-failure, and tenant-collision behavior.

Report findings as Critical, Important, or Minor. Each finding must name the file, behavior, impact, and smallest safe correction. End with verified passes and unresolved evidence. Do not turn missing evidence into a pass.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free