Lythoskill creator

Skill lythos-labs/lythoskill/skills/lythoskill-creator

Scaffold and build projects for the lythoskill ecosystem only. Creates thin-skill monorepos: heavy logic in npm packages (Starter), agent-facing instructions in lightweight SKILL.md (Skill), build output committed to skills/ (Output).From its SKILL.md

Install

npx -y skills add lythos-labs/lythoskill --skill lythoskill-creator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.7 KB, as published. Nobody here has run it

lythoskill-creator

Not a generic skill creator. This scaffolds projects for the lythoskill ecosystem only. If you just want to write a skill, create a SKILL.md file directly — no tooling needed.

A lythoskill project separates concerns into three layers:

Starter (packages/<name>/): npm-publishable package with CLI. All dependencies managed here.
Skill (packages/<name>/skill/): Thin SKILL.md + scripts that call the starter via bunx.
Output (skills/<name>/): Build output copied from Skill layer. Committed to Git so consumers can clone and use without building.

Scripts

init

Scaffold a new lythoskill monorepo.

bunx @lythos/[email protected] init <project-name>

Creates a monorepo with a starter package and an example skill.

add-skill

Add a new skill to an existing lythoskill monorepo. Follows the cortex Step 1/2/3 pattern: CLI creates template → agent fills content → probe verifies.

bunx @lythos/[email protected] add-skill <skill-name>

Step 1 (CLI): Creates packages/<skill-name>/skill/SKILL.md template. Step 2 (agent): Edit SKILL.md — fill description, when_to_use, body, gotchas. → After editing, run bunx @lythos/skill-coach to validate against 12-dimension quality rubric. → Fix issues coach flags, then proceed to Step 3. Step 3 (verify): Run cortex probe to confirm no empty-shell template.

Two skill types, decided upfront:

Type	Has CLI?	Has package.json?	npm publish?	Example
Skill + CLI	✅ bin field	✅ required	✅ to npm	deck, arena, curator, cortex
Pure skill	❌ no CLI	❌ none needed	❌ skip	scribe, onboarding, coach, journalist

Skill + CLI: add-skill creates packages/<name>/ with package.json + src/cli.ts + skill/SKILL.md. Add to scripts/publish.sh PACKAGES array.
Pure skill: Create packages/<name>/skill/SKILL.md directly. No package.json, no CLI, no npm. Distribution via cold pool (git clone / localhost). The pre-commit build hook auto-creates skills/<name>/ output.

After creation: run bunx @lythos/skill-creator build <name> to build the skill output, then git add skills/<name>/.

build

Build a skill for distribution. Copies packages/<name>/skill/ to skills/<name>/, strips dev-only files, validates SKILL.md frontmatter, and enforces the unified version.

bunx @lythos/[email protected] build <skill-name>

Version placeholder rule: Source packages/<name>/skill/SKILL.md must use version: 0.17.3. The build command substitutes this with the current root package.json version. Never write a literal version (e.g., version: 0.15.5) in source — this breaks future version bumps. If you find a hardcoded version in source, restore the placeholder and rebuild.

Build all skills at once (used by pre-commit):

bunx @lythos/[email protected] build --all

align

Audit an existing project against current lythoskill conventions. Reports drift between your project and the latest scaffolding standards.

# Audit only — reports what would change
bunx @lythos/[email protected] align

# Auto-fix drift where possible
bunx @lythos/[email protected] align --fix

Checks for: outdated package.json scripts, stale .gitignore patterns, missing skill-layer boilerplate, and version mismatches.

bump

Lock-step version bump for the entire monorepo. Updates root package.json + every packages/*/package.json to the same version (per project_lockstep_versioning policy). Used before npm publish runs.

# Semver targets
bunx @lythos/[email protected] bump patch
bunx @lythos/[email protected] bump minor
bunx @lythos/[email protected] bump major

# Explicit version (e.g. for major milestones)
bunx @lythos/[email protected] bump 1.0.0

# Preview the bump without writing files
bunx @lythos/[email protected] bump 1.0.0 --dry-run

Run from the project root. Expects source at packages/<name>/skill/ and outputs to skills/<name>/.

What ships with it: 5 files

9.8 KB alongside SKILL.md, 2 of them executable

references/

scripts/

build.shruns47 B
init.shruns46 B

Gives 0 of the 12 instructions most project setup skills give

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Scaffold a new monorepo
Add a new skill
Build a skill for distribution
Audit an existing project
Bump the version lock-step

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.