Clipsmith captures posts, articles, local media, and OCR output into portable
clipsmith.capture_bundle.v1 directories.
It is split into:
- a Python CLI for provider routing, bundle validation, jobs, sinks, install, and doctor checks
- agent skills for platform capture in Codex and Claude Code
- provider quality gates that combine deterministic checks with agent-run AI eval where extraction quality needs model judgment
uv tool install --force git+https://github.com/OctopusGarage/clipsmith.git
clipsmith install --all
clipsmith doctorRestart Codex or Claude Code after installing skills.
For a source checkout:
git clone https://github.com/OctopusGarage/clipsmith.git
cd clipsmith
./install.sh --allMore options: INSTALL.md.
After installing skills, ask an agent:
Use clipsmith-capture to capture https://example.com/post
To sink a validated bundle to a workspace inbox, say so explicitly:
Use clipsmith-capture to capture https://example.com/post and sink it to /path/to/inbox-workspace
Useful CLI commands:
clipsmith providers --json
clipsmith quality-gates --json
clipsmith validate-bundle /path/to/bundle --json
clipsmith export okf /path/to/bundle /path/to/okf-workspace --json
clipsmith sink directory /path/to/bundle ~/Downloads/clips --json
clipsmith sink inbox /path/to/bundle /path/to/inbox-workspace --jsonIn a source checkout, use uv run clipsmith ....
uv run pytest -q
./script/check-health.shcheck-health is the project gate: it runs tests, validates skill contracts,
checks quality gate declarations, and verifies packaged skills do not include
development-only assets.