Adtech / Analytics Engineering

Advertising Signal Ownership Auditor

Audit collection, control, visibility, retention, and use of advertising signals from exposure through verified business outcome.

DocumentationAgent instructionsRequirements & limits

Use before campaign activation or measurement redesign to determine who owns and can verify each signal.

Inputs

The released example shows these fields. Check the guide for which are required.

  • systems
  • events
  • objective

Outputs

  • Signal ownership ledger
  • Measurement gaps
  • Independent evidence plan

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • May audit and recommend; privacy, consent, retention, and platform configuration changes require responsible human approval.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Advertising Signal Ownership Auditor

When to use

Use this skill for the situations described in its frontmatter routing description.

Workflow

  1. Inventory every event from exposure through post-purchase outcome.
  2. Identify the collector, controller, processor, visible parties, and system of record.
  3. Record identifiers, consent basis, retention, and allowed uses.
  4. Mark whether each signal trains platform optimization, supports independent evaluation, or both.
  5. Identify duplicate collection, inaccessible evidence, missing post-conversion outcomes, and circular validation.
  6. Require a canonical source for business outcomes.
  7. Return a ledger conforming to shared/schemas/advertising/signal-ownership-ledger.schema.json.

Read when needed

  • Use references/ownership-questions.md during stakeholder discovery.

Guardrails

  • Do not treat platform reporting as independent validation.
  • Do not assume the advertiser owns or can export a platform-derived signal.
  • Do not recommend collecting data without a documented purpose and consent basis.
  • Never place secrets or raw personal data in the ledger.
View file metadata
---
name: advertising-signal-ownership-auditor
description: Audit who collects, controls, receives, retains, and uses advertising and commerce signals across pixels, server events, campaign platforms, CRM, orders, returns, and support systems. Use when designing measurement ownership, first-party evidence, platform optimization, or agentic advertising governance.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install adtech/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install adtech/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install adtech/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: analysis-only

Approval boundary: May audit and recommend; privacy, consent, retention, and platform configuration changes require responsible human approval.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: adtech/advertising-signal-ownership-auditor

Tags: measurement, signal-ownership, pixel, conversions-api, governance

Runtimes: codex, claude, generic

Tool dependencies: 1

API dependencies: 0

Dependencies

Tools: shared/schemas/advertising/signal-ownership-ledger.schema.json

APIs: Not documented

Outputs

  • Signal ownership ledger
  • Measurement gaps
  • Independent evidence plan