ingestion-pipeline-doctor-nodejs

Ingestion pipeline architecture overview and convention reference. Use when you need a quick orientation to the pipeline framework or want to know which doctor agent to use for a specific concern.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/ingestion-pipeline-doctor-nodejs/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured orientation reference that earns its tokens with domain-specific convention knowledge and concrete routing. The detailed convention paragraphs are the main candidate for extraction into separate reference files.

Suggestions

Consider moving the fan-out/fan-in and batching lifecycle convention detail into dedicated reference files, leaving the SKILL.md as a concise overview with one-level-deep pointers.

Add a short 'how to invoke a single doctor' example command alongside the 'run all doctors' note so the primary action is copy-paste ready.

Tighten the fan-out/fan-in paragraph by leading with the one-line rule and moving the sub-result contract into a compact list.

Dimension	Reasoning	Score
Conciseness	Dense, reference-style content that assumes framework familiarity and avoids explaining basics; the fan-out/fan-in and batching lifecycle paragraphs are long and could be tightened slightly, keeping it just below a 5.	4 / 5
Actionability	Concrete file paths in tables, named agents with when-to-use guidance, and explicit convention rules give actionable direction; it is a reference skill with no copy-paste code, but the guidance is specific and executable in the routing sense.	4 / 5
Workflow Clarity	The architecture diagram lays out a clear step sequence and the agent table gives routing logic; no destructive or batch operation is being instructed here, so the validation cap does not apply, but there is no explicit multi-step validated workflow to reach a 5.	4 / 5
Progressive Disclosure	Well-organized into distinct sections with one-level-deep 'Details: ...test.ts' pointers to deeper docs; the detailed fan-out/fan-in and batching convention paragraphs are arguably material that could live in separate reference files, which keeps it at 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

68%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clearly targeted, niche description with an explicit 'Use when' clause covering both orientation and agent selection. The main weakness is second-person voice and a somewhat abstract 'what' statement, which together hold specificity down.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'Ingestion pipeline architecture overview and convention reference. Use when orienting to the pipeline framework or selecting a doctor agent for a specific concern.'

Make the 'what' more concrete by naming the actual deliverables (e.g. 'Summarizes the step-chain architecture, key file locations, and per-concern doctor-agent routing').

Add a couple of natural trigger synonyms (e.g. 'pipeline steps', 'ingestion results', 'pipeline composition') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus two orientation/agent-selection actions ('quick orientation to the pipeline framework', 'know which doctor agent to use'), but the actions are reference functions rather than concrete operations; the second-person phrasing ('you need', 'want to know') triggers the voice penalty, lowering it from a base of 3.	2 / 5
Completeness	Explicitly answers both what ('Ingestion pipeline architecture overview and convention reference') and when ('Use when you need a quick orientation... or want to know which doctor agent to use'), with the 'what' side slightly generic.	4 / 5
Trigger Term Quality	Natural domain terms a user would say — 'ingestion pipeline', 'pipeline framework', 'doctor agent' — give good coverage for this niche, though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche — PostHog ingestion pipeline doctor agents — with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: .agents/skills/ingestion-pipeline-doctor-nodejs/SKILL.md
Commit: 06292db

Reviewed: 23 minutes ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.