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

test-extract

Skill1 starsChanged 37 days agoMITView on GitHub

Run a live CSS extraction test against a URL and selector, verify output contains HTML, CSS, and Tailwind classes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Hakkadaikon/hymme★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 a full extraction test against a live URL with a CSS selector.

    line 11
  2. Distinctive:

    If build fails, report errors and stop

    line 16
  3. Distinctive:

    No error messages in the output

    line 23
  4. Distinctive:

    If no URL/selector given, use these defaults:

    line 33
  5. Very specific:

    If the page times out, report and suggest increasing --timeout

    line 39
  6. Distinctive:

    If selector not found, report the error clearly

    line 40
  7. Distinctive:

    If build fails, show the TypeScript errors

    line 41

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

Test CSS Extraction

Run a full extraction test against a live URL with a CSS selector.

Steps

  1. Build the project first: npx tsc
  2. If build fails, report errors and stop
  3. Run extraction: node dist/index.js --url "$0" --selector "$1" --format json --timeout 30000
  4. Redirect stderr to /dev/null to get clean JSON output
  5. Parse the JSON output and verify:
    • html field exists and is non-empty
    • css field exists and contains CSS rules (look for { and })
    • tailwindHtml field exists and contains class=" attributes
    • No error messages in the output
  6. Report a summary:
    • Number of CSS rules extracted (count { in css field)
    • Whether Tailwind classes were generated
    • Sample of first 3 Tailwind classes found
    • HTML element count
    • Any fonts or CSS variables detected

Default test if no arguments provided

If no URL/selector given, use these defaults:

  • URL: https://example.com
  • Selector: body

Error handling

  • If the page times out, report and suggest increasing --timeout
  • If selector not found, report the error clearly
  • If build fails, show the TypeScript errors

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.