Agent skill

Astro Sites Manager

by fabricioctelles in fabricioctelles/skills

Comprehensive skill for building, migrating, and maintaining Astro v7 projects.

Apache-2.0Auto-check passedFrontend & Design

Install Astro Sites Manager

skills CLI
$ npx skills add fabricioctelles/skills --skill astro-sites-manager -a claude-code

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

GitHub CLI
$ gh skill install fabricioctelles/skills astro-sites-manager --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/fabricioctelles/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/astro-sites-manager .claude/skills/astro-sites-manager && 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
astro-sites-manager
GitHub stars
106
Token cost
~2.4k tokens
SKILL.md length
570 words
Files
13 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Comprehensive skill for building, migrating, and maintaining Astro v7 projects.

  • The user mentions Astro
  • SKILL.md covers MCP Documentation Access, Best Practices, CLI Commands and Project Structure, plus 4 more sections
  • Calls npx, curl and python
  • Islands architecture

What it does

Astro Sites Manager is an agent skill from fabricioctelles/skills. Comprehensive skill for building, migrating, and maintaining Astro v7 projects. Covers best practices from the official AGENTS.md, the v6→v7 migration path, validation of breaking/deprecated patterns, AI-enhanced dev server usage (background mode, JSON logging), advanced routing with src/fetch.ts, route caching, Sätteri Markdown, and the Rust compiler. Use when the user mentions 'Astro', '.astro files', 'astro dev', 'astro build', 'islands architecture', 'content collections', 'SSG', 'SSR adapter', 'upgrade to…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `references/ai-dev-server.md`, `references/coolify-deploy.md` and `references/deployment.md`).

It sits in Frontend & Design, covering Static sites and blogs. It works with Astro, Vite, Hono and Rust. The repository describes itself as: A collection of skills for AI agents (Kiro, Cursor, Windsurf, Claude Code, and others). Each skill is a reusable module that teaches the agent to perform complex tasks with… The licence is Apache-2.0.

When your agent uses it

  • The user mentions Astro
  • Islands architecture
  • Content collections
  • Upgrade to Astro 7

Example prompts

  • “.astro files”
  • “astro dev”
  • “astro build”
  • “/astro-sites-manager”

Requirements

  • Python 3
  • Node.js
  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit f1de632. 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:

    • npx
    • curl
    • python

    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.astro.build

    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

Astro Sites Manager loads about 2.4k tokens when it runs, and up to ~34k if it reads all its reference files. Until then it costs about 230 tokens; SKILL.md has 570 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~230
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~34k

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 fabricioctelles/skills at commit f1de632, republished under its Apache-2.0 licence (© fabricioctelles). 570 words, ~2,376 tokens.

Download SKILL.mdSave it as .claude/skills/astro-sites-manager/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
astro-sites-manager
description
Comprehensive skill for building, migrating, and maintaining Astro v7 projects. Covers best practices from the official AGENTS.md, the v6→v7 migration path, validation of breaking/deprecated patterns, AI-enhanced dev server usage (background mode, JSON logging), advanced routing with src/fetch.ts, route caching, Sätteri Markdown, and the Rust compiler. Use when the user mentions 'Astro', '.astro files', 'astro dev', 'astro build', 'islands architecture', 'content collections', 'SSG', 'SSR adapter', 'upgrade to Astro 7', 'migrate Astro', 'Astro v7', 'Astro v6', 'Sätteri', 'route caching', 'Astro.cache', 'astro dev --background', 'src/fetch.ts', 'advanced routing', 'Hono + Astro', 'Rolldown', 'Vite 8', 'queued rendering', 'CDN cache provider', 'Astro AI', 'related content', 'related posts', 'vector embeddings Astro', 'astro-related-content', or asks about static site generation with Astro.
metadata.author
ft.ia.br
metadata.version
1.0.0
metadata.date
2026-06-22
metadata.repository
https://github.com/fabricioctelles/skills
metadata.license
Apache-2.0
metadata.category
ci-cd-and-deployment

Astro Framework — v7

MCP Documentation Access

This skill works alongside the Astro Docs MCP server. Before answering Astro questions, check if the astro-docs MCP tool is available and query it for the latest documentation. The MCP server provides real-time access to docs.astro.build and is the single source of truth for current APIs.

