Skip to the rows

agentsclimarketplace

Trellis spec bootstrap

Skill lifan-builds/context-harness/.agents/skills/trellis-spec-bootstrap

Lightweight durable context for AI coding agents: 4 files, 9 rules, companion skills, and scripts that let agents self-iterate inside your workflow.

Install

npx -y skills add lifan-builds/context-harness --skill trellis-spec-bootstrap

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 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.

What its author says it does

Copied from the file, not written here

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.

SKILL.md

2.6 KB, 478 tokens by cl100k_base, as published. Nobody here has run it

Trellis Spec Bootstrap

Use this skill to create or refresh .trellis/spec/ guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand.

Workflow

Confirm Trellis is initialized and inspect the current .trellis/spec/ tree.
Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
Decompose the spec work by package and layer only when that reflects the actual codebase.
Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
Verify that the final specs are internally consistent and contain no template placeholders.

Reference Routing

Need	Read
Repository architecture analysis	references/repository-analysis.md
Spec work decomposition and task planning	references/spec-task-planning.md
Writing high-signal Trellis spec files	references/spec-writing.md
GitNexus and ABCoder MCP setup	references/mcp-setup.md

Operating Rules

Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it.
Prefer source-backed rules over generic advice. Every important recommendation should point at a real file or repeated local pattern.
Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
Do not write platform-specific instructions unless the target project already standardizes on that platform.
Do not leave placeholder text, empty headings, or copied boilerplate in .trellis/spec/.

Done Criteria

.trellis/spec/ describes the project as it exists now.
Each relevant package or layer has practical coding guidance with real examples.
Non-applicable template sections are removed.
index.md files match the final spec file set.
Any required setup or analysis assumptions are documented in the relevant spec or task notes.

What ships with it: 4 files

9.7 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most docs writing skills give in 478 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

Announce the skill at startin 54 of 1637, across 26 files
Convert legacy doc files before editingin 45 of 1637, across 7 files
Predict questions readers might askin 42 of 1637, across 4 files
Generate clarifying questions for initial contextin 42 of 1637, across 3 files
Create document scaffold with placeholder textin 42 of 1637, across 3 files
Brainstorm content options for each sectionin 42 of 1637, across 3 files
Test the document with a fresh context-less instancein 42 of 1637, across 3 files
Include exact file paths in every taskin 42 of 1637, across 15 files
Ask interview questions one at a timein 42 of 1637, across 27 files
Apply surgical edits during refinementin 41 of 1637, across 2 files
Offer structured workflow or freeformin 40 of 1637, across 1 file
Ask for document meta-contextin 40 of 1637, across 2 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.