immamdouhaboammar/omni-skill

Search for and leverage existing runtime primitives, standard libraries, repository utilities, and battle-tested ecosystem packages rather than building custom implementations. Use before authoring new helpers, utility functions, wrapper shims, or external client libraries.

Use when Skill Conductor needs to inspect, search, modify, or verify files in the active host workspace using the safest native capability available. Do NOT assume the plugin itself grants filesystem, shell, search, patch, or Python access.

Understand human cognitive models, reading patterns, implicit assumptions, and intent formulation. Use when drafting text or documentation intended for humans, eliciting user design decisions, interpreting user feedback, or designing collaborative agent-human workflows.

Protocol for adopting a new library, tool, or architectural pattern. Ensures that introduction does not stop at installation, but mandates full migration of existing call sites, mechanical enforcement preventing legacy usage, standardization on a single pattern, and deletion of deprecated code. Use when adding or replacing dependencies, frameworks, utilities, or architectural standards.

Establish hypotheses and measurable verification criteria before implementing changes or diagnosing bugs, and decide strictly based on measured outcomes. Use when investigating bug causes, comparing performance, optimizing latency, choosing between architectures, or whenever tempted to make decisions based on guesswork.

Route a skill-engineering request to the next useful specialist. Use when creating, improving, evaluating, adapting, packaging, or distributing agent skills, including requests in Arabic. Do not activate for unrelated app coding, everyday writing, or merely running an already configured skill.

Apply the 24 battle-tested engineering principles for architecture design, refactoring, implementation, bug diagnosis, migration, and verification. Use when deciding technical tradeoffs, structuring systems, writing tests, or reviewing code changes.

Craft high-presence open-source repositories and configure universal multi-agent distribution manifests, GitHub discovery metadata, and automated installers. Use when the user asks to prepare a repository for publishing, configure skill distribution for Claude Code, Skills.sh, npm, or Cursor, generate aesthetic README diagrams and badges, or set up multi-agent installers — even if they don't explicitly say "distribute skill" or "repo crafter". Do NOT use for general git branching, conflict resolution, or writing code implementation.

Use when a Skill Conductor workflow needs deterministic computation, file generation, parsing, package inspection, hashing, or validation that should be actually executed with host-native Python.

Set up OmniSkill after installation or check which skill workflows this host can execute. Use for first-run onboarding and capability troubleshooting, not for a general coding environment installation.

Architect a new agent Skill or convert an existing prompt, SOP, playbook, runbook, workflow, or repeated agent behavior into a durable Skill. Use when the main problem is deciding what the Skill should contain, how it should activate, which architecture and freedom levels fit, and how to separate instructions, references, scripts, and host adapters. Do NOT use when the user only wants to run an existing Skill or only wants behavioral evaluation of an already-frozen Skill.

Create, refine, audit, and evaluate Agent Skills according to the AgentSkills.io v1 specification and Poteto principles. Use when building a new skill, rewriting an existing skill, structuring SKILL.md, or enforcing quality gates on skill directories.

Coordinate skill improvement and packaging loops. Use when a skill needs evidence-based trigger tuning, bounded iterative improvement, or package preparation. For original authoring, use skill-architect or skill-authoring.

Evaluate an agent Skill for activation accuracy, instruction compliance, outcome quality, efficiency, pressure resistance, and regression risk. Use when testing a new Skill, diagnosing an unreliable Skill, comparing versions, validating a claimed improvement, creating held-out evals, or deciding whether a Skill is behaviorally ready. Do NOT use as a substitute for actually executing tests when the active host cannot run them.

Port an agent Skill across ChatGPT, Codex, Claude, API agents, or another compatible host without losing its decision logic, evidence gates, activation boundary, or completion conditions. Use when a Skill is tied to one vendor's paths, tool names, keys, hooks, subagents, packaging, or runtime assumptions and needs a portable core plus host adapters. Do NOT claim a host is behaviorally supported unless that host was actually tested.

Standards and guidelines for drafting high-density, anti-slop technical documentation, PR summaries, commit messages, architectural records, and agent instructions. Use when writing, editing, or polishing documentation and instructions, or to remove AI writing tropes, unnecessary conversational preambles, and low-density filler.