agentleFS
oscal-compass-laboscal-compass-lab/compliance-trestle-skills/.cursor/skills/workspace-validate/SKILL.md

workspace-validate

Skill16 starsChanged 3 months agoApache-2.0View on GitHub

Validate the current Compliance Trestle workspace with trestle validate, report failures clearly, and recommend fixes using the validation assistant workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run Compliance Trestle validation from Cursor.

    line 9
  2. Distinctive:

    If Trestle is missing, write a skipped or missing-tool status.

    line 40
  3. Distinctive:

    Do not imply success when the tool is missing.

    line 41
  4. Distinctive:

    After successful assembly, import, merge, create, or split operations, run validation before you report the workspace as ready.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workspace Validate

Run Compliance Trestle validation from Cursor.

Read first

  • commands/workspace/validate.md
  • agents/validation-assistant.md
  • skills/trestle-validation/SKILL.md

Run

From the workspace root that contains .trestle/:

trestle validate -a

Or use the repository wrapper for consistent reports:

bash scripts/trestle-workflow.sh validate <workspace>

For one model:

trestle validate -t <type> -n <name>

Output

  • Capture validation output in reports/ when you work inside an import workspace.
  • If Trestle is missing, write a skipped or missing-tool status.
  • Do not imply success when the tool is missing.
  • Explain schema, reference, and markdown-authoring failures separately when possible.

Follow-up

After successful assembly, import, merge, create, or split operations, run validation before you report the workspace as ready.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.