Maintain portable Feature Track docs for project features. Use when designing, planning, implementing, reviewing, or finishing feature work; creating or updating PRD/API/design/implementation docs; adding a new feature; or validating docs/features.
Run Claude Code JavaScript Workflows through the awsl compatibility runtime. Use when an agent's current task or loaded Skill requires dispatching a Claude Code Workflow but the host cannot execute that Workflow natively, or when awsl workflow inspection, durable run state, resume, or provider diagnostics are needed.
A controlled workflow for completing one coding task and submitting an envelope: a record of files read, files changed, patches, checks, and uncertainties. The envelope is an honest summary of the work, not just the code patch.
An independent, read-only check for a code-fix report. It verifies that each claimed check was run against the real contract, rather than trusting a summary or allowing the fixer to alter its own evidence.
Write and run dynamic workflows: short JavaScript scripts in Claude Code's workflow dialect, run with the odw CLI outside the host agent's context, fanning subtasks out to coding-agent CLIs (Codex, Claude Code, Gemini, Qwen, Kimi, or your own) in a background process and handing back only the final result. Use this…
A way to write JavaScript workflows that send parts of a large task to separate coding-agent command-line programs and return only the final result. It supports multiple agents, stages, loops, and checks within one workflow.
Execute explicitly authorized Ultracode / Ultra Mode requests: optimize for exhaustive, correct answers within the user's stated scope by using any available independent-work mechanism (ODW workflows, subagents, dispatched workers, or tool-worker fan-out), with serial multi-pass fallback only when no such mechanism…
Query Lerim's persistent project context before agent work. Use it to check prior decisions, constraints, preferences, and historical context through exact queries or synthesized answers.
Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.
Analyze and safely optimize OpenSpec main specifications. Use when asked to find semantically duplicate Requirements or Scenarios, cluster related capabilities, enforce spec line/token budgets, or generate reviewable consolidation mappings and diffs without changing main specs automatically.
An API documentation generator that uses interfaces, data types, and examples to produce structured reference material. API means the defined way software programs communicate with each other.
Use this skill to create or improve README content. Cover what the project does, setup, common commands, configuration, development workflow, and troubleshooting.
Run one action in an outcome-loop folder. Use when the user wants to execute the outcome loop, start with Superdense reward maintenance, choose one action on a lever, create runs/ /work.md and learnings.md, or use prior outcomes to improve a real-world metric.
Set up or repair one outcome-loop folder for improving a real-world outcome. Use when the user wants to define goal.md, run.md, analytics/instrumentation, levers, target repos/accounts, or the folder contract for an outcome loop.
Find & read context prior AI-agent sessions. Use when the user asks about previous or other agent runs, needs context from earlier work, wants to understand what happened, compare attempts, audit decisions/tools/errors, plan-mode behavior, or access the original session record.
API authentication patterns including JWT, OAuth 2.0, API keys, and session-based auth. Covers token generation, validation, refresh strategies, security best practices, and when to use each pattern. Use when implementing API authentication, choosing auth strategy, securing endpoints, or debugging auth issues.…
LLM evaluation and testing patterns including prompt testing, hallucination detection, benchmark creation, and quality metrics. Use when testing LLM applications, validating prompt quality, implementing systematic evaluation, or measuring LLM performance.
Comprehensive guide to implementing RAG systems including vector database selection, chunking strategies, embedding models, and retrieval optimization. Use when building RAG systems, implementing semantic search, optimizing retrieval quality, or debugging RAG performance issues.
Build a trustworthy first ontology from an empty or near-empty ontology-atlas vault using only Atlas MCP evidence. Use when the user asks to analyze a codebase, bootstrap/fill its ontology, extract product meaning from a repository, or when a requested ontology task finds only starter nodes. Separate observed…
Measure whether Atlas actually works on a repository nobody here knows, by building a vault with a real MCP agent and then handing that vault — without the source — to a second agent who must answer questions from it alone. Use when changing the construction rules, the MCP read/write contract, the bootstrap skill, or…
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
Use when Agentplane task completion, direct finish, branchpr integration, hosted-close, close-tail PRs, PR metadata, dirty task artifacts, or remote branch divergence need diagnosis or recovery.
76 3d agoA46 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: