Agentistry CLI
This skill teaches you how to use the Agentistry CLI (agentistry) to interact with the Agentistry marketplace — an open skill marketplace for AI agent developers.
When to Use This Skill
Use this skill when the user:
- Wants to search for agent skills ("find a skill for X", "is there a skill for X")
- Wants to install a skill ("add skill X", "install X")
- Wants to submit or publish their own skill
- Asks about the Agentistry marketplace or CLI
- Wants to manage their submissions or check submission status
- Mentions "agentistry" by name
Installation
npm install -g agentistry
Commands Reference
Search for skills
agentistry search [query]
Options:
--target claude_code|mcp— filter by target platform--limit N— max results (default: 20)
Examples:
agentistry search react # find React-related skills
agentistry search "code review" # find code review skills
agentistry search --target mcp # only MCP skills
agentistry search --limit 5 test # top 5 testing skills
Output shows each skill's slug, version, supported targets, and summary.
Install a skill
agentistry add <slug>
Options:
--target claude_code|mcp— install target (default:claude_code)--global— install at user level (~/.claude/skills/<slug>/) instead of project level (.claude/skills/<slug>/)--dir <path>— override install directory
Examples:
agentistry add frontend-design # install to project
agentistry add next-best-practices --global # install globally
agentistry add my-skill --dir ./custom/ # custom directory
Authenticate
agentistry login # opens browser for authentication
agentistry logout # remove stored credentials
Authentication is required for submitting skills. Credentials are stored at ~/.config/agentistry/credentials.json.
Submit a skill
agentistry submit <path> --name <skill-name> [--skill-version <version>] [--poll]
Options:
--name(required) — skill name--skill-version— semantic version (default:1.0.0)--poll— wait and poll until submission reaches a terminal status (approved/rejected/failed)
The directory must contain a SKILL.md file. Limits: max 50 files, 500 KB total. Hidden and binary files are skipped.
Example:
agentistry submit ./my-skill --name "my-skill" --skill-version 1.0.0 --poll
List submissions
agentistry submissions [--limit N]
Shows your submissions with ID, name, status, and creation date.
Creating a Skill
A skill is a directory with a required SKILL.md file:
my-skill/
├── SKILL.md # Required — frontmatter + markdown instructions
├── scripts/ # Optional helper scripts
├── docs/ # Optional documentation
└── other-files/ # Any supporting resources
SKILL.md Format
# My Skill
Instructions, workflows, and guidelines go here in markdown.
Required fields:
name— unique skill identifier
Optional fields:
description/summary— what the skill does (used for search and triggering)supported_targets— list ofclaude_code,mcplicense_spdx— valid SPDX license ID (e.g., MIT, Apache-2.0)tags— categorization tags
Submission Pipeline
After submitting, a skill goes through automated checks:
- Schema check — validates SKILL.md structure and required fields
- License check — validates SPDX license ID if provided
- Secrets check — scans for credential patterns (API keys, tokens)
- Malware check — scans for suspicious code patterns (eval, exec, shell injection)
Status flow: pending_ingestion → ingesting → checks_running → ready_for_review → approved or rejected
Full Workflow Example
# 1. Create the skill
mkdir my-react-skill && cd my-react-skill
# ... create SKILL.md and supporting files ...
# 2. Authenticate
agentistry login
# 3. Submit for review
agentistry submit . --name "my-react-skill" --skill-version 1.0.0 --poll
# 4. Once approved, users can discover and install it
agentistry search react
agentistry add my-react-skill
Environment Variables
AGENTISTRY_API_URL— override API base URL (default:https://api.agentistry.dev)AGENTISTRY_FRONTEND_URL— override frontend URL (default:https://agentistry.dev)
Tips
- Use specific keywords when searching for better results
- Install skills globally (
--global) for tools you use across projects - Install skills locally (default) for project-specific workflows
- Use
--pollwhen submitting to see real-time status updates - Keep skills focused — one skill per domain or workflow