maya
v1.9.5Eight skills that run the Maya dates project: orient, spec, record, fixtures, plan, fleet, implement, review
By Drew Sonne0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 8 skill or MCP entries
- Source updated
- Sep 26, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install maya for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install maya@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/drewsonne/maya-projectClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/maya/.
Plugin files
├── .claude-plugin/plugin.json├── skills/maya-fixtures/SKILL.md├── skills/maya-fleet/SKILL.md├── skills/maya-implement/SKILL.md├── skills/maya-orient/SKILL.md├── skills/maya-plan/SKILL.md├── skills/maya-record/SKILL.md├── skills/maya-review/SKILL.md└── skills/maya-spec/SKILL.md
Included Skills8
Build and run the citation-backed correctness suite for the Maya date project — sourced Long Count, Calendar Round, day-number and western-date vectors as language-agnostic data. Use when adding test vectors, investigating suspected calendar bugs, or differential-testing two implementations.
Gate, dispatch and collect a wave of parallel agents against a maya-plan wave. Use only when a plan exists and the fixture suite passes; it refuses to run otherwise.
Craft rules for writing code in the Maya date project — fixtures first, layer discipline, test and commit conventions. Use when implementing a work package or making any change to calendar logic, and hand it to every dispatched agent.
Load the current state of the Maya dates project (drewsonne/maya-*) — repo map, work in flight, blockers, and a few sized next actions. Use when picking the project back up or asking where things stand.
Decompose the Maya dates product spec into dependency-ordered work packages sized for independent parallel agent execution, then write them to docs/plan/ and GitHub Issues. Use after specs or ADRs settle and before dispatching any agents.
Write a settled decision or a sourced research finding for the Maya dates project into docs/decisions or docs/research as a numbered, citable markdown file. Use when reasoning should outlive the conversation.
Review a pull request on the Maya date project against its acceptance criteria, layer rules and fixture integrity before merge. Use on agent-authored and hand-written PRs alike, especially any touching calendar arithmetic.
Interview the Maintainer into a product spec for the Maya date calculator and write it to docs/product/. Use before planning work, or whenever what the product is for has drifted out of view.
Plugin manifests1
{
"name": "maya",
"displayName": "Maya Dates Project Skills",
"description": "Eight skills that run the Maya dates project: orient, spec, record, fixtures, plan, fleet, implement, review",
"version": "1.9.5",
"author": {
"name": "Drew Sonne"
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[maya on Agent Plugins Marketplace](https://pluginsmp.com/plugins/maya)