Skip to content
Skills Library
Programming · Automation

release-docs

/release-docs

This skill should be used when updating documentation metadata after adding or removing plugin components. It updates plugin.json description and README.md counts, then verifies the Eleventy build produces correct output.

Repository
soleur ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
2
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

This skill should be used when updating documentation metadata after adding or removing plugin components. It updates plugin.json description and README.md counts, then verifies the Eleventy build produces correct output.

Original author description

This skill should be used when updating documentation metadata after adding or removing plugin components. It updates plugin.json description and README.md counts, then verifies the Eleventy build produces correct output.

How it works

  1. Overview
  2. Step 1: Sync README Counts
  3. Step 2: Update plugin.json
  4. Step 3: Update Skill Category Mapping (if needed)
  5. Step 4: Verify Build
  6. Step 5: Report Changes
  7. Post-Release
Original SKILL.md headings · 89 lines, 453 words
SKILL.md preview
---
name: release-docs
description: "This skill should be used when updating documentation metadata after adding or removing plugin components. It updates plugin.json description and README.md counts, then verifies the Eleventy build produces correct output."
---

<!-- grok-harness-invoke:start -->
**Grok Build (`plugins/soleur/lib/harness.ts` `invokeSkill()`):** Read this SKILL.md in this process and run it to completion. A one-segment `soleur:<name>` in this document names a SKILL — on Grok Build, Read `plugins/soleur/skills/<name>/SKILL.md` in this process; it is not a nested tool_use. A multi-segment id such as `soleur:<domain>:<name>` names an AGENT: spawn it, never Read it, and on Grok Build spawn_subagent takes the id with its colons replaced by hyphens (`agentIdToGrokSubagentType`). **Claude Code:** Skill tool for a skill (`soleur:<name>`), Task tool with `subagent_type` for an agent. Forbidden is executing a subset, not the Read.
<!-- grok-harness-invoke:end -->

# Release Documentation

Update documentation metadata and verify the docs site builds correctly after plugin component changes.

## Overview

The documentation site auto-generates agent and skill catalog pages from source file frontmatter via Eleventy. This skill handles the metadata files that still need manual updates.

**What is automated (no action needed):**

- Agent catalog page (`pages/agents.html`) -- built from `agents/**/*.md` frontmatter
- Skill catalog page (`pages/skills.html`) -- built from `skills/*/SKILL.md` frontmatter
- Stats on landing page -- counted from file system at build time

**What still needs manual updates:**

- `plugins/soleur/.claude-plugin/plugin.json` description with counts
- `knowledge-base/marketing/brand-guide.md` agent/skill counts (if it exists)

## Step 1: Sync README Counts

Run the automated sync script to update counts in both `README.md` and `plugins/soleur/README.md`:

```bash
bash scripts/sync-readme-counts.sh
```

This updates: root README intro line, root README "What is Soleur?" counts, plugin README component count table, and plugin README domain section headers.

## Step 2: Update plugin.json

Update `plugins/soleur/.claude-plugin/plugin.json` description with correct counts (not covered by the sync script).

## Step 3: Update Skill Category Mapping (if needed)

If skills were added, removed, or recategorized, update the category mapping in:

```
plugins/soleur/docs/_data/skills.js
```

The `SKILL_CATEGORIES` object maps each skill name to its display category. New skills must be added here or they will appear as "Uncategorized" in the catalog.

## Step 4: Verify Build

```bash
# Run the Eleventy build
npx @11ty/eleventy
```

After the build completes, verify counts by using Grep to count occurrences of `component-card` in `_site/pages/agents.html` and `_site/pages/skills.html`.

Verify JSON files are well-formed:

```bash
cat plugins/soleur/.claude-plugin/plugin.json | jq .
```

## Step 5: Report Changes

Provide a summary of what was updated:

```
## Documentation Release Summary

### Component Counts
- Agents: X (previously Y)
- Commands: X (previously Y)
- Skills: X (previously Y)

### Files Updated
- plugin.json - Updated counts
- README.md - Updated component lists
- _data/skills.js - Updated category mapping (if applicable)
```

## Post-Release

After successful release:

1. Suggest updating CHANGELOG.md with documentation changes
2. Remind to commit with message: `docs: Update documentation metadata to match plugin components`
3. Remind to push changes -- the deploy workflow will rebuild the site automatically

Versions

The database has no other skills named release-docs.

Database snapshot: 13.11.2026 · package version a0faeb2824c9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100deploy-docs
    This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
  • 100garden-plugin-author
    Create, test, and publish plugins for the Digital Garden Eleventy template (oleeskild/digitalgarden, used by the obsidian-digital-garden plugin and Forestry.md). Use when asked to build a garden plugin, add a feature to a digital garden as a plugin, write or edit a…
  • 100docs-site
    This skill should be used when scaffolding a Markdown-based Eleventy documentation site: base layout, data files, GitHub Pages deployment workflow, and passthrough copy configuration.
  • 90plugin-readme
    Write or review a NetAlertX plugin's README.md (server/plugins/<code_name>/README.md). Use this when asked to create, enhance, audit, or clean up a plugin README, or plugin docs generally.
  • 85netalertx-plugin-readme
    Write or review a NetAlertX plugin's README.md (server/plugins/<code_name>/README.md). Use this when asked to create, enhance, audit, or clean up a plugin README, or plugin docs generally.
  • 90marketplace
    Use when working on the cc-plugins repository itself: adding a plugin, renaming one, removing one, bumping a version, or after editing any plugin's components. Also when writing or revising a skill's description or body, or editing CLAUDE.md — WRITING.md carries the judgment for…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.