CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

effect

Starlight Effect v4 house conventions - namespace-wrapped service modules, layers, runtime assembly, typed errors, and ast-grep enforcement. Load when writing or reviewing any Effect TypeScript code in this repo.

Quality

86%

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

82%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 dense, executable house-conventions reference that avoids conceptual padding and supplies copy-paste templates plus concrete commands. Its only real weakness is that the long inline anatomy template and ast-grep rule detail could be externalized for tighter progressive disclosure.

Suggestions

Move the full service-module anatomy template into a references/ file and keep a condensed skeleton inline to reduce token cost on every load.

Extract the ast-grep rule catalog (structural + rewrite rules) into a separate reference so the main body stays a quick overview.

Add an explicit 'validate -> fix -> re-run' loop for service-layer changes, mirroring the rule-edit feedback loop, to push workflow clarity higher.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no 'what is Effect' padding), but the ~28-line service anatomy template is long enough to count as a minor instance of content that could be trimmed or externalized.

4 / 5

Actionability

Fully executable guidance throughout: a copy-paste-ready namespace template, concrete commands ('bun run lint', 'bun run test:ast-grep-rules'), and exact repo paths ('script/ast-grep/rules', 'apps/server/src/services/runtime.ts') cover the common cases.

5 / 5

Workflow Clarity

The conventions are sequenced from service anatomy through errors, naming, runtime assembly, and enforcement, with a validation checkpoint ('verify with bun run test:ast-grep-rules') for rule edits; minor gaps remain since it is reference-oriented rather than a single end-to-end workflow.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and no bundle files to mismanage; it stays just above the simple-skill line and could still split the ast-grep rule detail into a reference file.

4 / 5

Total

17

/

20

Passed

Description

83%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 tight, third-person description that clearly names its niche and trigger conditions while enumerating concrete convention areas. It is held back only by minor overlap risk with a generic Effect skill and a few missing synonym triggers.

Suggestions

Add a distinguishing disambiguator in the description (e.g. 'project-specific rules, not general Effect guidance') to reduce overlap with a global Effect skill.

Include a synonym trigger such as 'Effect-TS' or 'Effect service' so users who phrase it differently still hit this skill.

DimensionReasoningScore

Specificity

Names the domain (Effect TypeScript in this repo) and several concrete convention areas ('namespace-wrapped service modules, layers, runtime assembly, typed errors, and ast-grep enforcement'), but these are convention categories rather than fully enumerated actions, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly states both what ('Starlight Effect v4 house conventions - namespace-wrapped service modules, layers, runtime assembly, typed errors, and ast-grep enforcement') and when ('Load when writing or reviewing any Effect TypeScript code in this repo') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ('writing or reviewing any Effect TypeScript code'), with good keyword coverage, though synonyms like 'Effect-TS' or 'Effect service' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'Starlight ... house conventions' framing scoped 'in this repo' carves a clear niche, but 'Effect TypeScript' overlaps with a general-purpose Effect skill, creating minor conflict risk.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

divaltor/starlight

Path

.opencode/skills/effect/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.