skillctx

<div align="center">

# skillctx

**Portable config for agent skills — for Skill creators and users alike.**

[![CI](https://github.com/jackchuka/skillctx/actions/workflows/ci.yml/badge.svg)](https://github.com/jackchuka/skillctx/actions/workflows/ci.yml)
[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776AB?logo=python&logoColor=white)](https://www.python.org)
[![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
[![Version](https://img.shields.io/badge/version-0.1.0-blue.svg)](https://github.com/jackchuka/skillctx)

<br>

<img alt="skillctx — one config, every skill, zero deps" src="assets/hero.svg" width="100%">

</div>

## The Problem

Agent skills are personal by default. A skill that posts your standup, manages your todos, or deploys your app is wired to **your** usernames, paths, Slack channel IDs, and API endpoints. It works perfectly — on your machine.

The moment you share it, it breaks. The next person has to dig through your SKILL.md, find every hardcoded value, and manually swap them out. Multiply that across ten skills and it's no longer "install and use" — it's "install and debug."

**For creators**, this means your skills aren't truly portable. You can publish them, but every user has to reverse-engineer your personal config.

**For users**, this means every new skill is a setup chore — hunting through files for values that need changing before anything works.

## The Solution

```diff
 # SKILL.md (daily-standup)
- Post standup for alice in Slack (CABC123DEF) channel
- Save memo to ~/notes
+ Post standup for {username} in Slack ({channel_id}) channel
+ Save memo to {notebook_path}
```

Hardcoded values become `{placeholders}`, resolved at runtime from one shared config (`~/.config/skillctx/config.json`).

**For creators**: one command migrates your skill. No manual find-and-replace, no template syntax to learn.

**For users**: install a skill and run it. On first use you're prompted for missing values — fill the