agentleFS
mrieckmrieck/snipkiwi-design-extract/.claude/skills/test-compare/SKILL.md

test-compare

Skill1 starsChanged 37 days agoMITView on GitHub

Compare CSS extraction results between two runs or two selectors on the same page, to verify consistency and correctness

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run extraction on one or two selectors and compare/analyze the results.

    line 11
  2. Distinctive:

    If only URL and one selector provided:

    line 15
  3. Distinctive:

    Run extraction twice on the same URL + selector

    line 17
  4. Distinctive:

    If differences found, show exactly what differs

    line 20
  5. Distinctive:

    If URL and two selectors provided:

    line 24
  6. Very specific:

    Run extraction on selector1, save to /tmp/snipkiwi-test-1.json

    line 26

≈ “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

Compare Extraction Results

Run extraction on one or two selectors and compare/analyze the results.

Mode 1: Single selector stability test (2 args)

If only URL and one selector provided:

  1. Build: npx tsc
  2. Run extraction twice on the same URL + selector
  3. Compare the two JSON outputs
  4. Report whether results are deterministic (identical CSS, HTML, Tailwind)
  5. If differences found, show exactly what differs

Mode 2: Two selector comparison (3 args)

If URL and two selectors provided:

  1. Build: npx tsc
  2. Run extraction on selector1, save to /tmp/snipkiwi-test-1.json
  3. Run extraction on selector2, save to /tmp/snipkiwi-test-2.json
  4. Compare:
    • How many CSS rules each produced
    • Whether they share any CSS rules
    • Tailwind class overlap
    • HTML structure differences

Commands

# Run extraction and capture JSON
node dist/index.js --url "$URL" --selector "$SEL" --format json 2>/dev/null

Output

Present results as a clear comparison table with pass/fail indicators. Clean up temp files when done.

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.