agentleFS
Sign inStart free
wollemiahqwollemiahq/cavuno-mcp/skills/publish-blog/SKILL.md

publish-blog

Skill2 starsChanged 28 days agoMITView on GitHub

Draft, update and publish Cavuno job board blog posts, and manage authors and tags, through the Cavuno MCP server. Use when the user wants content, SEO articles or blog publishing on their Cavuno board.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Call search to find the blog post, author and tag operations and their request schemas.

    line 17
  2. Distinctive:

    Run each operation with whichever tools you have:

    line 19
  3. Very specific:

    If an execute tool is available, call cavuno.request({ method, path, body?, query?

    line 20
  4. Distinctive:

    Create or update the post as a draft first, with the title, slug, body, tags and SEO fields the API supports.

    line 29
  5. Distinctive:

    After a write, read the post again to confirm its state, then return the public URL or slug.

    line 33
  6. Distinctive:

    Never invent post, author or tag IDs.

    line 39
  7. Distinctive:

    Do not fabricate statistics or citations.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 3 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

Publish Cavuno blog content

Prerequisites

  • Cavuno MCP connected, either at https://mcp.cavuno.com/mcp or at https://mcp.cavuno.com/mcp/connector.
  • Know the target topic, audience, and whether the post should stay a draft or go live.

Calling the API

  1. Call search to find the blog post, author and tag operations and their request schemas.
  2. Run each operation with whichever tools you have:
    • If an execute tool is available, call cavuno.request({ method, path, body?, query? }) inside it.
    • Otherwise use read for GET requests, query for the read-only search operations (such as /jobs/search and /companies/search), create for POST, update for PUT and PATCH, and delete for DELETE.

Workflow

  1. Reuse an existing author when possible; create one only if needed.
  2. Create or update the post as a draft first, with the title, slug, body, tags and SEO fields the API supports.
  3. Show the user a short preview (title, slug, summary) and ask before publishing unless they already said to publish.
  4. After a write, read the post again to confirm its state, then return the public URL or slug.

Safety and quality

  • Confirm before deleting or unpublishing a post.
  • Never invent post, author or tag IDs; look them up first.
  • Match the board's niche and tone, and aim for one clear primary keyword.
  • Link to relevant jobs or category pages when the API allows it.
  • Do not fabricate statistics or citations.

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.

Check your setup, free