Computed Skills banner
Joncik91 Joncik91

Computed Skills

Development community

Description

Skills vs Computed Skills — when the prompt is a program's output

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Computed Skills

[![License: MIT](https://img.shields.io/badge/license-MIT-E8954A.svg)](LICENSE) [![Python 3.8+](https://img.shields.io/badge/python-3.8%2B-3776AB?logo=python&logoColor=white)](https://www.python.org/) [![Claude Code](https://img.shields.io/badge/works%20with-Claude%20Code-E8954A)](https://claude.ai/claude-code) [![GitHub stars](https://img.shields.io/github/stars/Joncik91/computed-skills?color=E8954A&logo=github)](https://github.com/Joncik91/computed-skills/stargazers) [![Concept + examples](https://img.shields.io/badge/concept%20%2B%20examples-✓-E8954A)]()

**Skills that adapt to what's actually happening.**

A static skill gives the same instructions every time. A computed skill runs a script first — analyzes the situation, pre-digests data, picks a strategy — then hands the agent tailored markdown. The agent never knows a script was involved.

Table of Contents

Static:    SKILL.md ──────────────────────────→ Agent reads markdown
Computed:  SKILL.md → runs script → markdown ─→ Agent reads markdown

Works with [Claude Code](https://claude.ai/claude-code) and any skill system that supports `!`command`` preprocessing. Any language that prints to stdout.

Why Computed Skills

Static skills have a fundamental problem: they can't see context. A static code review skill gives the same checklist whether you changed 2 files or 40, whether you touched auth code or CSS. A static deploy checklist shows 20 items every time — and agents learn to skim them all.

Computed skills fix this by letting a script decide what the agent sees:

2 aut