hyphen-skills

A collection of Claude Code skills maintained by mathhyphen.

Each skill lives in its own subdirectory and is independently installable.

Install a skill

Skills follow the Claude Code skill format.

One-off install (per-skill)

# Clone this repo, then symlink the skill into your Claude skills folder
git clone https://github.com/mathhyphen/hyphen-skills.git /tmp/hyphen-skills
ln -s /tmp/hyphen-skills/lab-daily-report ~/.claude/skills/lab-daily-report

Claude Code auto-discovers any folder under ~/.claude/skills/. Once the symlink exists, the skill is available in every session.

Install via the skills.sh registry (if published)

npx skills add mathhyphen/hyphen-skills
# or for a specific skill:
npx skills add mathhyphen/hyphen-skills/lab-daily-report

Skills in this repo

Skill	Description
lab-daily-report	Per-server daily experiment digest → Notion database row. Scrapes Claude Code / Codex session logs + training *.log files, compresses them with an LLM, and writes a structured page (with postmortem on failed experiments) to a Notion database once per day.

Repository layout

hyphen-skills/
├── README.md                  # this file
├── .gitignore                 # excludes dist/, __pycache__, etc.
└── <skill-name>/              # one folder per skill
    ├── SKILL.md               # required: frontmatter + workflow + constraints
    ├── scripts/               # runnable code
    ├── references/            # docs loaded by Claude on demand
    └── assets/                # templates copied into the user's project

When adding a new skill:

1. Create <skill-name>/ with the standard layout.
2. Write SKILL.md with a YAML frontmatter (name, description) — the description is the trigger text.
3. Document any non-obvious constraints in references/ so future Claude instances don't re-discover them via failed 400 errors.
4. Keep hard constraints (e.g. "Notion callout icon MUST be a real emoji") in SKILL.md itself, not buried in references.

Versioning

This repo uses a simple per-skill versioning model. Each skill's SKILL.md should state its current version at the top of the changelog section. Breaking changes (config file moves, removed scripts) warrant a major bump; new data sources or output fields are minor.

License

MIT. See each skill's folder for skill-specific license notes (most are MIT too).