Loading...
Loading...
Found 4,154 Skills
Use skill if you are running many small Codex-native web searches through codex exec with per-question files and parseable answer artifacts.
Optimize conversion rates. Use when: auditing landing pages, testing forms, or improving checkout flow.
Track AI engine brand narratives. Use when: detecting narrative drift, misrepresentation, or competitor narrative gains over time.
Generate, refine, research, and validate startup ideas through an interactive founder-specific idea machine. Use when Codex needs to ask a few focused questions, search current public web signals, rapidly brainstorm startup or SaaS ideas, learn from love/maybe/no reactions, produce additional idea rounds, compare finalists, investigate competitors and existing workarounds, select a promising opportunity, or create an evidence-linked Markdown startup-idea report.
Use this when you need to execute R4 (generate an interactive Demo project based on requirements/prototype.md) in the sdlc-dev product requirement Spec process, and need to avoid skipping spec-context, proceeding when prototype.md is missing or the runnable Demo project root directory is missing, or creating custom pages/directories that lead to untraceability and inability to close the loop.
EIDE (Embedded IDE) project build tool, used to scan .eide/eide.yml projects, enumerate build configurations (ConfigName), execute build/rebuild/clean and parse build logs, returning artifact paths that can be reused by jlink/openocd. It is automatically triggered when users mention EIDE, Embedded IDE, eide.yml, unify_builder, VS Code EIDE Extension, or Cl.eide, and also supports explicit invocation via /eide. Even if users only say "Compile with EIDE" or "Burn to board via EIDE", this skill should be triggered as long as the context involves EIDE embedded projects.
Generate a Software Bill of Materials in CycloneDX or SPDX format. Use when producing SBOMs for compliance, supply chain transparency, or software composition analysis.
Create advanced MapleStory Worlds player attack and movement skills and preserve the project's monster combat presentation. Use for direct/projectile attacks, hit/die animation, damage-skin death hold, knockback pulses, monster ATTACK range/timing, custom player animation and cast locks, double jump, teleport/blink, cooldowns, hotkeys, or updates to the player/monster skill pipelines.
Sets up the translation supplements an IG-Publisher-based FHIR Implementation Guide needs for its non-default languages, putting each one exactly where the publisher reads it — either by translating from the default-language source or by harvesting an already-published rendering in the target language. The default language stays authoritative and every machine translation needs a bilingual human review. Use this skill when a guide builds green and an additional language rendering is wanted, when the /<lang>/ pages show the default language instead of the translation, when deciding where a .po supplement or a translated page belongs, or when the user mentions Übersetzung, translation supplement, input/translations, po file, i18n-lang or i18n-default-lang. Do not use for measuring or comparing guides, for migrating one onto the MII KDS module template, or for a template package's own language mechanism; see fhir-ig-analysis and mii-ig-migration.
Detect a project's toolchain, languages, package managers, test runners, linters, and conventions. Use when starting work on a project, onboarding to a codebase, or checking what tools are configured. Also detects tooling gaps and fetches external metadata.
Design and implement a systematic framework for informational elements that communicate state (Badges) and categorization (Tags) with clarity and accessibility.
Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.