Skip to content
Agentmart
Submit a tool

check-source

In an lstack learning vault (a folder containing lstack.yaml), read one source file, note, or node against the other sources and report suspected errors with…

Skill by sscw32

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sscw32-check-source

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

In an lstack learning vault (a folder containing lstack.yaml), read one source file, note, or node against the other sources and report suspected errors with confidence levels, without editing the file. Use for "/check-source", "is this chapter wrong anywhere", "check my notes for mistakes", "does this node contradict the book". Skip when the folder has no lstack.yaml, when the user wants structural lint (/lint-vault), or when the file is source code.

Use cases: documents, writing, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/check-source

What's inside

Skill name
check-source
Description
In an lstack learning vault (a folder containing lstack.yaml), read one source file, note, or node against the other sources and report suspected errors with confidence levels, without editing the file. Use for "/check-source", "is this chapter wrong anywhere", "check my notes for mistakes", "does this node contradict the book". Skip when the folder has no lstack.yaml, when the user wants structural lint (/lint-vault), or when the file is source code.
License
MIT
Instructions
41 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Check source

Find what looks wrong in one file. Report. Never edit the file.

## Preconditions

Confirm `lstack.yaml` exists in the working directory or a parent. If not, say this isn't a vault and suggest `/setup-vault`. Read `MISSION.md`, `kb/today.md`, and the newest file in `log/`. Open with one line on where the user is.

## Argument

The text after the skill name in the user's message is a file in `sources/` or `notes/`, or a node id. If there is none, ask.

## Steps

1. Read the file. Read every other file in `sources/` that covers the same topic (match by the nodes' `sources` citations and by terms). Read the related nodes' Summaries and Terms.
2. For each suspected error report, in this shape, one block per claim:
   - **Claim**: the sentence or formula, quoted.
   - **Why it looks wrong**: one or two sentences.
   - **What the other source says**: quote and cite, or "no other source covers this; from my own knowledge".
   - **Confidence**: low, medium, or high.
   Report nothing if nothing looks wrong, and say which sources you compared.
3. If the file is in `notes/`, also flag text that would make a good node addition and say `/add-source` or a node edit could take it. Do not write it here.
4. Offer to add each medium or high finding as an `## Open questions` entry on the related node. Preview per node. Wait for yes. Write. Run `node .lstack/lstack.mjs build`, then `node .lstack/lstack.mjs lint`. Report one line. If `lstack.yaml` says `node_available: false`, rebuild `kb/index.md` and `kb/today.md` by hand and say so.

## Preview format

```
### Proposed write 1 of 1: kb/vector-spaces/span.md
**Body**
+ - lecture-2.md says a spanning list is always independent; Axler 2.A gives (1,0),(0,1),(1,1) as a spanning dependent list. Which is right?
```

Reply **yes** to write, **no** to skip, or name what to change.

## Rules

- Never edit anything in `sources/`, `notes/`, or `problems/attempts/`. Never edit generated files.
- Never claim a source is wrong at high confidence from memory alone. Memory-only findings are low or medium.
- No hooks, no sub-agents, no argument substitution.

From sscw32/lstack, MIT.

More from sscw32/lstack

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 15, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from sscw32

Cite this page

check-source skill. Agent Mart. https://agentmart.dev/skills/sscw32-check-source (last updated 2026-10-24)