skills.rest
ithaloazevedo
ithaloazevedoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

metricas

Detect and configure external metric sources like GitHub, Plausible, and Stripe for a product.

Updated May 31, 2026
Search Tags:#analytics#metrics#configuration#detection#stripe#adapters#plausible
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill metricas-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: metricas
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/metricas
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill metricas-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Products often lack a configured set of metric sources, especially projects started before automated detection existed, leaving teams without a reliable way to know which analytics, payment, or deployment signals they can pull. ## Core Features & Use Cases - Signal Scanning: Inspects git remotes, package manifests, environment variables, and SDK installs to detect candidate metric sources automatically. - User-Guided Confirmation: Asks about deployment URLs, payment providers, app stores, and support channels that the repository cannot reveal, then confirms each source as yes, no, or later. - Adapter Generation: Creates per-source metric adapters when none exist and writes the confirmed source list to .Codex/jit-tooling/active-metrics.yml. - Use Case: A project predating v0.14 has no active-metrics configuration; run this skill to scan the repo, confirm Stripe and Plausible as sources, generate adapters, and prepare for the first metrics pull. ## Quick Start Run the metricas skill to detect which external metric sources apply to my product and configure the adapters for each confirmed source.

Frequently Asked Questions about metricas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect which metric sources apply to my product?▼

Run the metricas skill to scan git remotes, package manifests, environment variables, and SDK installs for candidate sources. It then asks about deployment URLs, payment providers, and app stores that the repository cannot reveal, and confirms each source with you.

How do I configure metric adapters for Stripe or Plausible?▼

After detection confirms a source, the skill checks for an existing adapter in the metrics-adapters directory. If none exists, it follows the GENERATING.md guide to create one, presents it for review, and saves it on your confirmation.

Does metric detection pull actual metrics data?▼

No, detection and data pulling are separate phases. This skill only identifies and configures sources; you run the metrics-pull command afterward to fetch the first snapshot, keeping network calls under your control.

Does the skill store my API credentials?▼

No, it never stores credentials. For each source it states which environment variables or vendor CLI authentication you need, verifies you have them, and marks sources as deferred rather than active when setup is incomplete.

When should I rerun metric source detection?▼

Rerun it when new infrastructure is added such as a new analytics provider or payment processor, when an existing adapter is over 180 days old, or when you want to review and reconfigure the current source list.

Related Skills

Explore More Product & Management Skills→
ax-llmax-llm
2.9k

ax-rust-gepa

Implement Rust code for Ax GEPA optimization with axllm.

Official
Advanced
coalesce-labscoalesce-labs
20

feature-results

Generate a structured Markdown post-launch feature results document.

Official
Advanced
ryan0122ryan0122

github-analytics-scoring

Score GitHub repository health and prioritize issues, PRs, and discussions.

Community
Advanced
jeremylongshorejeremylongshore

repo-scanning

Scan GitHub repositories to gather evidence for bug cluster analysis.

Community
Advanced