New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Manage Microfeed Content

by microfeed in microfeed/microfeed

Manage content on one or more microfeed sites through @microfeed/cli.

AGPL-3.0Auto-check passedBackend & APIs

Install Manage Microfeed Content

skills CLI
$ npx skills add microfeed/microfeed --skill manage-microfeed-content -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microfeed/microfeed manage-microfeed-content --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microfeed/microfeed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/manage-microfeed-content .claude/skills/manage-microfeed-content && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
manage-microfeed-content
GitHub stars
4.1k
Token cost
~2.3k tokens
SKILL.md length
1,153 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Manage content on one or more microfeed sites through @microfeed/cli.

  • Works in 3 steps: Inside a microfeed clone, use yarn… → In a project with @microfeed/cli… → Use yarn dlx @microfeed/cli only for…
  • An agent is asked to log in to a microfeed site
  • SKILL.md covers Choose the invocation, Use microfeed vocabulary…, Select and authorize a site and Operate deterministically, plus 2 more sections
  • Calls yarn and npx; needs MICROFEED_API_KEY

What it does

Manage Microfeed Content is an agent skill from microfeed/microfeed. Manage content on one or more microfeed sites through @microfeed/cli. Use when an agent is asked to log in to a microfeed site; select a saved site; list, read, create, update, or delete items; upload standalone or inline media, item cover art, or a media attachment/RSS enclosure; or call the authenticated microfeed REST API.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs, covering REST APIs. The repository describes itself as: an agentic cms self-hosted on cloudflare, for podcasts, blogs, photos, videos, documents, and curated urls. The licence is AGPL-3.0.

When your agent uses it

  • An agent is asked to log in to a microfeed site
  • Select a saved site
  • Upload standalone
  • A media attachment/RSS enclosure

Example prompts

  • “/manage-microfeed-content”

Requirements

  • Node.js
  • A credential in MICROFEED_API_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Inside a microfeed clone, use yarn microfeed after the normal
  2. In a project with @microfeed/cli installed locally, use
  3. Use yarn dlx @microfeed/cli only for intentional one-off use when a local

What it can do on your machine

Read from SKILL.md and the folder at commit bb84a81. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • yarn
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.microfeed.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • MICROFEED_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Manage Microfeed Content loads about 2.3k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 1,153 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microfeed/microfeed at commit bb84a81, republished under its AGPL-3.0 licence (© microfeed). 1,153 words, ~2,301 tokens.

Download SKILL.mdSave it as .claude/skills/manage-microfeed-content/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
manage-microfeed-content
description
Manage content on one or more microfeed sites through @microfeed/cli. Use when an agent is asked to log in to a microfeed site; select a saved site; list, read, create, update, or delete items; upload standalone or inline media, item cover art, or a media attachment/RSS enclosure; or call the authenticated microfeed REST API.

Manage microfeed content

Use the microfeed CLI so credentials, browser authorization, upload URLs, redirects, and output safety remain inside the project-owned client.

Choose the invocation

  1. Inside a microfeed clone, use yarn microfeed after the normal yarn install.
  2. In a project with @microfeed/cli installed locally, use yarn microfeed.
  3. Use yarn dlx @microfeed/cli only for intentional one-off use when a local package is unavailable.

Before using an unfamiliar command or option, run its --help. Inside a clone, read ../../../docs/microfeed-cli.md for the canonical reference. Outside a clone, use https://docs.microfeed.org/microfeed-cli/.

Use microfeed vocabulary precisely

  • Site URL: the root public URL of one microfeed site, such as https://feed.example.com. Do not include a dashboard path. Local testing may use http://127.0.0.1:<port>.
  • Instance name: a local alias for a saved site, such as production or local. It is not a username, account, browser identity, or Wrangler profile.
  • Connection name: this computer's label under Account settings → App access, such as Home Mac. It is not the local instance name. One site can show several computer connections for the same microfeed CLI application.
  • Item ID: the stable ID returned by item list, item search, or item get.
  • Item image: cover art or a thumbnail stored in the top-level image field. Use --image-file <path> for a local file or --image <url> for an already-hosted absolute URL.
  • Media attachment: the item's one main audio, video, document, image, or external link. It is JSON Feed attachments[0] and the RSS enclosure. Use --attachment-file <path> for a local file.
  • Standalone media: an uploaded file not assigned to either item field, such as an image embedded inside content_html. Use media upload <path> and read its permanent media_url.

When a user says “attach,” “media file,” or “enclosure,” default to a media attachment. When they say insert, embed, inline, description image, or rich-text image, use standalone media. Use an item image only when they say cover, artwork, thumbnail, item image, or equivalent. If their intent remains ambiguous and would change which field is written, ask before uploading.

Select and authorize a site

Start with:

console
yarn microfeed instances list --json

