Flint

User Manual

Core concepts: managing skills as assets

Before you start, spend a few minutes on a few key concepts: what a skill is, what the asset mindset means, and Flint's collect → organize → deploy workflow.

Flint is a local-first skills manager and skills hub. It centralizes the skills scattered across all of your agents and projects into one local single source of truth, then deploys them on demand into each agent's and project's own skills directory. For what a skill is and the standard, see the Learning Skills section.

Key concepts

  • SkillA reusable ability description, usually a piece of markdown (SKILL.md): when a model runs into a matching scenario, it reads it to get the method or tool usage.
  • AssetFlint's core view: treat each skill as an ability that belongs to you, not a software package to install. Deployment is just a mount — it never changes ownership or creates a second copy.
  • Single source of truthEvery skill lives once in one local directory. Tagging, search, and deduplication all happen on this source, instead of many scattered copies in each agent's directory.
  • DestinationsMount the asset on demand into each agent's / project's skills directory (e.g. .claude/skills, .cursor/skills). One asset can be mounted to several places at once.

A three-step workflow: collect (bring scattered or shared skills into your asset inventory) → organize (tag, dedupe, and describe them into your own skill list) → deploy (mount them on demand into each agent and project).