agentleFS
youcislayoucisla/Agent-Foundry/skills/optional/funnel-pr-guard/SKILL.md

funnel-pr-guard

Skill1 starsChanged 23 days agoMITView on GitHub

Every PR that touches the front door must state which funnel step it

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Every PR that touches the front door must state which funnel step it changes and by how much.

    line 16
  2. Distinctive:

    No user content in event meta

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Funnel PR Guard

Every PR that touches the front door must state which funnel step it changes and by how much.

When to Use

  • Diff touching landing, auth, onboarding, invite, or loading screens
  • Adding funnel/tracking events
  • Any PR that could affect signup → activation conversion

Procedure

1 — Identify the funnel step affected

Generic funnel steps for any web app:

visitor → signup_started → signed_up → activated → core_engagement → retention

State in the PR body which step(s) the change affects.

2 — Ensure tracking table exists

create table public.funnel_events (
  id uuid primary key default gen_random_uuid(),
  user_id uuid not null references auth.users(id) on delete cascade,
  event text not null,
  meta jsonb,
  created_at timestamptz not null default now()
);
alter table public.funnel_events enable row level security;
create policy "insert own" on public.funnel_events for insert to authenticated
  with check (auth.uid() = user_id);

3 — Fire-and-forget, no sensitive content

supabase.from('funnel_events').insert({
  user_id: session.user.id,
  event: 'event_name',
  meta: { version: 'v2' }
}).then().catch(() => {})

Rule: meta must never contain user content, PII, or proprietary data. IDs and event names only.

4 — Weekly funnel query

select event, count(*) as total, count(distinct user_id) as unique_users,
  min(created_at) as first_seen, max(created_at) as last_seen
from public.funnel_events
where created_at > now() - interval '7 days'
group by 1 order by 2 desc;

5 — Gate check before merging

Before merging, confirm:

  • Funnel step stated in PR body with expected direction
  • funnel_events table exists (or migration created it)
  • No user content in event meta
  • Rollback: feature flag (env var or toggle)
  • Data shows the expected change after N users flow through

Anti-patterns

  • A front-door PR with no funnel step in the body.
  • meta carrying user text, PII, or proprietary data.
  • A conversion change with no rollback path.

References

  • details

Verification Checklist

  • Affected funnel step and expected direction are in the PR.
  • funnel_events exists or its migration ships.
  • Event meta contains only IDs and event names.
  • A flag or toggle can roll back the change.
  • Post-merge data is compared with the expected direction.

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.