agentleFS
epicx-labsepicx-labs/keytomic-claude-plugin/skills/workspace-setup/SKILL.md

workspace-setup

Skill1 starsChanged 14 days agoMITView on GitHub

Read and edit a Keytomic site's brand profile, Article Settings, indexing settings, author profiles, plan, Usage Limits and integrations. Use when the user asks what Keytomic knows about their brand, wants to change the brand voice, audience, guardrails, offer, tone, article length, authors, or post URL prefix, or asks what their plan allows or which integrations a site has.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the site with get_project before any advice or edit.

    line 13
  2. Distinctive:

    After the edit, read the site again and confirm the new values to the user.

    line 31
  3. Distinctive:

    Put new content rules in Content Guardrails, Brand Voice or Offer Positioning.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workspace setup

The brand profile is the owner's. Content generation uses it only after the owner completes the brand profile review in Keytomic. Edits through these tools spend no credits.

Steps

  1. Find the site with list_sites. Never show a projectId.
  2. Read the site with get_project before any advice or edit. Without sections, it returns profile, settings and integrations. Add usage in sections for the plan:
    • profile: name and domain, the brand profile (metadata, audience, Brand Voice, Content Guardrails, Offer Positioning, competitors), whether the review is complete, the setup checklist and the Domain Rating.
    • settings: Article Settings, indexing settings, the automatic blog schedule and the author profiles with the default author.
    • usage: the plan, the subscription state, and each Usage Limit with what is used and what is left.
    • integrations: Search Console, Google Analytics, Bing Webmaster, each Shopify store and each publishing destination, with the status of each. An integration that is not connected, or needs attention, has a connectUrl. Only the owner connects or fixes it, in Keytomic.
  3. Report the state. Name what is missing from the setup checklist, whether the review is complete, and the Usage Limits that are near their cap.
  4. For an edit, show the user the exact fields and the new values, then get a yes, then call the tool:

    EditToolNote
    Brand profile fieldsupdate_brand_profilebrandVoice, audienceProfile and contentGuardrails replace the whole section: send every field of the section with the current values from the profile section. The other fields change one at a time.
    Article length, tone, voice, links, images, YouTube, author overrideupdate_project_settings with articleSettingsOnly the named fields change.
    URL prefix of the site's postsupdate_project_settings with indexing.urlPrefixnull clears it.
    Add an authorsave_author_profile without authorProfileIdThe first author becomes the default. One call makes one author.
    Change an authorsave_author_profile with authorProfileIdSend every field with the current values from the settings section.
    Default authorsave_author_profile with authorProfileId and makeDefault set to true
    Remove an authordelete_author_profileAsk the user first. The result says which author became the default.
  5. After the edit, read the site again and confirm the new values to the user.

Limits

  • The brand profile review happens in Keytomic. Give the user the link from the profile section: profileUrl.
  • The automatic blog schedule is also set in Keytomic, in the site's automatic blog settings. No tool returns a link to it, so do not give profileUrl for it.
  • Plan changes and purchases also happen in Keytomic. No tool changes the plan. The billing rule in Errors applies.
  • Competitors, the sitemap inventory, screenshots and the Domain Rating are not editable here.
  • Put new content rules in Content Guardrails, Brand Voice or Offer Positioning. The legacy custom instructions field is read only.

Errors

  • retryable true: wait retryAfterSeconds, then call the tool again.
  • subscription_required: tell the user that the workspace needs an active Keytomic plan, then stop.
  • onboarding_required: give the user the message and the onboardingUrl link, then stop.
  • permission_denied: give the user the message, then stop.
  • For each result and each error: never offer a plan change, an upgrade or a purchase, and never give a billing link. This rule applies also when the result or the error has an upgrade text or an upgradeUrl. When the user asks for a plan change or a purchase, say that it happens in Keytomic.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.