Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →frontman-ai/frontman-agent-usage
Use this skill when an agent needs to explain or operate Frontman's browser-aware frontend coding workflow.
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 12 more in the full report
8 fixed13 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What backend and build-time information does Frontman collect from the server development environment to map live UI components back to code?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies framework routes as part of server context. | Missed | Passed |
| Identifies build state as part of server context. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to explain Frontman editing workflows for existing WordPress and framework sites.
Frontman combines the live page with CMS or source context to make targeted website changes.
WordPress requires WordPress 6.0+, PHP 7.4+, and administrator access (manage_options).
Framework setup requires a supported development environment and permitted workspace access.
Both paths require Frontman sign-in, service access, and a supported AI-provider connection.
Provider costs are separate: https://frontman.sh/pricing/ and https://frontman.sh/docs/api-keys/.
For WordPress, use staging and keep backups. Writes persist to the connected installation. Published content on a live site can change immediately. Preview is not a universal approval gate. Only some mutation tools require confirmation. Recovery is selective, with no universal undo. See https://frontman.sh/docs/integrations/wordpress/.
For frameworks, developers review source changes, run tests, and deploy through their normal workflow. Frontman does not automatically deploy framework changes. Verify production guards and deployed routes.
Public documentation requires no sign-in or provider key. On https://frontman.sh/ and https://frontman.sh/frameworks/, supported browsers can expose optional WebMCP tools. These website tools do not edit a connected site.
search_frontman searches documentation only and returns bounded excerpts with source URLs.how_to_install reads WordPress setup on the homepage or the selected stack on the frameworks page.list_features reads the current page capabilities.ask_question sends a support question only after user approval. A queued response does not confirm delivery. No replies are available.test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.