MCP Server: astro-docs
Tool: search_astro_docs

If the MCP server is unavailable, fall back to the reference material in this skill and https://docs.astro.build.


Best Practices

Component Design
  • One .astro component per file. Keep components small and focused.
  • Use frontmatter (---) for data fetching and logic; template below for markup only.
  • Prefer Astro components over framework components unless client interactivity is needed.
  • Use client:* directives sparingly — each adds JavaScript to the bundle.
  • Directive hierarchy: client:idle > client:visible > client:load (prefer lazy).
Routing & Pages
  • Use file-based routing in src/pages/. Dynamic routes: [slug].astro, [...path].astro.
  • Always export getStaticPaths() for prerendered dynamic routes.
  • For SSR pages: export const prerender = false at the top.
  • Use src/fetch.ts (v7) only when you need control beyond middleware — don't use it for simple auth.
Content Collections
  • Define schemas in content.config.ts with Zod — never trust untyped content.
  • Use getCollection() for lists, getEntry() for single items.
  • Prefer glob() loader for local files, custom loaders for CMS data.
Performance
  • Default to static (prerender = true). Use SSR only for personalized/dynamic content.
  • Use <Image /> from astro:assets — never raw <img> for local images.
  • Prefer Sätteri (default v7) over unified for Markdown — it's significantly faster.
  • Use Server Islands (server:defer) for mixing static shells with dynamic fragments.
Styling
  • Scoped <style> in .astro files is default and preferred.
  • Use is:global only when truly needed (third-party component styling).
  • Tailwind: install with astro add tailwind, don't configure manually.
TypeScript
  • Run astro sync after changing content schemas or env variables.
  • Run astro check before committing — catches template type errors other tools miss.
  • Use astro:env/server and astro:env/client for typed env variables (never process.env directly).
Development Workflow
  • Use astro dev for HMR. Never use python -m http.server or other static servers.
  • Use astro add for official integrations — don't manually edit config for them.
  • Use astro build && astro preview to test production behavior locally.
  • In AI agent workflows: use astro dev --background and validate via /_astro/status.

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

CLI Commands

bash
npx astro dev              # Dev server (foreground)
npx astro dev --background # Dev server (detached, for AI agents)
npx astro dev --json       # Dev server with JSON structured logs
npx astro build            # Production build
npx astro preview          # Serve production build locally
npx astro check            # Type checking and diagnostics
npx astro sync             # Generate TypeScript types
npx astro add <integration># Install and configure integration
Background Dev Server (AI Agents)

When working as an AI agent, use background mode:

bash
# Start (blocks until ready, then detaches)
astro dev --background
# → Dev server running at http://localhost:4321 (pid 12345)

# Check status
astro dev status

# Read logs
astro dev logs

# Stop
astro dev stop

# Health check endpoint (JSON)
curl http://localhost:4321/_astro/status
# → {"ok": true}

Key behaviors:

  • Lockfile prevents duplicate instances — starting again returns existing instance
  • All commands are idempotent (stop when not running = silent success)
  • Auto-detected when running inside an AI agent (no flag needed)
  • Opt out: ASTRO_DEV_BACKGROUND=0 astro dev

Project Structure

src/
├── pages/          # File-based routing (.astro, .md, .mdx)
├── layouts/        # Reusable page layouts
├── components/     # Astro & framework components
├── content/        # Content collections (type-safe)
├── middleware.ts   # Request middleware
├── fetch.ts        # Advanced routing (v7, optional)
├── styles/         # Global CSS
├── assets/         # Optimized assets (images, fonts)
├── actions/        # Server actions
└── env.d.ts        # Environment type declarations
astro.config.mjs    # Main configuration
content.config.ts   # Content collection schemas
tsconfig.json       # TypeScript config

Configuration (v7)

typescript
import { defineConfig, memoryCache, logHandlers } from 'astro/config';

export default defineConfig({
  // Output mode
  output: 'static', // or configure per-page with server adapter

  // Route caching (stable in v7)
  cache: {
    provider: memoryCache(),
  },
  routeRules: {
    '/blog/[...path]': { maxAge: 300, swr: 60 },
  },

  // Logger (stable in v7)
  logger: logHandlers.json(), // or .console(), or .compose(...)

  // Markdown (Sätteri is default in v7)
  markdown: {
    // No config needed for defaults (GFM, smartypants, heading IDs)
    // For extra features:
    // processor: satteri({ features: { directive: true, math: true } })
  },

  // Advanced routing file (default: src/fetch.ts)
  // fetchFile: null, // disable if src/fetch.ts is used for other purposes

  // Whitespace (v7 default: 'jsx')
  compressHTML: 'jsx', // or true (v6 behavior), or false (preserve all)
});

