Agent skill

Wordpress Sage Theme

by giuseppe-trisciuoglio in giuseppe-trisciuoglio/developer-kit

Provides WordPress theme development patterns using Sage (roots/sage) framework.

MITAuto-check: notesDevelopment

Install Wordpress Sage Theme

skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill wordpress-sage-theme -a claude-code

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

GitHub CLI
$ gh skill install giuseppe-trisciuoglio/developer-kit wordpress-sage-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/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-kit-php/skills/wordpress/wordpress-sage-theme .claude/skills/wordpress-sage-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
wordpress-sage-theme
GitHub stars
357
Token cost
~3.2k tokens
SKILL.md length
951 words
Files
7 (incl. references, assets)
Skills in repo
115
Repo updated
First seen
Licence
MIT

At a glance

Provides WordPress theme development patterns using Sage (roots/sage) framework.

  • Works in 7 steps: Set up the environment: Install PHP… → Configure build tools: Run npm install… → Create Blade templates: Place templates… → …
  • Debugging WordPress themes with Sage
  • SKILL.md covers Overview, When to Use, Instructions and Examples, plus 9 more sections
  • Runs PHP scripts from its folder; calls npm, composer and npx

What it does

Wordpress Sage Theme is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides WordPress theme development patterns using Sage (roots/sage) framework. Use when creating, modifying, or debugging WordPress themes with Sage, including (1): creating new Sage themes from scratch, (2): setting up Blade templates and components, (3): configuring build tools (Vite, Bud), (4): working with WordPress theme templates and hierarchy, (5): implementing ACF fields integration, (6): theme customization and asset management.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `references/acf.md`, `references/blade.md` and `references/bud.md`).

It sits in Development. It works with WordPress, Vite, PHP and npm. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.

