The open artifact manager for AI tools.
grekt treats AI configurations (system prompts, rules, agents, skills, hooks, MCPs) as first-class artifacts with versioning, integrity checks, and a plugin-based sync system. It supports current and emerging AI tools, if a new agent or coding assistant appears tomorrow, grekt is ready.
curl -fsSL https://cli.grekt.com/install.sh | shnpm i -g @grekt/cligrekt init # initialize a project
grekt add @scope/name # add an artifact from the registry
grekt sync # sync artifacts to your AI toolsDocumentation | Explore artifacts
| Repo | Description |
|---|---|
| cli | The grekt CLI |
| engine | Core engine powering the CLI and integrations |
| docs | Documentation |
| docs-dev | Developer docs for building integrations |
This roadmap reflects our current direction. It's not a promise priorities shift as we learn.
What we're actively building and refining.
- Focus on auditability - Look for integrations or features that will allow teams to trust it's own AI stack.
What's coming after current work stabilizes.
- Private artifacts - publish private artifacts to the grekt registry, visible only to you or your organization
- Organizations and teams - shared artifact ownership, access control, team workspaces
- Verified publishers - trust signals for artifact authors and organizations
- Granular capability policies - leverage declared capabilities for fine-grained access control and auditing
- Registry hardening - improving the publish/download flow, error handling, and edge
- Artifact kits - curated collections for team onboarding and standardization
Directions we're exploring. No timelines.
- Discovery and insights - compatibility matrix, trending artifacts, usage analytics
Have ideas or feedback? Open an issue or start a discussion.
grekt is source-available under BSL 1.1. You can use it freely for any purpose personal, commercial, internal tooling, as long as you don't use the code to build a competing product. Each version converts to MIT after two years. Learn more.