{"id":48267,"plugin_id":"plugin_asdk_app_6a4d07cf0b208191bbb509c02fb72ee2","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:35:53.852Z","digest":"8284d4ffb1cf88625c50c8bc007414e4ae16f0c462e227faaea82671f98695e5","against":null,"payload":{"description":"Turn user-provided goals, notes, or procedures into a concise interactive how-to guide using the display-guide tool. Use when the user explicitly asks for a guide, checklist, structured steps, or guide widget, including requests to reorganize existing instructions. Do not trigger for general advice, explanations, or casual how-to questions that do not request structured guide presentation.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":212}],"name":"guide-authoring","skill_md_contents":"---\nname: guide-authoring\ndescription: Turn user-provided goals, notes, or procedures into a concise interactive how-to guide using the display-guide tool. Use when the user explicitly asks for a guide, checklist, structured steps, or guide widget, including requests to reorganize existing instructions. Do not trigger for general advice, explanations, or casual how-to questions that do not request structured guide presentation.\n---\n\n# Guide Authoring\n\nCreate a grounded, easy-to-follow guide and present it with `display-guide`.\n\n## Workflow\n\n1. Identify the outcome, audience, starting point, and constraints from the request.\n2. Ask only for details whose absence would make the procedure unsafe, incorrect, or unusable. Otherwise, keep assumptions minimal and disclose material ones in `notes`.\n3. Ground the procedure in the user's supplied information and reliable context. Verify volatile or high-stakes facts with authoritative sources when tools are available; never fill a material gap by guessing.\n4. Organize the content into the supported guide fields.\n5. Review the complete procedure for safety, order, and completeness.\n6. Call `display-guide` once with the finished guide and a concise `reason`.\n\nIf a safe and useful procedure cannot be produced, do not call the tool. Ask for the missing information or explain the limitation instead.\n\n## Map The Guide\n\n- `requirements`: List only prerequisites, materials, tools, access, or conditions needed before work begins.\n- `preparation`: List actions that make the user ready to start, such as setup, backups, isolation, or preheating.\n- `instructions`: Provide the required, ordered actions that accomplish the outcome. Include at least one item.\n- `wrapUp`: List verification, testing, cleanup, restoration, storage, or next actions after the main procedure.\n- `tips`: Include optional advice, shortcuts, alternatives, or troubleshooting hints that are not required checklist actions.\n- `notes`: Record concise warnings, assumptions, limitations, or context that does not belong in a checklist.\n\nOmit optional fields that add no value. Do not invent unsupported fields such as a title, duration, difficulty, nested steps, or per-step metadata.\n\n## Write Effective Steps\n\n- Start each checklist item with a clear imperative verb.\n- Keep one observable action or tightly coupled action group per item.\n- Order prerequisites and safety controls before the actions that depend on them.\n- Make each item understandable without relying on ambiguous words such as \"it\" or \"that.\"\n- Use concrete completion cues where they materially reduce uncertainty.\n- Keep optional advice out of required checklist sections.\n- Avoid embedded numbering because the widget orders the steps.\n- Avoid headings, duplicate actions, and unnecessary prose inside list items.\n- Preserve meaningful qualifications from the source instead of simplifying away safety or correctness.\n\n## Validate Before Display\n\nConfirm that:\n\n- `instructions` is a non-empty array of non-empty strings.\n- Every listed requirement is actually used, and every required prerequisite appears before use.\n- The sequence has no unexplained jumps, contradictions, or unsafe implied actions.\n- Verification and cleanup appear in `wrapUp` when the task needs them.\n- Warnings and assumptions are visible without making the guide sound more authoritative than its sources support.\n- The guide contains no secrets or sensitive details that should not be copied or shared from the widget.\n\nAfter invoking `display-guide`, do not repeat the entire guide in conversation unless the user asks for a text version.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}