From browser-data-capture
Produce or update a versioned "domain map" document for a single host — a curated, human-readable summary of what's been learned about a target across one or many capture runs. Aggregates endpoints, auth scheme, pagination style, rate-limit signals, ToS notes, and integration notes the user has added by hand. Writes to the user's private maps repo (if registered via init-private-repo) or to the plugin data directory otherwise. Use when the user says "make a map for example.com", "update the example.com map with this capture", "give me a clean summary of what we've learned about this site".
npx claudepluginhub danielrosehill/claude-code-plugins --plugin browser-data-captureThis skill uses the workspace's default tool permissions.
Aggregate captures into a single, version-controllable document per target domain.
Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.
Share bugs, ideas, or general feedback.
Aggregate captures into a single, version-controllable document per target domain.
Resolve in this order:
config.json has a private_maps_repo_path set, write into <private_maps_repo_path>/maps/<domain>/.${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/browser-data-capture/data/maps/<domain>/.Tell the user which root was used. Encourage routing through a private repo (via init-private-repo) if they haven't already — domain maps benefit from version control and a visible history of changes.
example.com).Inside <root>/maps/<domain>/:
README.md — the canonical map. Sections:
schemas/ subfolder for per-endpoint JSON Schemas.Retry-After, X-RateLimit-*, observed 429s.endpoints.json — merged inventory across runs.schemas/ — merged JSON Schemas.openapi.yaml — most-recent generated spec, if generate-openapi has been run.captures/ — symlinks (or, in the private-repo case, references) to the source capture runs that fed the map.<root> per the rules above.<root>/maps/<domain>/ exists, load existing endpoints.json and merge new captures into it. Otherwise create fresh.(method, host, path-template) → union the query params, sample values, status codes, header observations. Re-infer schema from the union of body samples.README.md from the merged inventory + the user's hand-written sections (ToS, integration notes, target description). Preserve hand-written content — never overwrite the user's prose; only refresh the auto-generated tables.The map is built from already-redacted endpoints.json files. Do not re-introduce raw secrets. If a hand-written note in README.md contains something that looks like a credential, flag it and ask before committing.