signals-scout-skills-store

Audits a team's PostHog skills store for authoring violations and files hygiene reports.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-skills-store
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signals-scout-skills-store
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-skills-store
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-skills-store

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Poorly authored agent skills — vague descriptions, bloated bodies, dead file links, or committed secrets — silently degrade every agent run that loads them, and teams have no systematic way to catch these issues as their skills store grows.

Core Features & Use Cases

  • Fresh-skill sweep: Checks recently changed skills against an 8-rule checklist covering description quality, name format, body size, single responsibility, link hygiene, secrets, instruction style, and duplication.
  • High-leverage deep pass: On a weekly rotation, audits the store's most-used or most-referenced skills even when unchanged, ranked by usage telemetry, version churn, or cross-references.
  • Report authoring and dedupe: Files one P3 recommendation report per non-compliant skill via the inbox report channel, editing existing reports on regressions instead of duplicating, with per-version dedupe tracked in a scratchpad.
  • Use Case: A team maintains dozens of shared agent skills in PostHog; this scout runs on a schedule, detects that a skill bundles a dead reference link and a leaked API key, and files a copy-ready fix report routed to the skill's author.

Quick Start

Run the skills-store scout to audit recently changed skills in our PostHog skills store and file reports for any authoring violations found.

Frequently Asked Questions about signals-scout-skills-store

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

FAQPage Schema
How do I audit agent skills for authoring best practices?

Run this scout against the skills store: it lists skills newest-first, fetches each fresh skill's fields, body, and file manifest, then checks them against an 8-rule checklist covering descriptions, naming, body size, links, secrets, and duplication.

How does the scout detect leaked secrets in skills?

It scans every textual field and every bundled file in the skill manifest for credential patterns such as phx_, phs_, sk-, ghp_, AKIA, private key blocks, and hardcoded bearer tokens. Reports redact the matched value and cite only the file, line, and token family.

Does the scout re-report skills it already flagged?

No. Dedupe entries are tracked per skill version in the scratchpad, and the inbox is searched before authoring. A skill still broken at a newer version gets its existing report edited rather than a duplicate filed.

What MCP tools does the skills-store scout require?

It needs read-only skill tools (skill-list, skill-get, skill-file-get), inbox report tools (inbox-reports-list, inbox-reports-retrieve), scratchpad memory tools, and the emit-report and edit-report report channel. Usage analytics tools are optional for the deep pass.

When does the scout skip auditing a skill?

It skips unedited seeded scout skills, the unchanged long tail outside the fresh set and high-leverage tier, archived or deleted skills, single-user scratch skills, and purely subjective style judgments with no rule behind them.