Agent skill

Update Optimal Blog

by adrianco in adrianco/retort

Refresh the data tables in optimal-blog.md from master.db. An agent skill from adrianco/retort.

Apache-2.0Auto-check passed

Install Update Optimal Blog

skills CLI
$ npx skills add adrianco/retort --skill update-optimal-blog -a claude-code

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

GitHub CLI
$ gh skill install adrianco/retort update-optimal-blog --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/adrianco/retort.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/update-optimal-blog .claude/skills/update-optimal-blog && 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
update-optimal-blog
GitHub stars
207
Token cost
~1.4k tokens
SKILL.md length
724 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Refresh the data tables in optimal-blog.md from master.db. An agent skill from adrianco/retort.

  • Works in 5 steps: Health-check master.db FIRST (gate) → Regenerate the tables → Verify the round-trip → …
  • SKILL.md covers Overview, Why per-language, not aggregates, Steps and Constraints Summary, plus 1 more section
  • Calls git

What it does

Update Optimal Blog is an agent skill from adrianco/retort. Refresh the data tables in optimal-blog.md from master.db. Checks the data for integrity problems FIRST, then runs the generator that picks per-language winners and splices every GEN-marked table, then reconciles the surrounding prose. Use after new experiment results land, or when the optimal-blog numbers are stale.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Platform Evolution Engine. Distill the best from the combinatorial mess. The licence is Apache-2.0.

Example prompts

  • “/update-optimal-blog”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Health-check master.db FIRST (gate)
  2. Regenerate the tables
  3. Verify the round-trip
  4. Reconcile the prose
  5. Report

What it can do on your machine

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

    • git

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

  • Network

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

Update Optimal Blog loads about 1.4k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 724 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 adrianco/retort at commit 1f75769, republished under its Apache-2.0 licence (© adrianco). 724 words, ~1,440 tokens.

