scrape

Other Community v1.0.0

Skill notes

When to invoke this skill

First call on a new intent prototypes the flow via $B primitives and returns JSON. Subsequent calls on a matching intent route to a codified browser-skill and return in ~200ms. Read-only — for mutating flows (form fills, clicks, submissions), use /automate. Use when asked to "scrape", "get data from", "pull", "extract from", or

First-run guidance (one-time)

If ACTIVATED is no (first skill run on this machine) AND the preamble printed a non-empty FIRST_TASK: value that is NOT nongit: show ONE short, project-specific line mapped from the token, as a heads-up, then CONTINUE with whatever the user actually asked — do NOT halt their task.

Voice

Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.

Completion Status Protocol

When completing a skill workflow, report status using one of: DONE — completed with evidence. DONE_WITH_CONCERNS — completed, but list concerns. BLOCKED — cannot proceed; state blocker and what was tried. NEEDS_CONTEXT — missing info; state exactly what is needed.

Operational Self-Improvement

Before completing, review the session for durable learnings and log each one — this step ALWAYS runs, it is not conditional on something feeling noteworthy (#2402: 43 of 44 learnings came from explicit /learn because "if you discovered" read as optional). A durable learning is a project quirk, command fix, pitfall, or pattern that would save 5+ minutes in a future session. If

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v1.0.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Determine intent

The user's request after `/scrape` is the intent. If they did not include one, ask once: "What do you want to scrape? Describe it in one line, e.g. 'top stories on Hacker News' or 'product names + prices on example.com/products'." Do not ask multiple clarifying questions up front. Any further questions

02
Step 2 — Refuse mutating intents

If the intent implies writes — verbs like *submit*, *post*, *send*, *log in*, *click X*, *fill the form*, *delete*, *create*, *order*, *book* — respond: "/scrape is read-only. For mutating flows, use /automate (browser-skills Phase 2 P0 in TODOS.md — not yet shipped). Until then, use $B click /

03
Step 3 — Match phase

List existing browser-skills: For each skill, `$B skill show <name>` exposes the full SKILL.md including `triggers:`, `description:`, and `host:`. Read these and judge whether the user's intent semantically matches one of them. A confident match means all three are true:

04
Step 4 — Prototype phase

No match. Drive the page using `$B` primitives: `$B goto <url>` — navigate to the target. The user's intent usually names a host or a URL; use it directly. `$B snapshot --text` (or `$B text`) — get a clean text view of the page to find selectors.

05
Step 5 — Skillify nudge

After a successful prototype, append exactly one line: "Say /skillify to make this a permanent skill (200ms on next call)." That is the entire nudge. Do not nag, do not list pros, do not push. Proactive surfacing is a Phase 3 knob (`gstack-config browser_skillify_prompts`), not this skill's job.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.