Islands Architecture (client:* directives)

astro
<!-- Load immediately (interactive above the fold) -->
<Counter client:load />

<!-- Load when browser is idle (non-critical interactivity) -->
<Newsletter client:idle />

<!-- Load when scrolled into viewport (below the fold) -->
<Comments client:visible />

<!-- Load on media query match (mobile-only widget) -->
<MobileMenu client:media="(max-width: 768px)" />

<!-- Client-only, skip SSR entirely (browser APIs needed) -->
<MapWidget client:only="react" />

<!-- Server Island: static shell, fetched at request time (v6+) -->
<UserGreeting server:defer />

Decision guide: No directive (default) = zero JS, static HTML. Add directive only when user interaction is required.


Image Optimization

astro
---
import { Image } from 'astro:assets';
import heroImage from '../assets/hero.jpg';
---
<!-- Local image (optimized, lazy-loaded, responsive) -->
<Image src={heroImage} alt="Hero" width={1200} />

<!-- Remote image (must allowlist domain in config) -->
<Image src="https://cdn.example.com/photo.jpg" alt="Photo" width={800} height={600} />

Config for remote images:

typescript
// astro.config.mjs
image: {
  domains: ['cdn.example.com'],
  remotePatterns: [{ protocol: 'https', hostname: '**.cloudinary.com' }],
}

Detailed References

  • Install MCP Server — Setup Astro Docs MCP for any AI tool (Kiro, Claude, Cursor, VS Code, etc.)
  • Migration Guide v6→v7 — Step-by-step upgrade plan with breaking changes checklist
  • Validation Checklist — Verify installation, detect breaking/deprecated patterns
  • AI Dev Server — Background mode, JSON logging, agent detection
  • Astro v7 Features — Rust compiler, Sätteri, Advanced Routing, Route Caching, CDN providers
  • Astro v6 Features — Content Collections v2, Actions, Sessions, Server Islands, env module
  • Related Content — Vector embeddings para posts relacionados, deploy leve no Coolify sem modelo
  • Testing — Vitest components, Playwright E2E, link checking, CI pipeline
  • SEO Full Stack — JSON-LD graph, agent discovery, IndexNow, OG images, build-time validation, performance
  • Starlight & Patterns — Docs sites, Pagefind search, i18n, pagination, RSS
  • Deployment — Cloudflare, Vercel, Netlify, Firebase, GitHub Pages, Docker/Coolify, Azure
  • Coolify Deploy — Self-hosted deploy on Coolify (Dockerfile, API, gotchas, recommended stack)

© fabricioctelles, Apache-2.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 12 other files (references) in skills/astro-sites-manager of fabricioctelles/skills.

  • SKILL.md
  • references/ai-dev-server.md
  • references/coolify-deploy.md
  • references/deployment.md
  • references/install-mcp.md
  • references/migration-v6-to-v7.md
  • references/related-content.md
  • references/seo-full-stack.md
  • references/starlight-and-patterns.md
  • references/testing.md
  • references/v6-features.md
  • references/v7-features.md
  • references/validation-checklist.md

Open the folder on GitHubat commit f1de632

Compare with similar skills

Astro Sites Manager 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.

Astro Sites Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Astro Sites Manager this skillfabricioctelles/skills106—~2.4kAutomated safety check: PassApache-2.0
Workflow Initusenotra/notra256—~821Automated safety check: PassAGPL-3.0
Feature Sliced Designfeature-sliced/skills109—~5.5kAutomated safety check: PassNone
Glide SetupSrivarsanK/Glide120—~868Automated safety check: PassApache-2.0
Asc Aso Rankingsn0an/VivaDicta130—~985Automated safety check: PassMIT
Lunora Quickstartanolilab/lunora284—~2.5kAutomated safety check: PassCustom licence

