Framer Connector for Muse
Verify a Framer project's Server API connection.
- What
- Verify a Framer project's Server API connection.
- Cost
- Free
- Needs
- A per-project Framer API key (Site Settings > General in the Framer project — the key works for that one project only), plus the project's URL or id, kept in your Muse's secure vault (never paste secrets here). Note: this connector performs a connection check only; deeper page/CMS/deploy operations run through Framer's official npm package. Framer has a free plan.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that verifies a Framer project's Server API connection: Framer's Server API is WebSocket/SDK-only (no REST surface), so the connector performs the official handshake from the `framer-api` npm package as a connection check — a successful check proves the API key and project pair work. Honest note: deeper operations (pages, CMS, deploys) run through the official npm package, not this CLI, and are intentionally out of scope; the key is bound to one project only. Framer has a free plan. Draft: the handshake transport is pinned from the official package source; the client has not been run against Framer's servers yet — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A per-project Framer API key (Site Settings > General in the Framer project — the key works for that one project only), plus the project's URL or id, kept in your Muse's secure vault (never paste secrets here). Note: this connector performs a connection check only; deeper page/CMS/deploy operations run through Framer's official npm package. Framer has a free plan. No GitHub account needed unless listed here. Install "Framer Connector for Muse" for me. A Muse agent skill that verifies a Framer project's Server API connection via the official WebSocket handshake. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/framer 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "framer". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Framer API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.