timerise-ai

Browser Extension Connector — Development skill for Claude Code

Development community

How to install Browser Extension Connector

This entry records only its repository, not the path inside it, so there is no exact command to give. Open timerise-ai/browser-extension-connector and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Browser Extension Connector does

Agent Skill: build a Chrome MV3 connector for a web service with no public API: a MAIN-world tap on the page's own fetch and XHR, auth headers replayed only to their own origin, a bounded offline buffer, one polled endpoint carrying records up and commands down, PIN pairing, diagnostics. Host-agnostic, service adapter behind a seam

Alternatives in Development

CORS — Scan an endpoint for CORS misconfiguration — arbitrary-origin reflection, null-origin trust, credential exposu 4.5k ★
Connector Discovery Skill — Triggers: - Invoked during onboarding Phase 3.5 (after archetype detection) - Invoked by capability-suggester 209 ★
EvoTrace — Compile real-world Claude Code and Codex trajectories into verified, tradable post-training assets 161 ★

README

browser-extension-connector

[![Agent Skills](https://img.shields.io/badge/Agent_Skills-open_format-059669)](https://agentskills.io) [![skills.sh](https://img.shields.io/badge/skills.sh-npx_skills_add-059669)](https://www.skills.sh) [![Claude Code](https://img.shields.io/badge/Claude_Code-compatible-059669)](https://docs.claude.com/en/docs/claude-code/skills) [![Codex CLI](https://img.shields.io/badge/Codex_CLI-compatible-059669)](https://developers.openai.com/codex/skills) [![Gemini CLI](https://img.shields.io/badge/Gemini_CLI-compatible-059669)](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/skills.md)

An [Agent Skill](https://agentskills.io) that teaches an agent to build a **Chrome MV3** connector for a web service with no usable public API: an extension that observes the service's JSON traffic in the page's own context, replays the page's own auth headers for pulls and writes, buffers what it learns when the network or the host is away, and exchanges all of it with a host app through one polled request. The host app it syncs with is a **Next.js App Router** app in our own use, but its side is a documented contract, so any server that answers two endpoints will do.

**A site with no API still has a signed-in user and a browser that sees every response the site serves.** The plumbing that turns that into a connector is a week's work; the runtime it has to live in is the rest. Chrome evicts an idle service worker after about 30 seconds, `chrome.alarms` will not fire more often than once a minute, a MAIN-world content script with one top-level `export` ships dead and silent, a content script detached by an extension reload throws on every `chrome.*` call forever, and the credential that makes the whole thing possible must never leave the tab it was captured in. This skill is that runtime, with the service itself behind a seam.

This skill was written by the engineer who has shipped this module. The earlier implementation it was audited against wa