Update to Dyslex.ai

{
  "name": "accessible-response",
  "description": "Adapt an AI response for dyslex.ai readability. Use when a user asks for clearer, easier-to-read, less overwhelming, more structured, or accessibility-oriented wording without losing technical detail.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 216
    }
  ],
  "skill_md_contents": "---\nname: accessible-response\ndescription: Adapt an AI response for dyslex.ai readability. Use when a user asks for clearer, easier-to-read, less overwhelming, more structured, or accessibility-oriented wording without losing technical detail.\n---\n\n# Accessible Response\n\n## Superpowers Gate\n\nBefore applying this skill, verify that Superpowers is available in the current session, such as an active `superpowers:` skill, `using-superpowers`, or equivalent Superpowers workflow instructions.\n\nIf Superpowers is missing or uncertain, stop and reply exactly with this guidance before doing any dyslex.ai work:\n\n```text\ndyslex.ai requires Superpowers before it can run. Install Superpowers from /plugins, or use codex plugin add superpowers@<marketplace> if you manage plugins from the Codex CLI, then start a new session.\n```\n\nDo not perform the requested dyslex.ai workflow until Superpowers is installed and loaded.\n\nRewrite or present the response so it is easier to scan and decode.\n\n## Rules\n\n- Preserve meaning, decisions, caveats, file names, commands, code identifiers, and numbers.\n- Use short paragraphs and descriptive headings when they help.\n- Prefer exact nouns over unclear pronouns like \"it\", \"this\", or \"that\".\n- Explain acronyms the first time they appear when the explanation is useful.\n- Split long instructions into numbered steps only when order matters.\n- Do not add a medical claim, diagnosis, excessive praise, emojis, or a childish tone.\n\n## Output\n\nKeep all important information. Change only presentation and wording.\n\nWhen technical precision matters, add a short `Unchanged technical tokens` note if tokens were protected.\n"
}