Run any Skill in Manus with one click

adapt-claude-to-agents

Stars2

Forks0

UpdatedMay 26, 2026 at 03:51

Generate or refresh a project-local AGENTS.md.tmpl for Praxion Codex onboarding from a project's root CLAUDE.md: removes Claude-only operational details, preserves portable project guidance. Triggers: install.sh codex needs a Codex source template, refreshing a previously generated Codex project template.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

francisco-perez-sorrosal

francisco-perez-sorrosal/praxion

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	adapt-claude-to-agents
description	Generate or refresh a project-local AGENTS.md.tmpl for Praxion Codex onboarding from a project's root CLAUDE.md: removes Claude-only operational details, preserves portable project guidance. Triggers: install.sh codex needs a Codex source template, refreshing a previously generated Codex project template.
allowed-tools	["Read","Write","Edit","Bash"]
compatibility	Codex, Claude Code, Cursor, and installer-driven CLI workflows.

Adapt Claude To Agents

Generate a project-local Codex template source from a project's root CLAUDE.md. The output is AGENTS.md.tmpl, not the final compiled AGENTS.md.

Workflow

Read the project's root CLAUDE.md.
Preserve portable project guidance: project description, repository layout, build/test commands, verification paths, and cross-project conventions.
Remove or rewrite Claude-only operational details that do not belong in a Codex project template.
Write a reviewable AGENTS.md.tmpl that can be merged with Praxion's shared Codex baseline.

Bundled Script

Use scripts/claude_to_agents.py for deterministic generation during install.sh codex. The installer may call the script directly; the output still follows this skill's workflow and contract.

Guardrails

Treat AGENTS.md.tmpl as project-local source.
Treat final AGENTS.md as compiled output.
Do not copy Praxion's shared Codex baseline into the generated project template.
Favor conservative removal over speculative rewriting when Claude-only details are ambiguous.

Related Skills

rule-crafting — when authoring new rules that need Codex portability annotations.

More from this repository

same repository

cicd

francisco-perez-sorrosal/praxion

CI/CD pipeline design and GitHub Actions workflow authoring: pipeline architecture, testing stages, deployment strategies, caching, secrets management, security hardening, performance optimization. Triggers: creating CI/CD pipelines, writing GitHub Actions workflows, configuring automated testing, setting up deployment automation, debugging workflow failures, optimizing pipeline performance, reviewing CI/CD config, designing deployment pipelines, implementing build automation.

2026-07-032

deployment

francisco-perez-sorrosal/praxion

Application deployment: Docker Compose (watch mode, profiles, GPU passthrough, health checks), PaaS, cloud containers, Kubernetes, AI-native GPU platforms, reverse proxy, secrets management, AI/ML model serving. Triggers: deploying an app, writing compose.yaml or Dockerfile, choosing a hosting platform, configuring Caddy/nginx, deploying Ollama/vLLM, GPU passthrough, choosing Render/Railway/Fly.io/ Vercel, managing Railway environments or PR environments, wiring Railway's agent plugin/MCP/CLI, deploying to Cloud Run/ECS/Modal/CoreWeave, writing systemd units for Compose. Siblings: cicd-engineer (pipeline automation), observability (monitoring).

2026-07-032

software-planning

francisco-perez-sorrosal/praxion

Planning complex software tasks via a three-document model (IMPLEMENTATION_PLAN.md, WIP.md, LEARNINGS.md) in small, known-good increments. Triggers: starting significant development, breaking down complex features, architecture planning, multi-session projects, feature breakdown, work planning, task tracking, WIP management, incremental development. Language modules available for Python, TypeScript.

2026-07-022

spec-driven-development

francisco-perez-sorrosal/praxion

Behavioral specification methodology with requirement traceability for medium and large features: spec format (When/and/the system/so that), complexity triage (trivial through spike), REQ ID conventions, REQ-* traceability threading through the pipeline, decision documentation, spec archival. Triggers: behavioral specifications, requirement traceability, SDD methodology, spec format, REQ IDs, spec-driven development, complexity triage, spec archival.

2026-07-022

agent-readiness

francisco-perez-sorrosal/praxion

Interpret and act on the Agent Readiness score produced by /project-metrics: 8 Factory pillars × 5 maturity levels × 80%-per-level gate + Praxion-native Pillar 9 Manageability sub-score. Read the readiness block from METRICS_REPORT_*.json, understand the LLM-judged criteria (naming_conventions, test_quality, readme_quality, docs_agent_friendliness), prioritize remediation by failing criterion → pipeline handoff, and interpret level-by-level progress. Triggers: reading or acting on an agent readiness report, understanding why a project scored a given level, deciding how to improve readiness, interpreting mechanical vs LLM criteria, running readiness without an API key, grounding a new readiness run on a prior report.

2026-06-292

goal-disambiguation

francisco-perez-sorrosal/praxion

Task-intake protocol for turning a fuzzy user request into an unambiguous, verifiable goal before committing to a direction. Covers the ask-vs-proceed decision rule (the 2x2 of intent-clarity x reversibility), lexical ambiguity detection, the XY-problem test, assumption surfacing over interrogation, Mom-Test question phrasing with a hard 3-question cap, and capturing measurable outcome signals (Intent / Key Signals / Health Guards / Uncertainty Flag) into a TASK_BRIEF.md that seeds downstream architecting, planning, testing, and verification. Triggers: at the start of any non-trivial task when the request is vague, implementation-first, or its success is not measurable; deciding whether to ask the user a clarifying question or proceed with stated assumptions; capturing acceptance criteria / definition-of-done at intake; reducing rework from misread intent.

2026-06-272

name	adapt-claude-to-agents
description	Generate or refresh a project-local AGENTS.md.tmpl for Praxion Codex onboarding from a project's root CLAUDE.md: removes Claude-only operational details, preserves portable project guidance. Triggers: install.sh codex needs a Codex source template, refreshing a previously generated Codex project template.
allowed-tools	["Read","Write","Edit","Bash"]
compatibility	Codex, Claude Code, Cursor, and installer-driven CLI workflows.

Adapt Claude To Agents

Generate a project-local Codex template source from a project's root CLAUDE.md. The output is AGENTS.md.tmpl, not the final compiled AGENTS.md.

Workflow

Read the project's root CLAUDE.md.
Preserve portable project guidance: project description, repository layout, build/test commands, verification paths, and cross-project conventions.
Remove or rewrite Claude-only operational details that do not belong in a Codex project template.
Write a reviewable AGENTS.md.tmpl that can be merged with Praxion's shared Codex baseline.

Bundled Script

Use scripts/claude_to_agents.py for deterministic generation during install.sh codex. The installer may call the script directly; the output still follows this skill's workflow and contract.

Guardrails

Treat AGENTS.md.tmpl as project-local source.
Treat final AGENTS.md as compiled output.
Do not copy Praxion's shared Codex baseline into the generated project template.
Favor conservative removal over speculative rewriting when Claude-only details are ambiguous.

Related Skills

rule-crafting — when authoring new rules that need Codex portability annotations.