Use the named site the user supplied. If several saved sites exist and the target is unclear, show their instance names and site URLs and ask the user to choose. Never silently select the first one.

New microfeed instances keep API access disabled by default. Browser login may succeed while content commands still return 404. When that happens, pause and ask the site owner to sign in to the admin dashboard, open API → API Settings, and turn on Enable API access. This is a browser-only owner action. Never ask for the dashboard password, an API key, or a CLI credential. After the owner confirms access is enabled, retry the same content command; the saved browser login does not need to be recreated.

Browser OAuth also requires the site's built-in login. Cloudflare Access may protect routes, but it does not create the microfeed application session OAuth needs. If the CLI reports that OAuth authorization is unavailable, tell the owner to run npx @microfeed/cli manage auth setup, then retry login. Newer sites report this capability explicitly; follow the CLI's compatible setup guidance for older sites that do not.

When authorization is missing, run:

console
yarn microfeed login <site-url> --instance <name> \
  --connection-name <computer-name>

Tell the user that browser administrator sign-in and consent are required, then pause. The user must approve or deny access; do not click Allow for them. Never ask the user to paste a credential into chat. If the user does not choose a connection name, let the CLI use the computer hostname; do not invent an owner identity. Re-login reuses the saved connection ID and should not create a duplicate entry for that computer.

logout revokes this computer's token family and removes the local saved instance. It intentionally leaves the authorization visible as Inactive under Account settings → App access until the owner revokes it. Do not promise that logout removes the App access entry.

Show full SKILL.md (520 more words)Show less

Operate deterministically

  • Add --instance <name> when the target is not already unambiguous.
  • Add --json when an agent or program consumes the result.
  • Prefer item list --summary and item get --unwrap to avoid loading channel metadata or unrequested content. Add --fields only with the corresponding compact flag.
  • Prefer common flags for short, simple values. Prefer --input <file|-> for a complete JSON object or fields that have no flag. Do not combine --input with item flags.
  • Before a create when server-accurate validation is useful, run the same input with --validate-only. It authenticates to the target but does not write an item, upload a file, or invalidate caches.
  • Generate one UUID for each logical item creation, pass it with --idempotency-key, and reuse that exact key and payload for every retry. Never generate a new key merely because a network request is retried.
  • Add --verify to creates so the completed item is read back after any media workflow. If verification fails, report the already-created ID and inspect or retry the read; do not create another item.
  • Treat --content-html as the item's description/body.
  • Use published, unlisted, or unpublished for status.
  • Read response fields rather than scraping dashboard HTML.

Common operations:

console
yarn microfeed item list --summary --instance <name> --json
yarn microfeed item search "hello" --fields title --instance <name> --json
yarn microfeed item get <item-id> --unwrap --instance <name> --json
yarn microfeed item create --instance <name> --input item.json \
  --validate-only --json
yarn microfeed item create --instance <name> --title "Title" \
  --content-html "<p>Body</p>" --status unlisted \
  --idempotency-key <logical-create-uuid> --verify --json
yarn microfeed item update <item-id> --instance <name> \
  --status published --json

Upload files safely

For an image embedded in the description or other rich HTML:

console
yarn microfeed media upload ./diagram.png --instance <name> --json

Read only the permanent media_url, insert it into an <img src> in content_html, and create or update the item. The upload command does not edit the item. Reference the returned URL promptly so the standalone object is not left unused. Images need no item ID. For standalone audio, video, or documents, pass --item-id <item-id> as required by the REST contract.

For a main media attachment/RSS enclosure:

console
yarn microfeed item update <item-id> --instance <name> \
  --attachment-file ./episode.mp3 --json

For item cover art or a thumbnail:

console
yarn microfeed item update <item-id> --instance <name> \
  --image-file ./cover.png --json

Do not construct, follow, copy, persist, read, or print a presigned upload URL. The CLI sends file bytes without a Bearer credential and refuses cross-site upload URLs and redirects.

Creating with --attachment-file is a create-upload-update sequence because the attachment requires an item ID. If upload or update fails after creation, report the created item ID and inspect it before retrying. Reuse the original logical create's idempotency key and payload; do not create another item blindly. --verify reads the item only after the attachment update succeeds.

Protect credentials and destructive actions

  • Never request, read, print, log, copy, or expose API keys, CLI access or refresh credentials, encrypted credential files, or keychain entries.

  • Let MICROFEED_API_KEY and MICROFEED_URL remain opaque environment inputs in CI. Never persist them.

  • Before deletion, report the exact instance name, site URL, and item ID; explain that deletion is permanent; and obtain explicit approval. Then use:

    console
    yarn microfeed item delete <item-id> --instance <name> \
  --confirm <item-id> --json

  • A 404 can mean the resource is absent or API access is disabled. Follow the CLI's recovery instructions: pause for the owner to enable access under API → API Settings, then retry the same command. If access is already on, verify the resource and /api/v1/ path instead of repeatedly retrying.

