Skills enter through a controlled pipeline instead of ad hoc source installs.
Aptitude turns scattered prompts, scripts, and tools into structured, versioned, composable assets that can be published, discovered, resolved, and consumed by humans and AI agents.
Product Overview
Aptitude treats skills the way package managers treat libraries: structured metadata, immutable artifacts, exact versions, declared dependencies, and reproducible installation.
Skills enter through a controlled pipeline instead of ad hoc source installs.
Humans and agents search a catalog without crawling GitHub or guessing identifiers.
Dependencies, policies, and versions produce a deterministic execution plan.
The Problem
Today, skills are difficult to discover, trust, govern, and compose reliably at scale. That creates low reuse, duplicated work, and unpredictable agent behavior.
Agents still depend on crawling, cloning, and heuristics instead of a standard discovery surface.
Without validation, benchmarks, provenance, and trust tracking, capability usage stays unsafe and brittle.
Teams need lifecycle states, access controls, and policy enforcement before skills become operational defaults.
Atomic skills, dependencies, and lockfiles are required for reproducible bundles across users and agents.
The Solution
Aptitude turns team knowledge into audited, benchmarked, immutable skill versions that can be discovered, composed, locked, and installed under policy.
Package checks, security review, quality benchmarks, and provenance capture turn raw skills into trusted artifacts.
Lifecycle state, trust tier, ownership, and installation policy travel with each skill version.
Approved skills are selected, dependency-checked, locked to exact versions, and installed as repeatable plans.
Evidence
The benchmark pattern is straightforward: curated context helps, noisy retrieval hurts, and refinement turns retrieval into a stronger operating loop.
Retrieval alone is not the win. Selection and curation are the difference between signal and extra surface area.
Workflow
The operating loop stays readable: author, review, publish, discover, resolve, and install. Governance stays attached at each step.
Built For
Aptitude connects the operators who govern skills, the people using agents, and the agents that need dependable capability discovery at runtime.
Govern publication, access, policy, versions, provenance, and runtime installation paths.
Anyone using agents can find trusted capabilities, understand what they do, and reuse shared knowledge without hunting through repos.
Discover, resolve, and install approved skills through the same governed capability layer.
System Composition
Aptitude separates enforcement, storage, and decision-making so each component owns one responsibility and the system remains deterministic.
Catalog Access