Consult consistency lint
Skill Timelnapp/skills/skills/consulting-os/consult-consistency-lint
Trigger on "consult lint", "consistency pass", "diagram vs narrative", "broken promises across docs", "cross-artifact check", "scope drift lint". Read-only diff across frame, arc, gates, acceptance, commercial, architecture artifact. NOT rewriting copy (use consult-package), NOT drawing diagrams (use arch-diagrams).From its SKILL.md
npx -y skills add Timelnapp/skills --skill consult-consistency-lintAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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 file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, 557 tokens by cl100k_base, as published. Nobody here has run it
Consult Consistency Lint -- Cross-Artifact Diff
Flag inconsistencies: text vs diagram, missing acceptance for a phase, duplicated/conflicting scope, option drift.
Inputs
| Input | Required |
|---|---|
Latest consult-frame, consult-arc, consult-gates, consult-acceptance, consult-commercial | yes |
Architecture artifact (Mermaid, draw.io path, image, or bullet list from arch-diagrams) | optional |
Workflow
- Phase coverage -- every phase in gates has exactly one acceptance row; flag orphans either direction.
- Option alignment -- MVP/Pilot/Full names and definitions match across arc, gates, commercial; flag renamed or missing options.
- Scope strings -- in/out scope in frame must not reappear as promised deliverables unless explicitly in acceptance; flag contradictions.
- Decision thread -- arc "thread" sentence must match frame primary decision; flag mismatch.
- Diagram vs text -- for each box/layer in the architecture artifact, map to a noun in arc or acceptance; unmapped diagram elements or unmapped promises in text get FINDING.
- Commercial vs gates -- durations/options must reference the same phased path; flag phases with no timebox or timebox with no phase.
- Placeholder scan --
TBD,TODO,unknown -- confirm,lorem, angle brackets; list file/section if known from paste titles.
Output -- exactly this shape
## Lint -- <client or "TBD"> -- <YYYY-MM-DD>
**Summary**
- Critical: <n>
- Warning: <n>
**Findings**
| ID | Severity | Where | Issue | Suggested fix |
|---|---|---|---|---|
| L1 | critical | ... | ... | ... |
**Clean checks passed**
- <bullet list of checks that passed>
Severity: critical = would embarrass in client readout or breaks contract intent; warning = clarity or internal consistency.
Rules
- Do not invent architecture elements -- if no diagram supplied, skip diagram checks and note
skipped -- no architecture artifact. - If an input artifact is missing, list as
missing -- <skill name>and skip dependent checks. - Suggested fix is one line each; no full rewrites.
Common failure modes
| Mistake | Fix |
|---|---|
| Nitpicking tone differences | Only flag semantic or commitment drift |
| Auto-resolving conflicts | Report -- let owner choose |
| Missing diagram treated as pass | Must emit skipped line |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.