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

Develop Microfeed Theme

by microfeed in microfeed/microfeed

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

AGPL-3.0Auto-check passed

Install Develop Microfeed Theme

skills CLI
$ npx skills add microfeed/microfeed --skill develop-microfeed-theme -a claude-code

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

GitHub CLI
$ gh skill install microfeed/microfeed develop-microfeed-theme --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/develop-microfeed-theme .claude/skills/develop-microfeed-theme && 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
develop-microfeed-theme
GitHub stars
4.1k
Token cost
~1.1k tokens
SKILL.md length
560 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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

  • Works in 8 steps: Read THEME.md, microfeed-theme.json, and… → Before changing the public shell, Page… → Inspect package scripts and source… → …
  • Editing microfeed-theme.json
  • Calls yarn
  • Declared format v1

What it does

Develop Microfeed Theme is an agent skill from microfeed/microfeed. Develop, revise, build, validate, test, and preview a microfeed theme repository. Use when editing microfeed-theme.json, declared format v1 or v2 theme files, migrating a theme to v2, public Pages, navigation, search integration, shared shell code, theme build sources, fixtures, schemas, packaged assets, or immutable theme versions.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/public-site.md`).

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

  • Editing microfeed-theme.json
  • Declared format v1
  • Migrating a theme to v2
  • Search integration

Example prompts

  • “/develop-microfeed-theme”

Workflow steps

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

  1. Read THEME.md, microfeed-theme.json, and the schemas under .microfeed/schemas/ completely before editing.
  2. Before changing the public shell, Page layout, navigation, or search, read references/public-site.md completely. Preserve its…
  3. Inspect package scripts and source directories. Run yarn install before the baseline checks when the repository has a Yarn package. Do not…
  4. If the repository has build sources, edit those sources and regenerate all declared output files; do not hand-edit generated bundles. If…
  5. Run the package build when present, then prefer the repository scripts yarn validate and yarn test. Fall back to theme-kit validate…
  6. Prefer yarn preview for visual review, falling back to theme-kit preview . only when needed. Use supplied fixtures first; use a public…
  7. Increment the manifest SemVer before installing changed content. Never reuse a published package ID and version for different content…
  8. Install as inactive. Do not activate a theme or change a live site without explicit permission.

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

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

  • Network

    No URLs in SKILL.md. Its commands use yarn, which can reach the network depending on how they are called.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Develop Microfeed Theme loads about 1.1k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 560 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.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). 560 words, ~1,096 tokens.

Download SKILL.mdSave it as .claude/skills/develop-microfeed-theme/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
develop-microfeed-theme
description
Develop, revise, build, validate, test, and preview a microfeed theme repository. Use when editing microfeed-theme.json, declared format v1 or v2 theme files, migrating a theme to v2, public Pages, navigation, search integration, shared shell code, theme build sources, fixtures, schemas, packaged assets, or immutable theme versions.

Develop a microfeed theme

  1. Read THEME.md, microfeed-theme.json, and the schemas under .microfeed/schemas/ completely before editing.
  2. Before changing the public shell, Page layout, navigation, or search, read references/public-site.md completely. Preserve its platform/theme ownership boundary and stable hooks.
  3. Inspect package scripts and source directories. Run yarn install before the baseline checks when the repository has a Yarn package. Do not rely on dependencies from a parent workspace.
  4. If the repository has build sources, edit those sources and regenerate all declared output files; do not hand-edit generated bundles. If an export contains only rendered files, edit the declared files directly. Keep all files inside the package directory and modify only declared templates, declared assets, build sources, fixtures, and documentation.
  5. Run the package build when present, then prefer the repository scripts yarn validate and yarn test. Fall back to theme-kit validate . --json and theme-kit test . --json only when those scripts are absent. Repair every diagnostic.
  6. Prefer yarn preview for visual review, falling back to theme-kit preview . only when needed. Use supplied fixtures first; use a public JSON feed only when real content is needed. Check Feed, Item, Page, Search, RSS, shared navigation, the search popup, mobile behavior, and the special 404 layout. Stop the preview server after verification.
  7. Increment the manifest SemVer before installing changed content. Never reuse a published package ID and version for different content. Package IDs beginning with microfeed. are reserved for themes bundled by the microfeed repository. Outside that official source, fork an exported bundled theme with theme init so it receives local.*, or use a distributable package ID the author controls; never mint a new microfeed.* version.
  8. Install as inactive. Do not activate a theme or change a live site without explicit permission.
Show full SKILL.md (268 more words)Show less

Bundle CSS and JavaScript

  • The installer never runs Vite, Webpack, Tailwind, or package scripts. Keep TypeScript, source CSS, bundler configuration, and node_modules in the repository; build and commit every generated runtime file before validation or installation.
  • For a small bundle that must work without R2, capture Vite or Webpack output and embed CSS in <style> inside web-header.mustache and JavaScript in <script> inside web-body-end.mustache. Keep assets: []. These generated slots are stored in the immutable D1 theme row, count toward the theme text limits, and can be edited in an Admin-derived draft. Escape any </script> sequence when generating inline JavaScript.
  • For larger or independently cacheable output, configure Vite with deterministic library-mode filenames, or Webpack with a deterministic output.filename and MiniCssExtractPlugin. Emit files such as assets/theme.css and assets/theme.js, declare every file in the manifest, and reference them as {{_theme.asset_base_url}}theme.css and {{_theme.asset_base_url}}theme.js without repeating assets/.
  • Declared asset bytes are uploaded to immutable R2 keys during installation; D1 stores their metadata and owning theme version. They require R2 on the target instance and cannot be replaced from a V1 Admin draft. The standalone preview serves the same references from its local asset handler. Never hard-code /assets/, /media/, an R2 hostname, or an environment name.
  • After changing build sources, run the package build and its deterministic/staleness check when present. Confirm generated bundles are declared, exclude source maps and other unsupported development artifacts, validate and test the rendered package, then bump SemVer.

Keep packaged assets declared in the manifest. Themes with assets need R2 enabled on the target instance; text-only and inline-bundle themes do not. Never create screenshots unless the user explicitly asks for them.

© 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 2 other files (references) in .agents/skills/develop-microfeed-theme of microfeed/microfeed.

  • SKILL.md
  • agents/openai.yaml
  • references/public-site.md

Open the folder on GitHubat commit bb84a81

Compare with similar skills

Develop Microfeed Theme 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.

Develop Microfeed Theme compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Develop Microfeed Theme this skillmicrofeed/microfeed4.1k—~1.1kAutomated safety check: PassAGPL-3.0
Theme Factoryanthropics/skills180k47 repos~781Automated safety check: PassApache-2.0
MCP Developmentcoollabsio/coolify63k1 repos~949Automated safety check: PassMIT
Theme Factorynexu-io/open-design100k—~329Automated safety check: PassApache-2.0
Game Developmentsickn33/agentic-awesome-skills47k1 repos~1.3kAutomated safety check: PassMIT
Twenty App Entity Developmenttwentyhq/twenty58k—~1.8kAutomated safety check: PassCustom licence

Similar skills

  • Theme Factory

    anthropics/skills

    Official

    Applies one of ten preset color and font themes to slide decks, documents or HTML pages, or creates a new theme on the fly after you choose from a showcase.

    180k GitHub starsUsed in 47 repos~781 tokens
    Frontend & DesignAuto-check passed

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

  • Theme Factory

    nexu-io/open-design

    Apply professional font and color themes to artifacts including slides, docs, reports, and HTML landing pages.

    100k GitHub stars~329 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Game Development

    sickn33/agentic-awesome-skills

    Game development orchestrator. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~1.3k tokens
    Game DevelopmentAuto-check passed

  • Twenty App Entity Development

    twentyhq/twenty

    Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

    58k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pierre Theme Package

    pierrecomputer/pierre

    Shows an agent how to install and use the @pierre/theme package, which ships ten Pierre light and dark color themes for Shiki and VS Code.

    6.2k GitHub stars~352 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

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 today
    Auto-check passed

  • Document Microfeed

    microfeed/microfeed

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

    4.1k GitHub stars~1.5k tokensUpdated today
    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 today
    Auto-check passed

  • Manage Microfeed Content

    microfeed/microfeed

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

    4.1k GitHub stars~2.3k tokensUpdated today
    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 today
    Auto-check passed

  • Build Microfeed Automation

    microfeed/microfeed

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

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

Questions about Develop Microfeed Theme

What does Develop Microfeed Theme do?

Develop, revise, build, validate, test, and preview a microfeed theme repository. Develop Microfeed Theme is an agent skill from microfeed/microfeed. Develop, revise, build, validate, test, and preview a microfeed theme repository.

When should I use Develop Microfeed Theme?

Develop Microfeed Theme fits situations like: editing microfeed-theme.json; declared format v1; migrating a theme to v2; search integration.

How do I install Develop Microfeed Theme in Claude Code?

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

How do I install Develop Microfeed Theme in Codex?

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

Can I use Develop Microfeed Theme 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 develop-microfeed-theme -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/develop-microfeed-theme, .gemini/skills/develop-microfeed-theme, .github/skills/develop-microfeed-theme and .opencode/skills/develop-microfeed-theme in your project.

What does Develop Microfeed Theme need to run?

Going by SKILL.md and its folder, Develop Microfeed Theme needs the command-line tools its instructions call (yarn).

Does Develop Microfeed Theme access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Develop Microfeed Theme 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 Develop Microfeed Theme use?

Develop Microfeed Theme 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 Develop Microfeed Theme use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Develop Microfeed Theme?

Skills that share tags, products or a category with Develop Microfeed Theme: Theme Factory (anthropics/skills, 180k stars), MCP Development (coollabsio/coolify, 63k stars), Theme Factory (nexu-io/open-design, 100k stars) and Game Development (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Develop Microfeed Theme?

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.