lineth-quickstart

Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or local L1 finality. Use whenever you are working inside the lineth-stack quickstart and need to boot or run the stack, choose between local and Sepolia L1 mode, get past the Sepolia deployer-funding step, read the finality/success signals, run traffic or bridge smoke tests, reset it, or debug a failing boot (L1 RPC unreachable, deploy gas too low, unfunded deployer, port collision, prover out-of-memory, address mismatch, finality not advancing). Trigger even on casual asks — "start the stack", "run the quickstart", "boot lineth locally", "my deploy keeps failing", "finality isn't happening", "reset the quickstart". When editing this package's scripts or docs, also read rules/making-changes.md so commits pass the repo's lint and DCO gates.

Quality

90%

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

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.

A well-architected routing skill: it stays lean by deferring procedure to a single source of truth and layers high-value triage and commit rules on top. Actionability and workflow clarity are strong but not maximal because the primary boot command and detailed validation steps are delegated rather than inlined.

Suggestions

Inline the one or two canonical boot commands (or a one-line 'to boot: see the boot section of AGENTS.md') so the primary task is actionable without opening the referenced file.

Add a short inline validation checklist for reset (a destructive operation) — e.g. confirm containers stopped and artifacts cleared — rather than relying solely on rules/debugging.md.

Consider including a compact symptom→cause→fix table inline for the most common failure (Sepolia deployer funding) since it is called out as the classic false step.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it explicitly refuses to restate the boot procedure ('duplicating it here would let the two drift apart'), assumes Claude knows Docker/L2 basics, and every section (Start here, two common mistakes, failure triage, change rules) earns its tokens with non-obvious operational detail.	5 / 5
Actionability	Gives concrete commands and paths ('git rev-parse --show-toplevel', './scripts/check-quickstart-static.sh', 'git commit -s', allowed scope 'misc') and exact files to read, but delegates the core boot command itself to AGENTS.md rather than inlining it — a minor gap for the primary task.	4 / 5
Workflow Clarity	Clear sequence (route to AGENTS.md/README.md → operate → triage → change with validation gate) with explicit checkpoints ('they win', success = observed finalizeBlocks + advancing currentL2BlockNumber, Hard STOP conditions); the detailed validation steps live in referenced files, leaving minor gaps rather than a fully inline checklist.	4 / 5
Progressive Disclosure	A clear overview that points one level deep to well-signaled package files (AGENTS.md, README.md, rules/debugging.md, rules/making-changes.md, scripts/check-quickstart-static.sh); content is appropriately split across those sources and easy to navigate, with no nested references.	5 / 5
	Total	18 / 20 Passed

Description

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

An unusually strong description: concrete capability list, explicit when-to-use clause with casual trigger phrases, and a tight distinct niche. The only weakness is second-person voice ('you are working'), which costs one point on specificity per the rubric guideline.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (boot/run, choose L1 mode, get past deployer-funding, read finality signals, run traffic/bridge smoke tests, reset, debug seven named failure modes), which is comprehensive coverage at the 5 anchor; reduced by one per the second-person-voice penalty since it uses 'Use whenever you are working' rather than third person.	4 / 5
Completeness	Explicitly answers both 'what' (operating manual for the Docker-Compose quickstart that boots a local Linea/Lineth L2) and 'when' ('Use whenever you are working inside the lineth-stack quickstart and need to...' plus 'Trigger even on casual asks') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Quotes natural casual phrases users would actually say — 'start the stack', 'run the quickstart', 'boot lineth locally', 'my deploy keeps failing', 'finality isn't happening', 'reset the quickstart' — comprehensive coverage including synonyms and paraphrases.	5 / 5
Distinctiveness Conflict Risk	Targets a clearly named niche (the Lineth Stack quickstart, a specific Docker-Compose dev/demo stack in the lineth-monorepo) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: LFDT-Lineth/lineth-monorepo
Path: docs/getting-started/lineth-stack/.agents/skills/lineth-quickstart/SKILL.md
Commit: b75b5ca

Reviewed: 5 days 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.