Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

orbitant-ai-readiness

Name: Orbitant Ai Readiness
Author: weorbitant

// Use when auditing whether a repo is configured for AI-assisted development — checking .claude/ setup quality, CLAUDE.md completeness, skills/agents presence, hooks, memory, or MCP server configuration. Activates when someone asks "is this repo AI-ready?", "how well is Claude configured here?", or wants to assess AI readiness before starting work on an unfamiliar project. Also trigger when reviewing any .claude/ config, CLAUDE.md quality, or hooks setup — even if the user doesn't explicitly mention "AI readiness".

Ejecutar en Manus

$ git log --oneline --stat

stars:3

forks:0

updated:27 de abril de 2026, 16:40

Explorador de archivos

2 archivos

SKILL.md

readonly

name	orbitant-ai-readiness
description	Use when auditing whether a repo is configured for AI-assisted development — checking .claude/ setup quality, CLAUDE.md completeness, skills/agents presence, hooks, memory, or MCP server configuration. Activates when someone asks "is this repo AI-ready?", "how well is Claude configured here?", or wants to assess AI readiness before starting work on an unfamiliar project. Also trigger when reviewing any .claude/ config, CLAUDE.md quality, or hooks setup — even if the user doesn't explicitly mention "AI readiness".
version	0.1.0
license	MIT
metadata	{"author":"orbitant","tags":"engineering, audit, ai-readiness, claude, dx"}

Overview

Audits a repo's AI readiness — how well it's configured for Claude Code and AI-assisted development. Produces a structured report with a rating and actionable findings.

All checks are static. No runtime access, no external APIs.

When to Use

Starting work on an unfamiliar repo and want to assess AI setup quality
Reviewing a client project before an engagement
Someone asks "is this repo ready for AI development?"
Running a section audit after /orbitant-engineering:ground-control flagged AI readiness issues

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/ai-readiness/references/ai-readiness.md

Then check the repo against every item in that file. Collect all findings before printing the report.

Output Format

## AI Readiness Audit   {rating}

### Passing
- CLAUDE.md present and substantive
- .claude/ directory exists
- ...

### Failing
- Agents not defined despite complex codebase
  Finding: No .claude/agents/ directory
  Recommendation: Define agents per sub-domain (API, frontend, infra)

### Improvement opportunities (Tier 3)
- Memory system not configured
- No MCP servers declared

Rating: ✅ Operational

Ratings: ❌ Not AI-ready / ⚠️ Minimal / ✅ Operational / 🚀 Optimized

See references/ai-readiness.md for full scoring criteria.

related-skills.json

mismo repositorio

orbitant-blog-post-create.md

from "weorbitant/orbitant-os"

Content generation skill for the Orbitant engineering blog. Activates when creating a blog post in Spanish from raw input — a Knowledge Sharing transcript, Slack thread, meeting notes, workshop draft, or bullet outline. Produces a structured, SEO-optimised article that matches Orbitant's narrative, tone, and content cluster strategy. Trigger on: "crear blog post", "redactar artículo", "convierte esto en un post", "blog post para Orbitant", "write a blog post", "turn this into an article". Also trigger when the user shares a long transcript, KS notes, or a Slack discussion about a technical decision — even if they don't explicitly say "blog post". When in doubt, ask if they want this turned into a post.

2026-05-223

orbitant-release-notes.md

from "weorbitant/orbitant-os"

Drafts structured, publication-ready release notes from git history. Activates when: creating releases, documenting version changes, drafting changelogs, or preparing release announcements. Use even when user just says "generate changelog", "what changed since last release", "help me write release notes", "prepare a release", or "I bumped the version". Also triggers after version bumps in plugin.json.

2026-05-213

orbitant-goal-alignment.md

from "weorbitant/orbitant-os"

Scores items against quarterly rocks from rocks.yaml. Activates during triage, task ranking, meeting prep, and scheduling. Flags drift when time allocation mismatches stated priorities.

2026-05-123

orbitant-graceful-degradation.md

from "weorbitant/orbitant-os"

Checks MCP servers and config files before any chief-of-staff command. Ensures no command hard-fails — always proceeds with available sources. Auto-activates on every command.

2026-05-123

orbitant-voice-drafting.md

from "weorbitant/orbitant-os"

Writes drafts in the user's voice using voice.md for tone and style. Activates during /triage, /crm, or any "draft an email/message" request. Never sends without confirmation.

2026-05-123

orbitant-debrief.md

from "weorbitant/orbitant-os"

Use at the end of a Claude Code session to capture project-specific friction as proposed CLAUDE.md edits. Triggered by /debrief (no args) to scan the full session, or /debrief <hint> to focus on a specific area (e.g., /debrief the API naming convention thing). Returning "session looks clean" with no proposals is a first-class outcome, not a fallback. Triggers on: "/debrief", "debrief the session", "wrap up this session", "what did we learn", "any rules to capture", "should we update CLAUDE.md".

2026-05-063

package.json

"author": "weorbitant"

"repository": "weorbitant/orbitant-os"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas15-1252L4

name	orbitant-ai-readiness
description	Use when auditing whether a repo is configured for AI-assisted development — checking .claude/ setup quality, CLAUDE.md completeness, skills/agents presence, hooks, memory, or MCP server configuration. Activates when someone asks "is this repo AI-ready?", "how well is Claude configured here?", or wants to assess AI readiness before starting work on an unfamiliar project. Also trigger when reviewing any .claude/ config, CLAUDE.md quality, or hooks setup — even if the user doesn't explicitly mention "AI readiness".
version	0.1.0
license	MIT
metadata	{"author":"orbitant","tags":"engineering, audit, ai-readiness, claude, dx"}

Overview

Audits a repo's AI readiness — how well it's configured for Claude Code and AI-assisted development. Produces a structured report with a rating and actionable findings.

All checks are static. No runtime access, no external APIs.

When to Use

Starting work on an unfamiliar repo and want to assess AI setup quality
Reviewing a client project before an engagement
Someone asks "is this repo ready for AI development?"
Running a section audit after /orbitant-engineering:ground-control flagged AI readiness issues

How to Run

Load the reference standards:

@plugins/orbitant-engineering/skills/ai-readiness/references/ai-readiness.md

Then check the repo against every item in that file. Collect all findings before printing the report.

Output Format

## AI Readiness Audit   {rating}

### Passing
- CLAUDE.md present and substantive
- .claude/ directory exists
- ...

### Failing
- Agents not defined despite complex codebase
  Finding: No .claude/agents/ directory
  Recommendation: Define agents per sub-domain (API, frontend, infra)

### Improvement opportunities (Tier 3)
- Memory system not configured
- No MCP servers declared

Rating: ✅ Operational

Ratings: ❌ Not AI-ready / ⚠️ Minimal / ✅ Operational / 🚀 Optimized

See references/ai-readiness.md for full scoring criteria.

orbitant-ai-readiness

Overview

When to Use

How to Run

Output Format

Más de este repositorio

Más de este repositorio

Overview

When to Use

How to Run

Output Format