CtrlK
BlogDocsLog inGet started
Tessl Logo

authoring-ci-workflows

Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under `.github/` — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, `timeout-minutes`, `paths` filters, caching, or runner choice. Covers PostHog's workflow-authoring conventions and the reasons behind them: the 500-runs/10s dispatch cap, shallow vs full clone, per-SHA push concurrency, dedicated App-token rate-limit buckets, and fork-safe secrets on a public repo. Points to the linters (`bin/hogli lint:workflows`, actionlint) that enforce the mechanical rules, and to the narrower skills for production deploys, secrets, and Depot runners. Not for debugging red CI (use debugging-ci-failures) or wiring a new secret end to end (use managing-github-actions-secrets).

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A high-quality conventions reference that delivers PostHog-specific judgment calls the linters cannot enforce, with executable YAML, named canonical files, an explicit lint validation gate, and a closing checklist. It is dense but not padded, and delegates cleanly to narrower sibling skills.

DimensionReasoningScore

Conciseness

Dense, specialized PostHog knowledge Claude does not already have (dispatch cap, per-SHA concurrency, blobless-checkout foot-guns, App-token buckets) with no basic-concept padding; rationale sentences are the promised 'reasons behind them' rather than fluff, so every token earns its place.

3 / 3

Actionability

Provides copy-paste YAML blocks (concurrency group, bounded blobless checkout, paths filter, App-token with fork fallback), concrete commands ('bin/hogli lint:workflows', 'actionlint'), and named canonical files, matching the executable copy-paste-ready anchor.

3 / 3

Workflow Clarity

Sequenced 'Before you write' guidance, an explicit validation gate ('Run bin/hogli lint:workflows and actionlint before pushing'), a 'New-workflow checklist', and error-recovery guidance (empty-mode normalization on drafts, continue-on-error then promote-to-blocking rollout) satisfy the clear-sequence-with-validation-and-feedback anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so the skill is appropriately self-contained and well-sectioned; it delegates to sibling skills one level deep with clear signaling ('Related skills — reach for these instead of duplicating them here') rather than nesting references.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, well-scoped description that opens with an explicit 'Use when' trigger enumerating concrete workflow-authoring tasks, explains the PostHog-specific rationale, and explicitly disambiguates from adjacent skills. It avoids fluff, uses third person, and gives clear positive and negative triggers.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice' — matching the anchor for multiple specific concrete actions rather than a partial domain/action list.

3 / 3

Completeness

Explicitly answers both what (PostHog workflow-authoring conventions) and when ('Use when adding or editing a GitHub Actions workflow...'), plus negative triggers ('Not for debugging red CI'), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural terms a developer authoring CI would say ('GitHub Actions workflow', 'composite action', 'reusable workflow', 'timeout-minutes', 'paths filters', 'action pinning', 'checkout/clone', 'runner') with broad coverage and consistent third-person voice ('Use when', 'Covers', 'Points to', 'Not for').

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation ('Not for debugging red CI (use debugging-ci-failures) or wiring a new secret end to end (use managing-github-actions-secrets)') and pointers to sibling skills, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
Reviewed

Table of Contents

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.