When your agent uses it

  • Debugging WordPress themes with Sage
  • : creating new Sage themes from scratch
  • : setting up Blade templates and components
  • : configuring build tools (Vite

Example prompts

  • “Use the wordpress-sage-theme skill to provide WordPress theme development patterns using Sage (roots/sage) framework”
  • “/wordpress-sage-theme”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Write, Bash, Glob, Grep

Workflow steps

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

  1. Set up the environment: Install PHP 8.0+, Node.js 18+, Composer, and create a new Sage theme with composer create-project roots/sage
  2. Configure build tools: Run npm install && composer install, then configure bud.config.js for asset entries and Tailwind
  3. Create Blade templates: Place templates in resources/views/, using layouts in layouts/, components in components/
  4. Wire up WordPress templates: Map WordPress template hierarchy to Blade files (e.g., page.blade.php for page templates)
  5. Integrate ACF fields: Use get_field() for basic fields, have_rows() loops for repeaters and flexible content
  6. Build and verify: Run npm run build, verify public/manifest.json exists, check browser console for asset errors
  7. Deploy: Ensure the production build step (npm run build) runs during deployment; raw source files cannot be served directly

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (PHP), which the agent can run.

    Shell commands in SKILL.md call:

    • npm
    • composer
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, 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

Wordpress Sage Theme loads about 3.2k tokens when it runs, and up to ~8.9k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 951 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Bash, Glob, Grep

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 giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 951 words, ~3,211 tokens.

Download SKILL.mdSave it as .claude/skills/wordpress-sage-theme/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
wordpress-sage-theme
description
Provides WordPress theme development patterns using Sage (roots/sage) framework. Use when creating, modifying, or debugging WordPress themes with Sage, including (1): creating new Sage themes from scratch, (2): setting up Blade templates and components, (3): configuring build tools (Vite, Bud), (4): working with WordPress theme templates and hierarchy, (5): implementing ACF fields integration, (6): theme customization and asset management.
allowed-tools
Read, Write, Bash, Glob, Grep

WordPress Sage Theme Development

Overview

Sage is a WordPress theme framework by Roots that provides modern development practices including Blade templates, dependency management with Composer, and build tools with Vite/Bud.

When to Use

  • Creating new Sage themes from scratch or from composer templates
  • Setting up Blade templates, layouts, and reusable components
  • Configuring build tools (Bud/Vite) for asset compilation
  • Working with WordPress template hierarchy in Blade format
  • Integrating Advanced Custom Fields (ACF) with Blade templates
  • Debugging theme rendering, asset loading, or build issues

Instructions

  1. Set up the environment: Install PHP 8.0+, Node.js 18+, Composer, and create a new Sage theme with composer create-project roots/sage
  2. Configure build tools: Run npm install && composer install, then configure bud.config.js for asset entries and Tailwind
  3. Create Blade templates: Place templates in resources/views/, using layouts in layouts/, components in components/
  4. Wire up WordPress templates: Map WordPress template hierarchy to Blade files (e.g., page.blade.php for page templates)
  5. Integrate ACF fields: Use get_field() for basic fields, have_rows() loops for repeaters and flexible content
  6. Build and verify: Run npm run build, verify public/manifest.json exists, check browser console for asset errors
  7. Deploy: Ensure the production build step (npm run build) runs during deployment; raw source files cannot be served directly

Examples

Create a new Sage theme:

bash
composer create-project roots/sage my-theme
cd my-theme
npm install && composer install
npm run dev

Blade page template:

blade
@extends('layouts.app')

@section('content')
  <main class="content">
    <h1>{{ the_title() }}</h1>
    <div class="entry-content">
      {{ the_content() }}
    </div>
  </main>
@endsection

ACF flexible content in Blade:

blade
@if (have_rows('flexible_content'))
  @while (have_rows('flexible_content'))
    @php the_row() @endphp
    @switch(get_row_layout())
      @case('hero_section')
        @include('components.hero')
        @break
    @endswitch
  @endwhile
@endif

Quick Start

Creating a New Sage Theme

Prerequisites: PHP 8.0+, Node.js 18+, Composer

bash
# Create new Sage theme
wp scaffold theme-theme my-theme --theme_name="My Theme" --author="Your Name" --activate

# Or install Sage directly via Composer
composer create-project roots/sage my-theme
cd my-theme

# Install dependencies
npm install
composer install

# Build for development
npm run dev

# Build for production
npm run build
Directory Structure
resources/
├── views/           # Blade templates
│   ├── layouts/     # Base layouts (app.blade.php)
│   ├── components/  # Reusable components
│   └── partials/    # Template partials
├── styles/          # CSS/SASS files
│   └── main.scss    # Main stylesheet
└── scripts/         # JavaScript files
    └── main.js      # Main JavaScript

Blade Templates

Layouts

Base Layout (resources/views/layouts/app.blade.php):

blade
<!DOCTYPE html>
<html {{ site_html_language_attributes() }}>
  <head>
    {{ wp_head() }}
  </head>
  <body {{ body_class() }}>
    @yield('content')
    {{ wp_footer() }}
  </body>
</html>
Template Hierarchy Mapping
WordPress TemplateSage Blade File
front-page.phpviews/front-page.blade.php
single.phpviews/single.blade.php
page.phpviews/page.blade.php
archive.phpviews/archive.blade.php
index.phpviews/index.blade.php

Example Page Template (resources/views/page.blade.php):

blade
@extends('layouts.app')

@section('content')
  <main class="content">
    <h1>{{ the_title() }}</h1>
    <div class="entry-content">
      {{ the_content() }}
    </div>
  </main>
@endsection
Components

Reusable Button Component (resources/views/components/button.blade.php):

blade
@props(['url' => '#', 'text' => 'Click', 'variant' => 'primary'])

<a href="{{ $url }}" class="btn btn-{{ $variant }}">
  {{ $text }}
</a>

Usage:

blade
<x-button url="/contact" text="Contact Us" variant="secondary" />

ACF Integration

Displaying ACF Fields

Basic Field:

blade
@while(the_post())
  <h1>{{ get_field('hero_title') ?? the_title() }}</h1>
  <p>{{ get_field('hero_description') }}</p>
@endwhile

Flexible Content:

blade
@if (have_rows('flexible_content'))
  @while (have_rows('flexible_content'))
    @php the_row() @endphp

    @switch(get_row_layout())
      @case('hero_section')
        @include('components.hero')
        @break

      @case('features_grid')
        @include('components.features-grid')
        @break
    @endswitch
  @endwhile
@endif

Repeater Field:

blade
@if (have_rows('testimonials'))
  <div class="testimonials">
    @while (have_rows('testimonials'))
      @php the_row() @endphp
      <blockquote>
        <p>{{ get_sub_field('testimonial_text') }}</p>
        <cite>{{ get_sub_field('author_name') }}</cite>
      </blockquote>
    @endwhile
  </div>
@endif

Build Configuration (Bud)

Tailwind CSS Setup

Install Tailwind:

bash
npm install -D tailwindcss
npx tailwindcss init -p

Configure (bud.config.js):

js
export default async (app) => {
  app
    .entry({
      app: ['@/scripts/main.js', '@styles/main.css'],
      editor: ['@scripts/editor.js', '@styles/editor.css'],
    })
    .assets('images', 'fonts')
    .tailwind()
    .runtime()
};

Tailwind CSS (resources/styles/main.css):

css
@tailwind base;
@tailwind components;
@tailwind utilities;

@layer components {
  .btn {
    @apply px-4 py-2 rounded font-semibold transition;
  }

  .btn-primary {
    @apply bg-blue-600 text-white hover:bg-blue-700;
  }
}

Advanced Patterns

Conditional Logic
blade
@if (is_front_page())
  @include('components.hero')
@elseif (is_singular('post'))
  @include('components.post-meta')
@endif
Custom Queries
blade
@php
  $args = [
    'post_type' => 'service',
    'posts_per_page' => 6,
  ];
  $query = new WP_Query($args);
@endphp

@if ($query->have_posts())
  @while ($query->have_posts())
    @php $query->the_post() @endphp
    <article>
      <h2>{{ the_title() }}</h2>
    </article>
  @endwhile
  @php wp_reset_postdata() @endphp
@endif
Theme Customization

functions.php additions:

php
// Custom image sizes
add_image_size('hero-lg', 1920, 1080, true);

// Custom post types
add_action('init', function() {
  register_post_type('service', [
    'label' => 'Services',
    'public' => true,
    'has_archive' => true,
    'supports' => ['title', 'editor', 'thumbnail'],
  ]);
});

References

  • Sage Documentation: See sage.md for complete framework reference
  • Blade Templates: See blade.md for advanced Blade patterns
  • Bud Configuration: See bud.md for build tool configuration
  • ACF Integration: See acf.md for ACF field examples

Troubleshooting

Build workflow validation (always run in order):

  1. npm run build completes without errors
  2. Verify public/manifest.json exists and contains asset entries
  3. Test locally in browser before production push
  4. Check browser console for asset 404 errors

Build issues:

bash
# Clear cache
npm run clean

# Rebuild
rm -rf node_modules public
npm install
npm run build

# Validate build output
ls -la public/
cat public/manifest.json | head -20

Blade not compiling: Check public/manifest.json exists after build

AC fields not showing: Verify field names match exactly (case-sensitive)

Best Practices

Blade Template Organization
  • Use components for reusable UI elements: Create blade components in resources/views/components/ for buttons, cards, and other repeated elements
  • Keep layouts minimal: Base layouts should only contain structural HTML; delegate styling to components
  • Leverage Blade directives: Use @include, @each, and @component for better code organization
  • Avoid inline PHP: Use @php blocks sparingly; move complex logic to Composers or service classes
ACF Field Management
  • Group related fields: Use ACF field groups to organize fields logically by content type
  • Use field keys for references: When referencing fields programmatically, use field keys (e.g., field_12345678) for reliability
  • Implement fallback values: Always provide default values for optional fields to prevent empty output
  • Cache expensive queries: Use WordPress transients for complex ACF queries on high-traffic pages
Asset Management
  • Use Bud for asset compilation: Let Bud handle versioning and optimization instead of manual asset management
  • Minimize HTTP requests: Combine CSS/JS files where appropriate using Bud's entry points
  • Optimize images: Use WordPress image sizes and lazy loading; consider WebP conversion
  • Cache busting: Bud automatically handles cache busting via manifest.json
Show full SKILL.md (381 more words)Show less
Code Organization
  • Use Composers for data: Move data retrieval logic from templates to Sage Composers (app/View/Composers/)
  • Separate concerns: Keep business logic in service classes, presentation in Blade templates
  • Follow WordPress coding standards: Maintain consistency with WordPress PHP coding standards
  • Use type declarations: PHP 8.0+ allows typed properties and arguments for better code quality
Security Considerations
  • Escape all output: Use {{ }} (Blade auto-escapes) or WordPress functions like esc_html(), esc_url()
  • Validate ACF input: Sanitize and validate custom field inputs on the backend
  • Nonce verification: Always verify nonces for form submissions
  • Capability checks: Use current_user_can() before privileged operations

Constraints and Warnings

Version Requirements
  • PHP 8.0+ required: Sage 10 requires PHP 8.0 or higher; earlier versions are not supported
  • Node.js 18+ required: Build tools require modern Node.js; older versions may cause compilation errors
  • WordPress 6.0+ recommended: While Sage works with WordPress 5.x, version 6.0+ is recommended for full feature support
  • Composer required: Dependency management requires Composer; manual installation is not supported
Build Tool Limitations
  • Hot reload limitations: Bud's hot reload may not work correctly with some WordPress multisite configurations
  • Production builds required for testing: Some features work differently in development vs production; always test with npm run build before deployment
  • Manifest.json dependency: Theme relies on public/manifest.json; missing this file breaks asset loading
Common Pitfalls
  • Template hierarchy confusion: Sage uses Blade files but follows WordPress template hierarchy; ensure file names match WordPress expectations
  • Direct file access: Do not access Blade files directly via URL; they must be rendered through WordPress
  • Plugin conflicts: Some caching and security plugins may interfere with Bud's hot reload or asset serving
  • Theme updates: Updating Sage via Composer may overwrite customizations; use child themes for extensive modifications
Performance Considerations
  • ACF Repeater performance: Large repeater fields can impact page load; consider pagination or alternative storage for large datasets
  • Blade compilation overhead: First load after cache clear compiles all templates; use OPcache in production
  • Asset bundle size: Monitor compiled asset sizes; large bundles affect page load performance
  • Database queries: Use Query Monitor plugin to identify and optimize expensive queries in theme templates
Deployment Constraints
  • Build step required: Production deployments must run npm run build; raw source files cannot be served
  • Environment-specific configuration: Bud configuration may need adjustment for different deployment environments
  • File permissions: Ensure public/ directory is writable during builds; incorrect permissions cause build failures

© giuseppe-trisciuoglio, MIT. 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 6 other files (references, assets) in plugins/developer-kit-php/skills/wordpress/wordpress-sage-theme of giuseppe-trisciuoglio/developer-kit.

  • SKILL.md
  • assets/starter-layout.blade.php
  • assets/starter-page.blade.php
  • references/acf.md
  • references/blade.md
  • references/bud.md
  • references/sage.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

Wordpress Sage 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.

Wordpress Sage Theme compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wordpress Sage Theme this skillgiuseppe-trisciuoglio/developer-kit357—~3.2kAutomated safety check: NotesMIT
DevAutomattic/wordpress-activitypub582—~1.1kAutomated safety check: PassMIT
Testingbonny/WordPress-Simple-History317—~5kAutomated safety check: NotesNone
Laravel ToolingHoangNguyen0403/agent-skills-standard572—~760Automated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
Wp Interactivity APIAutomattic/agent-skills2112 repos~1.5kAutomated safety check: PassNone

Similar skills

  • Dev

    Automattic/wordpress-activitypub

    Development workflows for WordPress ActivityPub plugin including wp-env setup, testing commands, linting, and build processes.

    582 GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Testing

    bonny/WordPress-Simple-History

    Guidance for writing and running tests in Simple History, including the Premium add-on.

    317 GitHub stars~5k tokensUpdated 3 days ago
    Testing & QAAuto-check: notes
  • Laravel Tooling

    HoangNguyen0403/agent-skills-standard

    Configure Laravel ecosystem with custom Artisan commands, Vite asset bundling, Pint code styling, and Horizon queue monitoring.

    572 GitHub stars~760 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Wp Interactivity API

    Automattic/agent-skills

    A skill your agent uses when building or debugging WordPress Interactivity API features (data-wp- directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration…

    211 GitHub starsUsed in 2 repos~1.5k tokens
    DevelopmentAuto-check passed
  • WooCommerce Dev Cycle

    woocommerce/woocommerce

    Workflow for WooCommerce development: run PHP and JavaScript tests, lint and fix code style on the current branch, and follow guides for i18n and markdown.

    11k GitHub starsUsed in 3 repos~431 tokens
    DevelopmentAuto-check passed

More from giuseppe-trisciuoglio/developer-kit

All 115 skills in this repo
  • Nestjs Drizzle Crud Generator

    giuseppe-trisciuoglio/developer-kit

    Generates complete CRUD modules for NestJS applications with Drizzle ORM.

    357 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Actuator

    giuseppe-trisciuoglio/developer-kit

    Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.

    357 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Crud Patterns

    giuseppe-trisciuoglio/developer-kit

    Provides and generates complete CRUD workflows for Spring Boot 3 services.

    357 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Security JWT

    giuseppe-trisciuoglio/developer-kit

    Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…

    357 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • AWS CLI Beast

    giuseppe-trisciuoglio/developer-kit

    Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.

    357 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check: notes
  • PR Review Comments

    giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.

    357 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check: notes

Categories

Questions about Wordpress Sage Theme

What does Wordpress Sage Theme do?

Provides WordPress theme development patterns using Sage (roots/sage) framework. Wordpress Sage Theme is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides WordPress theme development patterns using Sage (roots/sage) framework.

When should I use Wordpress Sage Theme?

Wordpress Sage Theme fits situations like: debugging WordPress themes with Sage; : creating new Sage themes from scratch; : setting up Blade templates and components; : configuring build tools (Vite.

How do I install Wordpress Sage Theme in Claude Code?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill wordpress-sage-theme -a claude-code`. Or copy the skill folder (plugins/developer-kit-php/skills/wordpress/wordpress-sage-theme in giuseppe-trisciuoglio/developer-kit) into .claude/skills/wordpress-sage-theme in your project. Claude Code loads it when a task matches its description.

How do I install Wordpress Sage Theme in Codex?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill wordpress-sage-theme -a codex`. Or copy the skill folder (plugins/developer-kit-php/skills/wordpress/wordpress-sage-theme in giuseppe-trisciuoglio/developer-kit) into .agents/skills/wordpress-sage-theme in your project. Codex loads it when a task matches its description.

Can I use Wordpress Sage 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 giuseppe-trisciuoglio/developer-kit --skill wordpress-sage-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/wordpress-sage-theme, .gemini/skills/wordpress-sage-theme, .github/skills/wordpress-sage-theme and .opencode/skills/wordpress-sage-theme in your project.

What does Wordpress Sage Theme need to run?

Going by SKILL.md and its folder, Wordpress Sage Theme needs PHP for the scripts in its folder and the command-line tools its instructions call (npm, composer and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Bash, Glob, Grep.

Does Wordpress Sage Theme access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Wordpress Sage Theme safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Wordpress Sage Theme use?

Wordpress Sage Theme is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wordpress Sage Theme use?

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

What are the alternatives to Wordpress Sage Theme?

Skills that share tags, products or a category with Wordpress Sage Theme: Dev (Automattic/wordpress-activitypub, 582 stars), Testing (bonny/WordPress-Simple-History, 317 stars), Laravel Tooling (HoangNguyen0403/agent-skills-standard, 572 stars) and WooCommerce Code Review (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wordpress Sage Theme?

giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.

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