agentleFS
abhaylaabhayla/claude-best-practices/.claude/skills/scan-url/SKILL.md

scan-url

Skill9 starsChanged 7 months agoMITView on GitHub

Trigger an internet scan for a specific URL or topic. Detects URL vs topic mode and triggers appropriate scan workflow.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS looks like a URL (starts with http/https) → URL mode

    line 22
  2. Distinctive:

    Check that the workflow dispatched successfully:

    line 39
  3. Distinctive:

    MUST validate URL format before triggering — reject obviously malformed URLs

    line 69
  4. Very specific:

    MUST distinguish URL mode from topic mode correctly — URLs start with http:// or https://

    line 70
  5. Distinctive:

    MUST report the workflow run URL so the user can monitor progress

    line 71

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

Scan URL — Trigger Internet Pattern Scan

Scan a URL or topic for Claude Code best practices.

Input: $ARGUMENTS


STEP 1: Detect Mode

  • If $ARGUMENTS looks like a URL (starts with http/https) → URL mode
  • Otherwise → Topic mode

STEP 2: Trigger Scan

URL Mode

gh workflow run scan-internet.yml -f url="$URL"

Topic Mode

gh workflow run scan-internet.yml -f topic="$TOPIC"

STEP 3: Verify Trigger

Check that the workflow dispatched successfully:

gh run list --workflow=scan-internet.yml --limit=1
StatusAction
queued or in_progressReport success, provide run URL
Not foundVerify gh is authenticated and workflow exists: gh workflow list
ErrorReport the error message and suggest manual trigger via GitHub UI

STEP 4: Post-Scan Follow-Up

Report the trigger result:

Scan triggered:
  Mode: URL/Topic
  Input: $ARGUMENTS
  Workflow: scan-internet.yml
  Monitor: gh run watch <run-id>

Optionally ask if the URL/topic should be added to the permanent watchlist in config/urls.yml or config/topics.yml.


CRITICAL RULES

  • MUST validate URL format before triggering — reject obviously malformed URLs
  • MUST distinguish URL mode from topic mode correctly — URLs start with http:// or https://
  • MUST report the workflow run URL so the user can monitor progress

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.