agentleFS
sami2919sami2919/SignalForce/skills/validate/SKILL.md

validate

Skill9 starsChanged 3 months agoMITView on GitHub

Use when verifying config.yaml is valid after editing, when troubleshooting why scanners return no results, or after running /setup to confirm the generated config works

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use policy-init, create and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • open-coder-aiSkill

    policy-init

    Create conformant Chock policy from request. args(request, target_path,

    Also in 3 projects that use this

  • MicrosoftSkill

    create

    Also in 4 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 4 projects that use this

  • Hugging FaceSkill

    sprint

    Work on a batch of GitHub issues in parallel using Agent Teams. Creates one worktree per issue with TDD enforcement, coordinates via a lead agent, then produces stacked PRs.

    Also in 4 projects that use this

  • qtzx06Skill

    eval

    Evaluate trained YOLO model accuracy with mAP metrics and per-class error analysis. Identifies failure cases for targeted improvement. Use after training.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    board

    Read, write, and browse the AgentHub message board for agent coordination.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 5

    Distinctive

    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 each check in order. Print a summary report at the end.

    line 8
  2. Distinctive:

    Check for missing optional fields that improve accuracy:

    line 60
  3. Distinctive:

    If any ERRORs exist, end with: "Fix ERRORs before running scans." and list the specific files or commands needed.

    line 82
  4. Distinctive:

    If only WARNs exist, end with: "Config is functional.

    line 84
  5. Distinctive:

    If all checks pass, end with: "Config is valid.

    line 86

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “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

Validate

Run each check in order. Print a summary report at the end.

Check 1 — Schema validation

python -c "from scripts.config_loader import load_config; load_config()"
  • OK: config loaded without errors
  • ERROR: print the exception and stop — remaining checks are unreliable until schema errors are fixed

Check 2 — Scanner modules importable

For each scanner marked enabled: true in config/config.yaml, verify its module path imports cleanly:

python -c "import <module_path>"
  • OK: import succeeds
  • ERROR: module not found or import error — note the scanner name and error

Check 3 — Scanner has scan() function

For each enabled scanner module, verify it exposes a scan() function:

python -c "from <module_path> import scan"
  • OK: function found
  • ERROR: scan not defined in module

Check 4 — Templates exist for enabled scanners

For each enabled scanner, check that at least one matching template file exists:

  • Email template: config/templates/email-sequences/<signal-type>*.md
  • LinkedIn template: config/templates/linkedin-sequences/<signal-type>*.md
  • OK: at least one template found per channel
  • WARN: template missing for a channel — outreach for this signal type will fail at runtime

Check 5 — Keyword lists not empty

For each enabled scanner, check that its keyword list in config/config.yaml contains at least one entry.

  • OK: one or more keywords present
  • WARN: empty keyword list — scanner will run but likely return zero results

Check 6 — Optional fields present

Check for missing optional fields that improve accuracy:

  • company.website — used by prospect-researcher for domain enrichment
  • icp.disqualifiers — used to filter false positives from scanner results
  • OK: field present and non-empty
  • WARN: field missing — note which field and its purpose

Summary report

Print one line per check:

[OK]    Schema validation
[OK]    Scanner import: scripts.github_rl_scanner
[ERROR] Scanner import: scripts.arxiv_monitor — ModuleNotFoundError
[OK]    scan() function: scripts.github_rl_scanner
[WARN]  Template missing: linkedin-sequences/github*.md
[WARN]  Empty keywords: job_posting_scanner
[WARN]  Missing optional field: icp.disqualifiers

If any ERRORs exist, end with: "Fix ERRORs before running scans." and list the specific files or commands needed.

If only WARNs exist, end with: "Config is functional. Address WARNs to improve signal coverage."

If all checks pass, end with: "Config is valid. Ready to run /signal-scanner."

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.