From Foldspace: Browser Extension
Help someone figure out the next step for adding a Foldspace agent via a browser extension when they cannot edit the website code. Use when the user asks where to start, is new to extension-based setup, does not have the target site's source code, or wants a guided path for a no-code integration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/foldspace-remote-plugin:foldspace-get-startedThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill as the entry point when someone wants to add a Foldspace agent to
Use this skill as the entry point when someone wants to add a Foldspace agent to a website they cannot edit, by building a browser extension. Your job is to orient them and point to exactly one next step, not to do the work here.
When you do not have the website's source code, you can still add a Foldspace AI agent by shipping a Chrome extension that injects it into the live site. You create the extension, learn one workflow at a time by watching the real site, build that action against the site's own APIs, add navigation where needed, and validate before sharing.
foldspace-get-started -> foldspace-create-extension -> foldspace-observe-flow-in-site -> foldspace-build-action -> foldspace-add-navigation (when needed) -> foldspace-verify-actions.
If the user skipped a step, route them to the earliest incomplete one.
This plugin is for websites where the user cannot edit the code and must use a browser extension. If any of these are true, they likely need the other Foldspace marketplace listing instead:
If so, respond with:
### Wrong plugin?
It sounds like you need **Foldspace: Add to Your App** from the Cursor marketplace, not this plugin.
This plugin is for adding Foldspace to a website you cannot edit, by building a browser extension.
Install that listing instead, then run its **Start here** skill.
Do not try to run in-app SDK setup steps from this plugin.
Keep these key terms in mind; explain any of them in plain language if the user is unsure:
PRODUCT_ID / AGENT_API_NAME.settings_billing) that lets the agent open the right page.Before creating or updating actions through MCP, make sure the user has a Foldspace Public API key available to this project:
.env.foldspace at the root of the project open in Cursor
with:FOLDSPACE_API_KEY=xxxxxxxx
${workspaceFolder}/.env.foldspace is the file used by this
plugin's mcp.json, so it must be in the user's open project.Missing MCP setup blocks creating or updating Foldspace actions from the agent, but it does not block scaffolding the browser extension itself. If they don't want to use the MCP they can do everything through agent studio in the foldspace website.
As you route the user, make sure they come away understanding, in plain language:
Tell the user that each skill explains the Foldspace terms it uses as it works, and that the remote flow deliberately pauses for their approval between learning a flow and writing code.
Do not scaffold, research, implement, or configure navigation in this skill. Keep routing within this plugin because selecting it already means the user is building a no-source-access extension.
.env.foldspace is configured for Foldspace MCP, if action creation or updates are needed.foldspace-create-extension.foldspace-observe-flow-in-site.foldspace-build-action.foldspace-add-navigation.foldspace-verify-actions.## Foldspace Remote Starting Point
### Assumption
You selected the browser-extension plugin, so this path assumes no target product source-code access.
### What I Need From You
- <target URL, current extension state, action candidate, DevTools evidence, schema, or approval status>
- <whether `.env.foldspace` exists with `FOLDSPACE_API_KEY` when MCP action creation/update is needed>
### Next Skill
Run `<namespaced foldspace remote skill command>` because <one-sentence reason>.
### Full Path
- <short ordered list of remaining remote skills>
Always end with:
Summary:
- Completed: identified the remote extension starting point.
- Concepts: <any Foldspace terms you introduced, e.g. browser extension, action, DevTools evidence>
- If you did this yourself: pick the earliest milestone you have not finished (create → learn → build → navigate → validate).
- Next step: <exact `/foldspace-*` skill command and concrete input>
- Blockers: <missing target URL, API key, product ID, Agent API Name, DevTools evidence, approval, or None>
npx claudepluginhub eucera/mcp-plugins --plugin foldspace-remote-pluginCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.