Skip to content

imMamdouhaboammar/chatgpt-codex-plugin-autopilot / skills/agentic-repo-discovery

agentic-repo-discovery

Verified

Use when an existing repository contains agents, prompts, workflows, playbooks, commands, or Skills and you need to identify which capabilities are worth converting into a ChatGPT/Codex Plugin.

Agentic Repo Discovery

Find the reusable user workflows inside a repository before creating Plugin files.

Procedure

  1. Read repository instructions and the main README first.
  2. Run the bundled analyzer when filesystem execution is available:
python3 ../chatgpt-codex-plugin-autopilot/scripts/analyze_repo.py <target-repo> --json
  1. Inspect high-scoring candidates in context. The analyzer finds signals; it does not understand the full product by itself.
  2. Build a candidate disposition table using: preserve_skill, compile_skill, reference_only, runtime_dependency, internal_only, or discard.
  3. Identify the user's repeatable job for every candidate. Reject candidates whose only value is repository maintenance trivia unless that is the intended Plugin product.
  4. Flag secrets, organization-specific instructions, destructive operations, security-sensitive workflows, hidden telemetry, and policy-sensitive capabilities for explicit public-distribution review.
  5. Recommend skills-only, MCP-backed, or hybrid from actual behavior. Treat .mcp.json or .app.json as evidence to inspect, not automatic proof that the public Plugin needs them.
  6. Hand selected workflow candidates to workflow-to-skill-compiler and the overall product boundary to plugin-experience-architect.

Output

Return a concise conversion brief containing:

  • repository/ref inspected
  • reusable jobs discovered
  • candidate dispositions with reasons
  • architecture recommendation with confidence
  • runtime dependencies
  • public exclusions
  • missing evidence
  • next conversion actions

Do not generate Plugin configuration before this boundary is clear.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall