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).

75

Quality

93%

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

86%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.

An information-dense, actionable conventions skill that leans on concrete code blocks and a closing validation checklist, with clean navigation to sibling skills; only mildly improvable on prose tightness in a few rationale sentences.

DimensionReasoningScore

Conciseness

Dense and judgment-call focused, mostly assuming Claude's competence and avoiding generic GitHub Actions primer; minor prose rationales (e.g. 'The default is 6 hours — a hung job burns paid minutes silently') could be trimmed, but most tokens earn their place as PostHog-specific context.

4 / 5

Actionability

Provides multiple complete, concrete YAML blocks (concurrency, bounded checkout, App-token, paths filter), specific commands (`bin/hogli lint:workflows`, `actionlint`), and named canonical files covering the common cases; placeholders like `<sha>` are deliberate pinning instructions rather than gaps.

5 / 5

Workflow Clarity

Logical structure from 'Before you write' through topic sections to an explicit 'New-workflow checklist' that ends with a validation checkpoint (`lint:workflows` and `actionlint` pass locally); it is a conventions reference rather than a tight destructive-operation workflow, so it lacks formal feedback loops but the checklist supplies the gate.

4 / 5

Progressive Disclosure

Single well-sectioned SKILL.md with clearly signaled one-level-deep pointers to sibling skills ('Details: `/depot-github-runners`', 'Related skills — reach for these instead of duplicating them here') and named canonical repo files; no bundle files exist and none are needed, and content is appropriately kept inline as judgment-call guidance.

5 / 5

Total

18

/

20

Passed

Description

100%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 highly specific, well-triggered description that concretely names the domain, lists concrete actions, gives explicit 'when' guidance, and cleanly separates itself from adjacent skills via boundary statements.

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' — comprehensive coverage of the workflow-authoring domain rather than vague language.

5 / 5

Completeness

Explicitly answers both what ('Covers PostHog's workflow-authoring conventions and the reasons behind them') and when ('Use when adding or editing a GitHub Actions workflow... under `.github/`'), plus explicit out-of-scope boundary guidance.

5 / 5

Trigger Term Quality

Uses natural developer-facing terms ('GitHub Actions workflow', 'composite action', 'reusable workflow', 'CI jobs', 'checkout', 'caching', 'runner') with synonyms and file-path triggers (`.github/`), matching how a user would phrase the need.

5 / 5

Distinctiveness Conflict Risk

Clear niche (workflow authoring under `.github/`) with explicit disambiguation from sibling skills — 'Not for debugging red CI (use debugging-ci-failures) or wiring a new secret end to end (use managing-github-actions-secrets)' — minimal conflict risk.

5 / 5

Total

20

/

20

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.