CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pi-inngest

Use Pi from Inngest safely in joelclaw. Covers event-driven detached Pi CLI runners, direct pi-ai calls inside step.run, service-account OAuth auth, claim-check files, and when to choose each pattern.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/pi-inngest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 strongly actionable, well-sequenced operational doctrine with explicit validation and failure handling, delivered as a dense single-file monolith. The main weaknesses are inline time-sensitive receipts and the absence of any reference-file split for the long auth and pattern sections.

Suggestions

Move the Service Account Auth Contract (including the bridging options and setup helper details) into a references/ file and keep a short contract summary in SKILL.md.

Isolate dated bench receipts and the model-lane note in a clearly labeled receipts/deprecated section so stale time-sensitive data does not blend with current doctrine.

Either define or briefly specify the contracts for Pattern B's helper functions (writePiRequestClaimCheck, spawnDetachedPiWrapper, routePiResultToEvent) so the skeleton is fully executable.

DimensionReasoningScore

Conciseness

The body is dense, project-specific doctrine that assumes Claude's competence and rarely explains known concepts, but inline time-sensitive material — 'Bench receipt from 2026-06-20', dated receipt paths from 2026-06-17, and the 'verified model lane is openai-codex/gpt-5.6-sol' — is not isolated in an old-patterns/deprecated section, and the Utah Sidecar narrative section could be tightened.

3 / 5

Actionability

Pattern A is fully executable copy-paste TypeScript, and the auth-verification Node script, CLI invocation flags, and setup-pi-service-auth.sh commands are concrete and runnable; however, Pattern B's skeleton depends on undefined helpers (writePiRequestClaimCheck, spawnDetachedPiWrapper, routePiResultToEvent), leaving minor gaps.

4 / 5

Workflow Clarity

Pattern B is laid out as an explicit 7-step numbered sequence, backed by a 7-item testing checklist with concrete proofs ('Prove step.waitForEvent resumes', 'Prove timeout writes a failure claim-check') and a failure-handling section that defines a terminal event for every failure mode — explicit validation checkpoints with error-recovery paths.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but this is a ~370-line single-file skill with no bundle files; the service-account auth contract, bench receipts, and both pattern implementations are inlined content that clearly belongs in separate reference files.

3 / 5

Total

15

/

20

Passed

Description

75%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, distinctive description with concrete capability enumeration, weakened only by the absence of an explicit 'Use when...' trigger clause and some missing natural keyword variations. Adding a trigger sentence would raise completeness and trigger-term quality to top levels.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a task mentions pi-ai, launching pi from an Inngest function, pi/workflow.* events, detached Pi CLI children, or service-account Pi auth.'

Include natural keyword variations users would actually type, such as '@earendil-works/pi-ai', 'step.waitForEvent', and 'pi/workflow' event names, to strengthen trigger-term coverage.

Consider naming the OpenAI Codex/subscription auth lane explicitly since it is a primary use case in the body.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'event-driven detached Pi CLI runners, direct pi-ai calls inside step.run, service-account OAuth auth, claim-check files, and when to choose each pattern' — giving comprehensive, specific coverage of the skill's scope rather than a partial list with gaps.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance; 'when to choose each pattern' only disambiguates between the covered patterns and does not state when to load the skill, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms like 'Pi', 'Inngest', 'pi-ai', 'step.run', 'Pi CLI', and 'OAuth' would be said by a user needing this skill, but common variations the body itself lists (e.g. '@earendil-works/pi-ai', 'pi/workflow.*' events, 'Codex') are missing from the description, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Use Pi from Inngest safely in joelclaw' carves out a clear niche (Pi+Inngest integration in one specific codebase) with distinct triggers, making confusion with other skills unlikely.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/pi-inngest/SKILL.md

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.