Framer Skills + External Agents: Why Templates Just Got More Powerful

Framer has shipped two updates in the same week that are more connected than they first appear.

Skills let a project teach the Agent how its design system, CMS and repeated workflows should work.

External Agents let tools like Grok Bot, Codex, ChatGPT and Claude work with that project from outside Framer.

Together, they change something important:

A Framer project can now carry more of its own operating logic.

For template creators, that could make the template itself much more valuable.

Skills can preserve the design system

The interesting part of Framer Skills is not another slash command.

A Skill can reference the actual components, text styles, colors, spacing and pages inside a project. It can then tell the Agent how those pieces should be used when creating or modifying something.

Framer’s own /design-system example shows exactly that: reuse the existing typography, colors, layouts and components instead of inventing a new system every time.

For a normal website, that means more consistent Agent output.

For a template, it means something bigger.

Framer says Skills stay inside the project when somebody remixes it. A template can therefore include instructions for how new pages should be built after the buyer takes ownership.

That turns the template from a collection of finished screens into a system that can explain how it should be extended.

This fixes one of the biggest template problems

A good template usually looks strongest on day one.

Then the buyer starts changing it.

They create another page. Duplicate a section. Add CMS content. Change the spacing. Create a second button style because they did not notice the first component.

Slowly, the original system starts disappearing.

Skills create a way to preserve some of the creator’s decisions inside the project itself.

A template could tell the Agent:

• which components should be reused
• which text styles belong to which hierarchy
• how sections should be spaced
• how new CMS content should be structured
• which visual patterns should never be introduced
• how pages should behave across breakpoints

The buyer still controls the result.

The Agent simply starts with better context.

External Agents handle the repeatable work around the site

Framer’s new Grok Bot examples show the other side of this.

Instead of asking an Agent to design another page, Framer is using focused external-agent workflows for operational work.

Their examples include:

• updating marketplace numbers
• preparing customer-story CMS drafts
• checking pages for SEO and AEO issues
• monitoring active A/B tests

Each workflow has one clear job, and Framer’s team reviews what it produces before anything goes live.

That is the part I find most useful.

The best agent workflow is often not:

“Build my whole website.”

It is:

“Do this one repeated job reliably.”

We are already using this approach on Northbrook

We recently started applying the same idea to Northbrook, our VC and private equity Framer template.

Using Codex as an External Agent, we connected directly to the Framer project and audited the actual system instead of reviewing screenshots.

The audit inspected:

• pages and breakpoints
• components and styles
• Portfolio and Insights CMS
• metadata
• responsive behavior
• accessibility
• links and forms
• content bindings
• performance

It found issues that are easy to miss visually.

For example, different portfolio companies were sharing one hardcoded investment narrative.

We moved that content into proper CMS fields and bound the portfolio template to the active company record instead.

That is the kind of work I want agents doing.

Not replacing the creative direction.

Strengthening the system underneath it.

What premium Framer templates can become

Page count is still useful.

CMS collections still matter.

Responsive quality still matters.

But I think the next generation of premium Framer templates can include another layer:

the rules for how the website should continue evolving.

A strong template could ship with:

• a clear component system
• structured CMS
• responsive rules
• project-specific Skills
• launch and accessibility checks
• SEO guidance
• instructions for adding new pages
• guardrails for External Agents

The value becomes less about how many demo pages are included and more about how well the system holds together after purchase.

That is a much more interesting direction for templates.

And it is exactly where we are taking the Pacts Studio catalog.