agentleFS
Sign inStart free
kostja94kostja94/openblog/skills/setup-blog-module/SKILL.md

setup-blog-module

Skill7 starsChanged 19 days agoMITView on GitHub

Greenfield OpenBlog setup — scaffold, config, deploy env, theme, features, validate/build. Use when starting from scratch or user wants to try OpenBlog locally first. NOT the default if user has an existing product site — use integrate-product-site instead.

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only use this skill after they choose greenfield / try-first.

    line 16
  2. Very specific:

    Not sure which path?: Start with blog-cms.

    line 88
  3. Very specific:

    Existing product site?: Use integrate-product-site instead.

    line 89
  4. Very specific:

    Writing posts?: Use create-post (user provides body/brief).

    line 90
  5. Very specific:

    Pre-publish checks?: Use validate-blog-seo.

    line 91
  6. Distinctive:

    Do not use this skill for:

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Setup Blog Module

Greenfield workflow for a new OpenBlog instance. Use when the user does not have an existing product site to integrate, or explicitly wants a local demo before INTEGRATION.

Agent: confirm with the user

If unclear, ask:

Do you want to mount /blog on an existing product site (→ INTEGRATION.md), or run a local demo first (→ create-openblog)?

Only use this skill after they choose greenfield / try-first.

When to use

  • User wants a new blog from zero (standalone, subdirectory, or subdomain)
  • User needs openblog.config.ts, env, theme, or features configured
  • User asks to verify the project builds before first deploy

Steps

1. Scaffold

git clone https://github.com/kostja94/openblog.git
cd openblog
npm run create-openblog -- my-blog

Options: --dir <name>, --preset vercel-geist, --no-install. See packages/create-openblog/README.md.

2. Configure openblog.config.ts

At repo root, set:

  • site — name, description, locale, url
  • content — adapter and content dir (default templates/next/content/blog)
  • theme — preset id or custom; run theme:sync after changes
  • features — toggle categories, tags, authors, RSS (see docs/features.md in monorepo, or FEATURES.md in scaffolded projects)
  • components.optional — Blog Chrome toggles (TOC, share bar, etc.)

The flags select existing OpenBlog UI. If the user needs a new or substantially redesigned named component, use Bricks component-builder and implement the result in the target project rather than adding component guidance to this skill.

3. Deploy environment

Copy templates/next/.env.example → .env.local:

SITE_URL=https://yourdomain.com
DEPLOY_MODE=subdirectory   # subdirectory | subdomain | standalone
BLOG_BASE_PATH=/blog       # subdirectory only
# ASSET_PREFIX=/blog       # if static assets 404 behind reverse proxy

See templates/next/docs/DEPLOY-ROUTING.md for mode details.

4. Theme sync

npm run theme:sync   # writes templates/next/src/app/theme.generated.css

dev and build run theme:sync automatically. See docs/theming.md. Optional: npm run theme:infer -- --url https://… for draft palette hints.

5. Features

Edit features in openblog.config.ts to disable taxonomy/feeds the site does not need. Validation rules follow enabled flags — see docs/features.md (or FEATURES.md in scaffolded projects).

6. Validate and build

From repo root:

npm install
npm run validate:posts
npm run build
npm run dev   # → http://localhost:3000/blog

Fix any frontmatter or config errors before handing off to content skills.

Related skills

  • Not sure which path? Start with blog-cms.
  • Existing product site? Use integrate-product-site instead.
  • Writing posts? Use create-post (user provides body/brief).
  • Pre-publish checks? Use validate-blog-seo.

Out of scope

Do not use this skill for:

  • Keyword research, content calendars, or GEO strategy → use marketing-skills
  • Marketing landing pages, product homepage, or docs site
  • Site-wide SEO audit (llms.txt, homepage meta, GSC) → host site responsibility
  • Autonomous AI content generation at scale → user provides content; OpenBlog validates structure

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