Who it is forA developer whose Codex Skills worked before and may now break under GPT-6/Astra behaviour changes, and who needs the next maintenance decision quickly.
The problemSkills written for earlier behaviour can carry outdated constraints that nobody has checked against GPT-6/Astra.
The outcomeA plain-language audit that names the current problem, what an improvement would change, and one next step, with no files changed.
What you need first
- Git
- Codex with local plugin support
- Python 3 for the requirement-ledger CLI, installed with uv or pip
- A local project folder to select as the target
Steps
- Run
git clone https://github.com/adand-91/gpt-6-astra-skill.gitand thencd gpt-6-astra-skill. - Run
codex plugin marketplace add "$PWD"from the checkout. - Run
codex plugin add gpt6-astra-skill-optimizer@requirement-ledger-local. - Select one project, start a fresh Codex task, and ask: "Please audit this project and its related Skills for GPT-6/Astra. Explain the current problem, what an improvement would change, and one next step."
Prompt for your agent
In the gpt-6-astra-skill repo's Codex plugin, audit the project at <project-path> and its related Skills for GPT-6/Astra. Return the current problem, what an improvement would change, and one next step. Verify that the audit made no file changes before accepting the result.
Caveat. The plugin is a thin Skill workflow, and complete GPT-6/Astra adaptation still requires real project feedback, while the full Jarvis experience is a long-term goal.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for adand-91/gpt-6-astra-skill and "Audit a project's Skills for GPT-6/Astra in Codex"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer