Game Guide Generator · publiczny skill Open Skill
Game Guide Generator
Game Guide Generator to publiczny Open Skill w Digen. Otwórz go, by zobaczyć, co tworzy ten workflow.
Anime
0 2 9
https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/4023697/2026-09-04/7zscynx6.png
# Game Guide Generator ## When to use - The user provides a game name, character name, character description, and/or uploads a character image, and wants a detailed, well-structured guide (overview, lore, abilities, strengths/weaknesses, builds, strategies, tips, recommendations). - The user uploads a character image and wants the character (and game) identified and turned into a full guide. - The user wants an existing guide from this session revised, expanded, shortened, translated, or re-focused. ## Steps ### 1. Gather input - Collect whatever the user provides: game name, character name, description, and/or uploaded character image (use its asset_id or URL). - Determine which identification cues are available: explicit name, description, or image. ### 2. Identify the game and character - If an image is provided: call `recognize_image` on it with a prompt like: "Identify this character if possible (name, game, role, and notable visual traits: outfit colors, weapon, hair, species, markings). If unknown, describe the visual appearance in detail so it can be matched to a game." - Combine the image read with any name/description the user gave. - If the identity is still uncertain, use `search_web` (e.g. query the description plus likely genre: "blue-haired archer fox mask gacha character name"). - If identification is ambiguous, ask the user one short confirming question, or clearly label the guide with the assumption (e.g. "Assumed character: X — tell me if that's wrong") before writing the full guide. ### 3. Research - Use `search_web` with several targeted queries to ground the guide: "<character> <game> lore", "<character> abilities kit", "<character> build guide", "<character> strengths weaknesses counters", "<character> gameplay tips", and meta/patch notes when relevant. - Keep notes on what is verified from search results vs. what comes from general knowledge; never invent quotes, stats, or URLs. ### 4. Write the guide Create a clearly structured Markdown document. Adapt headings to the game genre (MOBA, RPG, shooter, fighting, etc.) while keeping this core layout: 1. **Character Overview** — who they are, role/archetype, one-paragraph summary, difficulty rating (e.g. 1–5). 2. **Lore & Background** — origins, backstory, personality, notable relationships/factions. 3. **Abilities / Skills** — full kit: name, what it does, key mechanics, and how it's meant to be used. 4. **Strengths** — what the character excels at (power spikes, favorable matchups, team roles). 5. **Weaknesses** — counters, bad matchups, resource/positioning constraints, skill ceiling. 6. **Recommended Builds** — 2–3 variants: beginner-friendly, optimal/meta, and a situational/budget option; explain why each works (items, weapons, runes, loadouts, team comps). 7. **Strategies** — early/mid/late game plan, combo rotations, positioning, team synergy, matchup tips. 8. **Gameplay Tips** — concrete dos and don'ts, common mistakes, practice advice, settings/controls tips if relevant. 9. **Useful Recommendations** — verdict on who this character suits, plus 2–3 similar characters to try next if applicable. - Write the guide in the same language as the user's message. - Keep it detailed but skimmable: headings, bullet lists, and bolded key terms. - If search results are thin, fill from general knowledge but mark those sections as "general knowledge — verify against current patch notes". - Note anywhere the meta may be patch-dependent and advise checking current patch notes. ### 5. Deliver - Save the guide with `create_document` using a fixed pattern: - `name`: `Guide — <Character> (<Game>)` (e.g. "Guide — Yuumi (League of Legends)") - `entity_type`: `guides` - `content_type`: `text/markdown` - Reply in chat with a short summary: the identified character/game (or the assumption used), the section list, and 2–3 highlight recommendations; point to the new document card. ## Revising an existing guide - When the user asks to change the guide (more deta