Similar skills

  • Workflow Init

    usenotra/notra

    Install and configure Vercel Workflow SDK before it exists in nodemodules.

    256 GitHub stars~821 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Feature Sliced Design

    feature-sliced/skills

    Official Feature-Sliced Design (FSD) v2.1 skill for applying the methodology to frontend projects.

    109 GitHub stars~5.5k tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed
  • Glide Setup

    SrivarsanK/Glide

    Zero-error setup guide for AI agents to install and configure @srivarsank/glide visual editor on any React, Vue, Svelte, Astro, or HTML Vite project in one prompt.

    120 GitHub stars~868 tokensUpdated 10 days ago
    Frontend & DesignAuto-check passed
  • Asc Aso Rankings

    n0an/VivaDicta

    Pull current keyword rankings from Astro MCP, compare against the previous rankings check, and save a new rankings file to the vault.

    130 GitHub stars~985 tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed
  • Lunora Quickstart

    anolilab/lunora

    Creates a new Lunora project or adds Lunora to an existing app, then gets the first schema + query/mutation round-trip running.

    284 GitHub stars~2.5k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Cloudflare Workers Frameworks

    secondsky/claude-skills

    Framework integration for Cloudflare Workers. An agent skill from secondsky/claude-skills.

    227 GitHub stars~1.4k tokensUpdated 13 days ago
    Frontend & DesignAuto-check passed

More from fabricioctelles/skills

All 15 skills in this repo
  • Motion Ad

    fabricioctelles/skills

    Produce a short motion-graphics video ad — a 15s Facebook/Instagram/TikTok spot — as a rendered MP4.

    106 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Agent Plugin Eval

    fabricioctelles/skills

    Audit, score, and compare repositories containing portable Agent Plugins against the official Agent Plugins specification.

    106 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Loop Architect

    fabricioctelles/skills

    Design well-structured agent loops with best-practice coaching and cross-model review gates before you run them.

    106 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes
  • Pier Cloud

    fabricioctelles/skills

    This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, workspace groups, and…

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes
  • Ralph Loop Kiro Specs

    fabricioctelles/skills

    Automated iterative agent runner for spec-based development in Kiro.

    106 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Security Specialist

    fabricioctelles/skills

    Runs security audits on codebases — full scans, diff reviews, threat models, vulnerability triage, remediation guidance, and finding tracking.

    106 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Astro Sites Manager

What does Astro Sites Manager do?

Comprehensive skill for building, migrating, and maintaining Astro v7 projects. Astro Sites Manager is an agent skill from fabricioctelles/skills. Comprehensive skill for building, migrating, and maintaining Astro v7 projects.

When should I use Astro Sites Manager?

Astro Sites Manager fits situations like: the user mentions Astro; islands architecture; content collections; upgrade to Astro 7.

How do I install Astro Sites Manager in Claude Code?

Run `npx skills add fabricioctelles/skills --skill astro-sites-manager -a claude-code`. Or copy the skill folder (skills/astro-sites-manager in fabricioctelles/skills) into .claude/skills/astro-sites-manager in your project. Claude Code loads it when a task matches its description.

How do I install Astro Sites Manager in Codex?

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

Can I use Astro Sites Manager 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 fabricioctelles/skills --skill astro-sites-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/astro-sites-manager, .gemini/skills/astro-sites-manager, .github/skills/astro-sites-manager and .opencode/skills/astro-sites-manager in your project.

What does Astro Sites Manager need to run?

Going by SKILL.md and its folder, Astro Sites Manager needs the command-line tools its instructions call (npx, curl and python). Our summary lists: Python 3; Node.js; Docker.

Does Astro Sites Manager access the network?

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

Is Astro Sites Manager 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 Astro Sites Manager use?

Astro Sites Manager is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Astro Sites Manager use?

About 2.4k tokens (SKILL.md is roughly 9.5k 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 32k tokens, read only when the agent opens those files.

What are the alternatives to Astro Sites Manager?

Skills that share tags, products or a category with Astro Sites Manager: Workflow Init (usenotra/notra, 256 stars), Feature Sliced Design (feature-sliced/skills, 109 stars), Glide Setup (SrivarsanK/Glide, 120 stars) and Asc Aso Rankings (n0an/VivaDicta, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Astro Sites Manager?

fabricioctelles (a GitHub user) maintains it in fabricioctelles/skills, which has 106 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 4, 2026.

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