For a REST operation that has no dedicated command, use yarn microfeed api with a relative /api/v1/... path. Never supply Authorization, Cookie, or Host; the CLI manages credentials and refuses redirects.

© microfeed, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/manage-microfeed-content of microfeed/microfeed.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit bb84a81

Compare with similar skills

Manage Microfeed Content next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Manage Microfeed Content compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Manage Microfeed Content this skillmicrofeed/microfeed4.1k—~2.3kAutomated safety check: PassAGPL-3.0
API DesignerJeffallan/claude-skills12k2 repos~2kAutomated safety check: PassMIT
Paperclippaperclipai/paperclip98k—~9.6kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works15817 repos~4kAutomated safety check: PassAGPL-3.0
OpenAPI to MCP Servermcp-use/mcp-use11k—~5.2kAutomated safety check: PassApache-2.0
Use Yaakmountain-loop/yaak19k—~1.9kAutomated safety check: PassMIT

Similar skills

  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed

  • Paperclip

    paperclipai/paperclip

    Interact with the Paperclip control plane API for task coordination and governance.

    98k GitHub stars~9.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 17 repos~4k tokens
    Backend & APIsAuto-check passed

  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed

  • RuView CLI, API and WASM

    ruvnet/RuView

    Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

    97k GitHub stars~1.2k tokensUpdated yesterday
    Backend & APIsAuto-check: notes

More from microfeed/microfeed

  • Develop Microfeed

    microfeed/microfeed

    Develop and contribute changes to the microfeed repository safely from branch creation through validation, commit, push, and draft pull request.

    4.1k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

  • Document Microfeed

    microfeed/microfeed

    Create, revise, organize, validate, and publish microfeed documentation.

    4.1k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

  • Export Microfeed Theme

    microfeed/microfeed

    Initialize or export a microfeed theme from a saved instance into an independent local repository, then install, validate, test, and preview it safely.

    4.1k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Deploy Microfeed

    microfeed/microfeed

    Deploy and administer microfeed through the source-code-free @microfeed/cli launcher or the project-owned yarn manage CLI.

    4.1k GitHub stars~6.6k tokensUpdated yesterday
    Auto-check passed

  • Build Microfeed Automation

    microfeed/microfeed

    Build persistent microfeed webhook receivers, integrations, and autonomous workflows.

    4.1k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Develop Microfeed Theme

    microfeed/microfeed

    Develop, revise, build, validate, test, and preview a microfeed theme repository.

    4.1k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Manage Microfeed Content

What does Manage Microfeed Content do?

Manage content on one or more microfeed sites through @microfeed/cli. Manage Microfeed Content is an agent skill from microfeed/microfeed. Manage content on one or more microfeed sites through @microfeed/cli.

When should I use Manage Microfeed Content?

Manage Microfeed Content fits situations like: an agent is asked to log in to a microfeed site; select a saved site; upload standalone; A media attachment/RSS enclosure.

How do I install Manage Microfeed Content in Claude Code?

Run `npx skills add microfeed/microfeed --skill manage-microfeed-content -a claude-code`. Or copy the skill folder (.agents/skills/manage-microfeed-content in microfeed/microfeed) into .claude/skills/manage-microfeed-content in your project. Claude Code loads it when a task matches its description.

How do I install Manage Microfeed Content in Codex?

Run `npx skills add microfeed/microfeed --skill manage-microfeed-content -a codex`. Or copy the skill folder (.agents/skills/manage-microfeed-content in microfeed/microfeed) into .agents/skills/manage-microfeed-content in your project. Codex loads it when a task matches its description.

Can I use Manage Microfeed Content in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microfeed/microfeed --skill manage-microfeed-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manage-microfeed-content, .gemini/skills/manage-microfeed-content, .github/skills/manage-microfeed-content and .opencode/skills/manage-microfeed-content in your project.

What does Manage Microfeed Content need to run?

Going by SKILL.md and its folder, Manage Microfeed Content needs the command-line tools its instructions call (yarn and npx) and credentials named MICROFEED_API_KEY. Our summary lists: Node.js; A credential in MICROFEED_API_KEY.

Does Manage Microfeed Content access the network?

SKILL.md names 1 domain. As links in the text: docs.microfeed.org. This is read from the text; nothing was executed.

Is Manage Microfeed Content safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Manage Microfeed Content use?

Manage Microfeed Content is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Manage Microfeed Content use?

About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Manage Microfeed Content?

Skills that share tags, products or a category with Manage Microfeed Content: API Designer (Jeffallan/claude-skills, 12k stars), Paperclip (paperclipai/paperclip, 98k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Manage Microfeed Content?

microfeed (a GitHub organization) maintains it in microfeed/microfeed, which has 4,109 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 6, 2026.

Source: microfeed/microfeed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.