Philosophy & Design
Flint: same stone, a different object to polish — skills
Flint's name comes from Obsidian. Obsidian is a naturally sharp volcanic glass that early humans knapped into blades; Flint is the other tool stone that stands beside it.
Knapping
Gather scattered skills, deduplicate, tag, and strike them into precise, handy tools. This maps to the 'organise' half of the product.
Spark
Deploy and distribute skills into agent and project directories so they are truly ignited and start doing work. This maps to the 'deploy' half.
Obsidian → Flint
Three beliefs, carried over
Every skill you collect is a piece of flint waiting to strike a spark.
Local and private
Skills exist only as plain files on your local disk — no cloud, no account, no telemetry
Open formats, never locked in
A skill's body is just a SKILL.md directory, versioned with git; switch ecosystems and the asset comes with you
Sharpen your thinking
Sharpen your skills: collect, deduplicate, tag — handier with use
Two design orientations
Stay close to the open ecosystem
Tags land in each SKILL.md frontmatter's top-level tags field — a position natively read by 40+ tools including Claude Code and agentskills.io, and versioned together with the skill directory and git.
Reduce ecosystem fragmentation
When same-named skills come from multiple sources, deduplication keeps one copy; duplicates, divergence, and broken references are surfaced on the Health page and handled in place.