Download SKILL.mdSave it as .claude/skills/update-optimal-blog/SKILL.md (or your agent's skills folder).
name
update-optimal-blog
description
Refresh the data tables in optimal-blog.md from master.db. Checks the data for integrity problems FIRST, then runs the generator that picks per-language winners and splices every GEN-marked table, then reconciles the surrounding prose. Use after new experiment results land, or when the optimal-blog numbers are stale.
type
anthropic-skill
version
1.0

Update optimal-blog.md

Overview

optimal-blog.md records what to run today, per language and task size. Its data tables are not hand-written — they are generated from master.db by the retort report optimal subcommand (code in src/retort/reporting/optimal.py) and live between <!-- GEN:<key> START/END --> markers. This skill is the safe procedure for refreshing them: check the data before you trust it, regenerate, verify the round-trip, then fix any prose whose numbers moved.

The order matters. master.db does not record the full stack/config (see the health gaps below), so a blind regenerate can silently publish wrong numbers. Always run the health check first and stop if it reports anything new.

Why per-language, not aggregates

A single cross-language reliability number is misleading — it blends a stack's strong languages with its weak ones (local Qwen passes Python/Go but fails Rust; Opus 4.8 dips on Java). The generator's centrepiece is the per-language success-rate matrix; the leading-stacks routine aggregate is explicitly labelled the least-useful number. Keep it that way — do not "promote" an aggregate back into the recommendation.

Steps

1. Health-check master.db FIRST (gate)
bash
retort report optimal --health

Compare against the known, accepted gaps (already documented in the blog's Keeping this current section):

  • ⚠️ No sampling columns / max_context_tokens unpopulated — the qualified config is curated in FEATURED_STACKS, not filtered from data.
  • ⚠️ ~250 rows have a blank model (local provenance bug) — attributed by experiment slug.
  • ⚠️ experiment-11, experiment-29 not ingested.

You MUST STOP and surface to the user if the report shows anything beyond those:

  • "Unmapped model strings" — a new model appeared that no featured/legacy entry covers. Decide whether it's a new featured stack (add to FEATURED_STACKS) or legacy (add to KNOWN_NONFEATURED) before regenerating. Publishing without deciding would drop it silently.
  • New experiment dirs not in master.db — results exist on disk but aren't ingested; the refresh would omit them. Re-ingest first, or note the omission to the user.
  • A jump in the blank-model count — the harness may have regressed; a run recording no model is invisible to the tables. (The fix landed in src/retort/playpen/runner.py stack_metadata(); if new blanks appear, that path is being bypassed.)
2. Regenerate the tables
bash
retort report optimal --write optimal-blog.md

This splices every GEN:* block (leading stacks, per-language matrix, per-language winners, prompt method). It only touches text between markers.

3. Verify the round-trip
bash
retort report optimal --write optimal-blog.md   # run twice
git diff --stat optimal-blog.md

A second --write MUST produce no further change — the tables are idempotent. If git diff shows table cells changed, that's the real new data; if it shows nothing, the blog was already current.

Show full SKILL.md (330 more words)Show less
4. Reconcile the prose

The generator owns the tables, not the sentences around them. After a refresh, read the diff and fix any prose that quotes a number that moved:

  • The bullets under Leading stacks (e.g. "Opus 4.8 ~0.59 on hard").
  • The per-language recommendation table (the curated one with the prompt/testing column) and its †/‡ footnotes — reconcile its picks against the generated matrix and winner table. A cell that flipped qualified↔unqualified (e.g. a language gaining local support) changes the recommendation.
  • The decision procedure list.
  • The language split sentence if a language moved between local and cloud.

You MUST NOT edit numbers inside the GEN markers by hand — re-run the generator instead.

5. Report

Tell the user: which table cells changed, any prose you reconciled, and — if step 1 found anything — what you stopped on. If nothing changed, say the blog was already current.

Constraints Summary

  • You MUST run --health and clear it against the known gaps before --write.
  • You MUST NOT hand-edit between GEN:* markers; the generator is the source of truth.
  • You MUST NOT introduce or re-elevate a cross-language aggregate as a recommendation — per-language success rates are the point.
  • You MUST verify idempotency (step 3) before considering the update done.
  • A new model string or un-ingested experiment is a STOP-and-ask, not a silent skip.

Troubleshooting

--health reports an unmapped model — add it to FEATURED_STACKS (with a models list and short column name) if it should appear in the blog, or to KNOWN_NONFEATURED if it's legacy/a serving variant. Re-run health until only the accepted gaps remain.

Blank-model count grew — the harness stopped recording model for some runs. Check stack_metadata() is still called by every runner's provision() (local_runner, metaharness_runner, docker_runner); a new runner or a bypass would reintroduce the original bug. Do not paper over it in the generator.

A local language's number looks too low — confirm the curated selection in FEATURED_STACKS still points at the tuned-config experiments, not an all-experiment average (which includes early bad-config runs and understates the tuned reality).

© adrianco, 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

Just SKILL.md in skills/update-optimal-blog of adrianco/retort.

Open the folder on GitHubat commit 1f75769

Compare with similar skills

Update Optimal Blog 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.

Update Optimal Blog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Optimal Blog this skilladrianco/retort207—~1.4kAutomated safety check: PassApache-2.0
SQL Optimizationgithub/awesome-copilot40k2 repos~2.3kAutomated safety check: PassMIT
BlogAgriciDaniel/claude-blog2.3k—~6.2kAutomated safety check: PassMIT
BlogAgriciDaniel/claude-blog2.3k1 repos~8.6kAutomated safety check: WarnMIT
Agent Performance Optimizerruvnet/ruflo74k2 repos~3.6kAutomated safety check: PassMIT
Database Optimizerdavila7/claude-code-templates32k8 repos~2.5kAutomated safety check: PassMIT

Similar skills

  • SQL Optimization

    github/awesome-copilot

    Official

    Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server…

    40k GitHub starsUsed in 2 repos~2.3k tokens
    DatabasesAuto-check passed
  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 templates, 100-point scoring, and 5 agents.

    2.3k GitHub stars~6.2k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Blog

    AgriciDaniel/claude-blog

    Full-lifecycle blog engine with 31 sub-skills, 12 content templates, 5-category 100-point scoring, and 5 specialized agents.

    2.3k GitHub starsUsed in 1 repo~8.6k tokens
    Writing & ContentAuto-check: warnings
  • Agent skill for performance-optimizer - invoke with $agent-performance-optimizer

    74k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed
  • Database Optimizer

    davila7/claude-code-templates

    Expert database optimizer specializing in modern performance tuning, query optimization, and scalable architectures.

    32k GitHub starsUsed in 8 repos~2.5k tokens
    DatabasesAuto-check passed
  • Prompt Optimizer

    affaan-m/ECC

    分析原始提示,识别意图和差距,匹配ECC组件(技能/命令/代理/钩子),并输出一个可直接粘贴的优化提示。仅提供咨询角色——绝不自行执行任务。触发时机:当用户说“优化提示”、“改进我的提示”、“如何编写提示”、“帮我优化这个指令”或明确要求提高提示质量时。中文等效表达同样触发:“优化prompt”、“改进prompt”、“怎么写prompt”、“帮我优化这个指令”。不触发时机:当用户希望直接执行任…

    276k GitHub starsUsed in 2 repos~2.4k tokens
    DevelopmentAuto-check passed

More from adrianco/retort

  • Compare Runs

    adrianco/retort

    Compare evaluated runs in a retort experiment along factor dimensions.

    207 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Diagnose Failed Run

    adrianco/retort

    Determine the TRUE cause of a failed retort run before attributing it.

    207 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Evaluate Run

    adrianco/retort

    Evaluate a single retort experiment run. An agent skill from adrianco/retort.

    207 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • File Run Issues

    adrianco/retort

    Aggregate a retort run's findings.jsonl into a machine-readable assessment.json summary with severity counts, penalty score, requirement coverage, and top findings.

    207 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Run Summary

    adrianco/retort

    Summarize the architecture of code generated by a single retort run.

    207 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Questions about Update Optimal Blog

What does Update Optimal Blog do?

Refresh the data tables in optimal-blog.md from master.db. An agent skill from adrianco/retort. Update Optimal Blog is an agent skill from adrianco/retort.db.

How do I install Update Optimal Blog in Claude Code?

Run `npx skills add adrianco/retort --skill update-optimal-blog -a claude-code`. Or copy the skill folder (skills/update-optimal-blog in adrianco/retort) into .claude/skills/update-optimal-blog in your project. Claude Code loads it when a task matches its description.

How do I install Update Optimal Blog in Codex?

Run `npx skills add adrianco/retort --skill update-optimal-blog -a codex`. Or copy the skill folder (skills/update-optimal-blog in adrianco/retort) into .agents/skills/update-optimal-blog in your project. Codex loads it when a task matches its description.

Can I use Update Optimal Blog 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 adrianco/retort --skill update-optimal-blog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-optimal-blog, .gemini/skills/update-optimal-blog, .github/skills/update-optimal-blog and .opencode/skills/update-optimal-blog in your project.

What does Update Optimal Blog need to run?

Going by SKILL.md and its folder, Update Optimal Blog needs the command-line tools its instructions call (git).

Does Update Optimal Blog access the network?

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

Is Update Optimal Blog 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 Update Optimal Blog use?

Update Optimal Blog 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 Update Optimal Blog use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Update Optimal Blog?

Skills that share tags, products or a category with Update Optimal Blog: SQL Optimization (github/awesome-copilot, 40k stars), Blog (AgriciDaniel/claude-blog, 2.3k stars), Blog (AgriciDaniel/claude-blog, 2.3k stars) and Agent Performance Optimizer (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Optimal Blog?

adrianco (a GitHub user) maintains it in adrianco/retort, which has 207 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

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