By cmgramse
Active analytics instrumentation plugin — owns the canonical event taxonomy, the tracking plan, and write-side tag/event/custom-dimension/key-event/consent configuration across analytics platforms (GA4, Zaraz, GTM, PageSense), plus live verification that the right events actually fire (pre/post-consent). Ships instrumentation-engineer (plan + apply, write-capable) and instrumentation-auditor (live-firing audit, read-only). Provider-neutral, role-based dispatch over adapters; automation-first (MCP > CLI > API > handoff) behind hard cost/credential/consent gates. The producer that turns measurement-contract@1 requirements into real collected signals for measurement-and-optimisation to read.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
VERIFIES that analytics instrumentation actually fires correctly on the live site — loads the page, observes what really happens (dataLayer pushes, tag-manager / Zaraz / GTM activity, GA4 hits, network beacons) before AND after consent, and compares it against the tracking plan to produce a gap report. Use when the user wants to: check / audit / verify / debug whether events are firing, confirm tracking is working, validate that GA4 / a tag manager is collecting the right events with the right parameters, check consent gating (does tracking fire before consent?), find missing or misfiring events, or QA an instrumentation change before trusting the data. Also triggers on: "is tracking working", "are events firing", "verify GA4 events", "check the dataLayer", "audit our analytics tracking", "tracking isn't firing", "events missing in GA4", "does tracking fire before consent", "consent gating check", "instrumentation gap report", "QA the tags". READ-ONLY / inspect — it never mutates tracking, consent, or platform config. For PLANNING or APPLYING instrumentation (the write side), use instrumentation-engineer. For analysing the collected data, use measurement-and-optimisation:measurement-analyst. For rendered-UX / consent-as- dark-pattern review, use site-reviewer.
The single WRITE-EXECUTOR of the collection + experimentation layer. APPLIES analytics instrumentation (event taxonomy, custom dimensions, key events / conversions, tags/triggers, consent gating) AND executes the PageSense A/B + Split-URL experiment lifecycle — create/configure (variations, traffic allocation, audiences), attach goals, publish/pause/delete — driving the pagesense-write MCP. Use when the user wants to: set up / add / fix event tracking, define a tracking plan or event taxonomy, configure GA4 custom dimensions or key events, wire tags/triggers, instrument a page or funnel, "make the analytics collect X" — OR create / configure / publish / pause / delete a PageSense experiment, set up an A/B or Split-URL test, adjust variation traffic allocation, attach a goal, "run the experiment we planned", "launch the test". Provider-neutral, automation-first (MCP > CLI > API > handoff), behind cost/credential/consent gates; experiment publish/pause/delete + traffic shifts require explicit confirm (P8/R25). WRITE-CAPABLE — optimisation-strategist PLANS experiments, you EXECUTE them. For VERIFYING events fire live use instrumentation-auditor; for reading collected data use measurement-and-optimisation:measurement-analyst; for source-code event-firing hand off to site-builder.
Admin access level
Server config contains admin-level keywords
This repository (skill-development) is the skill factory for iurFriend: the centralized environment where all Claude Code plugins are developed, tested, and refined. It is structured as a plugin marketplace (iurfriend-skills), but the primary activity is building and refining skills, not distributing them. Forward-going, marketplace-distributable skills ship as plugins (single- or multi-skill) per Anthropic's canonical shape.
First stop for anyone (AI or human) doing skill work — read these three before touching anything:
CLAUDE.md— the de-facto orientation doc: the full plugin catalog, plugin architecture, credential/contract/orchestrator doctrine, and the development workflow.PATTERNS.md— Layer-0 canonical index of every binding doctrine, principle, R-decision, and shared contract (routes to the sources in.agents/andconcepts/skills-ecosystem/).AGENTS.md— the Codex / Opencode parity entry-point; mirrors CLAUDE.md's catastrophic-invariant summary for non-Claude harnesses.The README below is the marketplace-facing front door. The canonical rules live in the three files above — this README orients, it does not govern.
25 marketplace plugins (plus the resident iurfriend-skill-patterns carrier, counted separately) across the marketing operating system and supporting web/management/observability tooling — brand extraction, funnel and conversion design, SEO, content creation, concept development, measurement and optimisation, site building/design/review/refactor, solution architecture, team and finance operations, data-collection engineering, creative media and podcast generation, voice, and LLM observability operators (LangFuse, MLflow).
Plus a vendored (third-party) tier — 18 vetted-external developer-tooling and productivity plugins imported for iurFriend employees (superpowers, beads, cloudflare, n8n-skills, supabase, obsidian-skills, defuddle, impeccable, extract-design, agent-browser, using-entire, frontmatter-generation, asana, and the official agent-sdk-dev / claude-code-setup / claude-md-management / feature-dev / mcp-server-dev). These are not factory-built: each is copied verbatim from a permissively-licensed upstream (MIT/Apache-2.0, or license flagged UNCONFIRMED), carries its LICENSE + UPSTREAM.md, and is listed in the auditable VENDORED.md register. The Anthropic docx/xlsx/pdf/pptx document skills are proprietary and not vendored; they are approved for install directly on iurFriend laptops — see EXTERNAL-PLUGINS.md (the companion register to VENDORED.md) for the exact install commands. Full vendored per-plugin catalog: the Vendored plugins section in CLAUDE.md.
For the authoritative, per-plugin catalog with one-line purposes, see the Plugins in This Marketplace table in CLAUDE.md. It is kept current; this README does not duplicate it.
Every top-level entry, one line each. Plugin directories are listed collectively (each is a self-contained plugin — see the canonical layout in CLAUDE.md § Plugin Architecture); the per-plugin catalog is in CLAUDE.md.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub cmgramse/skill-development --plugin data-collection-engineeringMLflow GenAI observability and evaluation operator — onboarding, tracing instrumentation, trace/session analysis, agent evaluation, metrics, and docs search.
Local podcast studio — turns any source (topic, URL, PDF, markdown, repo) into a finished branded episode: research, multi-voice script, Gemini TTS, music mix, show notes, and cover image. Ships the podcast-studio orchestrator skill and a /podcast command. Brand-as-config via show profiles; decoupled from any cloud control plane.
Rendering presenter — brainstorms, selects, and renders the most impactful visualisations for producer artifacts or ad-hoc data into self-contained (or interactive) reports. Emits frontmatter-free presentation siblings under presentation-sibling-contract@1. A strict presenter: it represents data and producer-supplied interpretations, never computes new findings, scores, deltas, or verdicts.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Project bootstrap operating layer for Codex, Claude Code, and OpenCode: Beads setup, audit logging, AGENTS.md, CLAUDE.md, project rules, and orchestrator/executor/reviewer roles.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Production-grade vibe coding suite. Structured workflows from discovery to deployment: start, build, ship, fix, refactor.
Plugin that includes the Figma MCP server and Skills for common workflows
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
Claude Code settings and skills for spec-driven development workflows
Give your AI a memory — mine projects and conversations into a searchable palace. 35 MCP tools, auto-save hooks, and guided setup.