
Crawl from one or more starting web pages, fetch readable content, search within pages, follow relevant links, and stop when the requested information is found or a bounded limit is reached.
# Guidance ## Choose This Skill When - This skill is being used deliberately for widget development, testing, or UI debugging. ## Resolve With Context - Keep the behavior scoped to the widget or playground scenario being tested. ## Avoid - Do not route normal owner requests here.
# Guidance ## Choose This Skill When - The owner wants to create, adjust, or preview a synthesized voice design workflow supported by this skill. ## Resolve With Context - Preserve the current voice settings and generated artifacts across follow-up turns. - Ask for the missing voice attribute only when the current skill context cannot supply it. ## Avoid - Do not guess subjective voice preferences that the owner has not stated.
# Guidance ## Choose This Skill When - The owner wants a video summarized after downloading or transcribing its content. ## Resolve With Context - Reuse the downloaded media, extracted audio, and transcription paths from the current workflow. - If the summary language or source path is missing, ask for it instead of guessing. ## Avoid - Do not restart upstream download or transcription steps if the workflow artifacts already exist and remain relevant.
# Guidance ## Choose This Skill When - The owner explicitly needs live web retrieval, search, or page analysis through this skill. ## Resolve With Context - Use the current task objective to choose the narrowest useful retrieval step. - Prefer existing workflow context over repeating the same search. ## Avoid - Do not use this skill when a non-web local answer is sufficient. - Do not broaden the search goal beyond the owner request.
# Guidance ## Choose This Skill When - The owner wants to generate a podcast-style output from provided source material. ## Resolve With Context - Preserve the current source inputs, generation settings, and intermediate artifacts across the workflow. - Ask for missing source material instead of inventing it. ## Avoid - Do not treat vague brainstorming as a generation request. - Do not overwrite an existing generation flow unless the owner clearly wants a restart.
# Guidance ## Choose This Skill When - The owner asks about Leon age or how old Leon is. ## Resolve With Context - Answer directly and briefly. - If the owner combines this with another request, prefer the more substantive task. ## Avoid - Do not route general biography or technical questions here.
# Guidance ## Choose This Skill When - A workflow needs audio transcription, dubbing, or vocal and instrumental separation. - The owner explicitly requests one of those audio-processing operations. ## Resolve With Context - Reuse audio paths and prior workflow artifacts from the current skill context when available. - For dubbing, require a target language that can be mapped to Leon canonical language list. ## Avoid - Do not use this skill for general music discussion. - Do not silently conti
# Guidance ## Choose This Skill When - The owner wants Leon to create, revise, or reason about Leon-native skills. ## Resolve With Context - Prefer the current Leon workflow architecture and top-level _skill structure. - Prefer declared action parameters and context_data over legacy entity-driven action code. - Keep outputs aligned with Leon existing bridges, skill.json, locales, and action folders. ## Avoid - Do not generate legacy category-based skills. - Do not reintroduce deprecated custo
# Guidance ## Choose This Skill When - The owner wants to set, check, or cancel a timer. ## Resolve With Context - Setting a timer requires a concrete duration value plus unit. - Checking or canceling should prefer the active timer state already held by the skill. ## Avoid - Do not start a timer from a vague request with no duration. - Do not create multiple interpretations when the owner clearly refers to the current timer.
# Guidance ## Choose This Skill When - The owner wants to translate a video speech track into another language through the full Leon workflow. ## Resolve With Context - Preserve workflow artifacts across steps: downloaded video, extracted audio, transcription, speaker references, and dubbed output. - Reuse the active target language from the current skill context unless the owner explicitly changes it. - Prefer continuing the current workflow over restarting it. ## Avoid - Do not silently ski
# Guidance ## Choose This Skill When - The owner wants to take the MBTI-style quiz or receive the associated personality result. ## Resolve With Context - Keep the quiz flow sequential and preserve prior answers from the active skill context. - Only move to the result once the required quiz state is complete. ## Avoid - Do not infer missing quiz answers from tone or prior conversation. - Do not route unrelated psychology questions here.
# Guidance ## Choose This Skill When - The owner asks for the current date, time, or a simple time-related fact supported by this skill. ## Resolve With Context - Answer directly with the requested date or time information. - Reuse the current locale and time context when relevant. ## Avoid - Do not route scheduling or timer workflows here.
# Guidance ## Choose This Skill When - The owner wants a forecast for a place and optionally a specific day or time window. ## Resolve With Context - Prefer an explicitly stated location. - Reuse the active location or forecast horizon from the current skill context only when the owner is clearly following up. ## Avoid - Do not assume a location if none was provided or grounded in the active conversation. - Do not answer historical climate questions with this forecast skill.
# Guidance ## Choose This Skill When - The owner asks Leon to introduce itself or asks who Leon is. ## Resolve With Context - Keep the introduction concise. - If the owner includes a concrete follow-up task, shift to the task instead of staying in introduction mode. ## Avoid - Do not treat a greeting as a full introduction request unless the owner asks for it.
# Guidance ## Choose This Skill When - The owner asks Leon to generate a random number. ## Resolve With Context - Prefer explicit bounds when the owner provides them. - If the skill only supports a narrow random-number pattern, keep the interpretation within that contract. ## Avoid - Do not treat unrelated numeric questions as a random-number request.
# Guidance ## Choose This Skill When - The owner asks about Leons favorite color or asks for a colors hexadecimal code. ## Resolve With Context - For hexadecimal lookups, require a concrete color name. - Normalize simple color-name variants, but do not guess a color that was not provided. ## Avoid - Do not use this skill for general color theory or design advice. - If the requested color is unknown to the skill color map, fail clearly instead of fabricating a code.
# Guidance ## Choose This Skill When - The owner wants to start or continue the guess-the-number game. ## Resolve With Context - During the game loop, a bare number should usually continue the current guessing action. - Treat replay as a yes or no decision only after the game has completed. ## Avoid - Do not restart the game if the owner is obviously continuing an active round. - Do not treat unrelated numbers as a guess when the game context is inactive.
# Guidance ## Choose This Skill When - The owner wants to check whether an email address appears in Have I Been Pwned. ## Resolve With Context - Require a concrete email address. - Keep the response factual and breach-focused. ## Avoid - Do not guess an email address from surrounding context.
# Guidance ## Choose This Skill When - The owner wants to know whether a specific website or domain is down. ## Resolve With Context - Require a concrete website or domain. - Reuse the active domain only for clear follow-up checks. ## Avoid - Do not guess the website when the owner is vague.
# Guidance ## Choose This Skill When - The owner explicitly asks for a joke. ## Resolve With Context - Deliver the joke directly. - If the owner asks for another one, stay in the same lightweight mode. ## Avoid - Do not route broader comedy or storytelling requests here unless they are clearly just a joke request.
# Guidance ## Choose This Skill When - The owner wants to start or continue a rock-paper-scissors game. ## Resolve With Context - During the game loop, short replies like rock, paper, or scissors should continue the current play action. - Reserve rematch handling for the post-round yes or no step. ## Avoid - Do not treat unrelated mentions of rock, paper, or scissors as gameplay outside the active skill context.
# Guidance ## Choose This Skill When - The owner explicitly wants to run a network speed test. ## Resolve With Context - Treat this as an operational measurement request. - Keep follow-up answers tied to the current test result. ## Avoid - Do not use this skill for general network troubleshooting unless the owner specifically asked for a speed test.
# Guidance ## Choose This Skill When - The owner wants to play Akinator or continue an active Akinator round. ## Resolve With Context - Use `guess` only while an Akinator question is already on screen. - Keep short follow-up replies like yes, no, probably, or don't know inside the current Akinator round. - After Akinator has made a guess, treat a short yes or no as the retry decision, not as another guess answer. ## Avoid - Do not route generic guessing questions or trivia to this skill. - Do
# Guidance ## Choose This Skill When - The owner wants to create, inspect, update, or complete todo items. ## Resolve With Context - Reuse the active list or task references from the current skill context when the owner says things like that one or the last task. - Ask for the missing task identifier only when context does not ground it. ## Avoid - Do not treat general planning talk as an explicit todo operation. - Do not delete or complete items unless the intent is clear.
# Guidance ## Choose This Skill When - The owner asks what Leon can do or how Leon can help. ## Resolve With Context - Keep the answer oriented around current Leon capabilities. - Prefer practical examples over abstract descriptions. ## Avoid - Do not hijack concrete task requests into a generic help response.
# Guidance ## Choose This Skill When - The request is specifically about the partner-assistant workflow supported by this skill. ## Resolve With Context - Reuse active partner-assistant state from the current skill context before asking again. - Prefer clear, bounded next steps over open-ended conversation. ## Avoid - Do not use this skill as a generic fallback assistant. - Do not infer sensitive relationship details that were never provided.
# Guidance ## Choose This Skill When - The owner explicitly asks about the meaning of life in the playful Leon sense. ## Resolve With Context - Treat this as a lightweight, personality-driven answer. ## Avoid - Do not route serious philosophical discussions here when the owner is clearly seeking depth.