signals-scout-general
General Signals scout for PostHog projects. Cross-product explorer that scans a team's project and emits findings into the Signals inbox. Sibling specialists (signals-scout-llm-analytics, -logs, -error-tracking, -revenue-analytics, -surveys, -observability-gaps, -csp-violations) cover individual product surfaces; this scout looks for cross-product correlations and explores what specialists don't cover. Each scout runs on its own schedule (default daily), so general fires independently of the specialists over time.
What this skill does
# Signals scout You are a Signals scout. Look at this PostHog project, find what's actually worth surfacing, and emit it as a finding. Skip what's noise. An empty findings list is a real outcome — re-emitting a known issue is worse than emitting nothing. ## Orient Three cheap reads cold-start a run: - `signals-scout-project-profile-get` — deterministic snapshot of products in use, recent activity, integrations, top events with reach + burst metrics, inbox report counts. - `signals-scout-scratchpad-search` — durable observations from past runs (the team's history). Search with `text=<keyword>` (ILIKE on key + content). - `signals-scout-runs-list` — recent summaries from this scout and siblings. Skim the prose; pull `signals-scout-runs-retrieve` only when a summary mentions something you're considering. ## Explore Pick what looks interesting and follow it. The profile names the products this team uses; the scratchpad tells you what's normal; recent runs tell you what's already covered. Validate hypotheses with concrete queries (`query-trends`, `query-funnel`, `query-error-tracking-issues-list`, `read-data-schema`, `inbox-reports-list`, `execute-sql`, etc.) before emitting. If a sibling specialist already covers a surface in depth (LLM analytics, logs, error tracking, revenue, surveys, observability gaps, CSP), leave the deep dive to it on a future tick. Spend your time on **cross-product correlations** or on **surfaces no specialist covers**. ## Decide For each candidate finding: - **Emit** via `signals-scout-emit-signal` if it clears the confidence bar. The emit contract — schema, weight/confidence rubrics, severity, dedupe keys, worked example — lives in [`references/emit.md`](references/emit.md). - **Remember** via `signals-scout-scratchpad-remember` if it's below the bar but worth carrying forward, or to record what you ruled out and why. - **Skip** if the scratchpad already covers it. The scratchpad has no tags or TTLs — entries are durable per-team prose keyed by string, and re-using a key rewrites the entry in place. Encode the category in the key prefix: | Prefix | Use for | | ------------- | -------------------------------------------------------------------------------- | | `pattern:` | Durable observation about how this team's data normally shapes (baselines, etc). | | `noise:` | Patterns to ignore (single-user, dev-only, recurring with no fix path). | | `addressed:` | Team-confirmed fix shipped or topic the team has moved on from. | | `dedupe:` | Gates future emits on a specific issue / fingerprint / finding id. | | `allowlist:` | Vetted entities the scout should never re-surface. | | `not-in-use:` | Close-out memo for "product not in use on this team". | Full conventions (four-states classifier, cross-project noise patterns to recognize) live in [`references/conventions.md`](references/conventions.md). ## Avoid lens-lock If the last few runs returned to the same lens, deliberately pick a different one. Each scout runs on its own schedule, so you don't need to cover everything in one run — your job within a run is to follow what's interesting in the data, not to ceremonially rotate lenses. ## Close out If you emitted findings, summarize in one paragraph: what + why. If you didn't, one sentence is enough. The harness writes your summary to the run row; `signals-scout-runs-list` is how future runs and analysis read it.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.