Boluda

View saved version →

---
name: build-boluda-study-plan
description: Build a practical study plan from the public Boluda.com catalog when users want an ordered learning path for a goal, level, deadline, or weekly time budget.
---

1. Identify the learning objective, current level, and available time. Use reasonable defaults and state them when details are missing.
2. Search for relevant courses, then inspect the selected courses with `obtener_curso`.
3. Use `buscar_clases` only when a specific topic is missing from the course-level results.
4. Select the smallest useful set of courses and classes. Avoid padding the plan with marginal results.
5. Order the path from foundations to application when the public copy supports that sequence.

Present a weekly or step-based plan with:

- The course or class and canonical link.
- The reason it appears at that point.
- A concrete learning checkpoint phrased from public catalog evidence.

Reply in the user's language. Do not invent prerequisites, exercises, lesson content, or completion data. Do not imply access to paid material; the plan describes what to study, not what the user can open.

For a course-based plan, call `mostrar_plan_estudio` with the verified course IDs in the proposed order, the user objective, and any stated level and weekly hours (0.5-40). The panel supports up to 12 courses. Preserve the user selection and order from panel context unless you explain a proposed change. This is a draft in the panel, not saved account progress. Keep lesson-specific steps in the text response. Do not translate availability into unverified course durations.

View saved version →

---
name: compare-boluda-courses
description: Compare two or more Boluda.com courses when users want to understand differences, overlap, scope, or which course better fits a specific learning goal.
---

1. Resolve each course from a supplied URL or ID, or use `buscar_cursos` when only names are given.
2. Inspect every candidate with `obtener_curso`.
3. Compare only evidence present in public course copy, categories, and class titles.

Cover the dimensions that matter to the request, such as:

- Main focus and scope.
- Topics and class structure.
- Meaningful overlap and differences.
- Fit for the user's stated objective or level, when the evidence supports it.

Use a compact table when it makes the differences easier to scan. End with a conditional recommendation tied to the user's criterion, not a universal winner. Reply in the user's language and include canonical URLs. If a course cannot be resolved, say which one. Never infer teaching depth, private lesson content, access rights, or user progress.

When a visual comparison is useful, call `comparar_cursos` with two or three distinct, resolved course IDs. Keep the text comparison useful when the client cannot render the panel. Use only the public evidence returned by the tools.

View saved version →

---
name: recommend-boluda-courses
description: Recommend grounded Boluda.com courses and classes when users ask what to study, where to start, or which catalog option fits their role, problem, level, or learning objective.
---

1. Identify the objective and any stated level or constraint. Ask one brief question only when the objective is genuinely ambiguous.
2. Search courses using the main topic. Try one close synonym only if it improves weak or empty results.
3. Inspect the strongest candidates with `obtener_curso` before recommending them.
4. Recommend at most three primary options unless the user requests more.

For each option, include:

- Why it matches the stated objective.
- A sensible starting point based on its public class list.
- Its canonical URL.

Reply in the user's language. Do not equate search ranking with course quality or call something the best without a stated criterion. Say when the public catalog lacks enough evidence. Never imply subscriber access or knowledge of private lesson content.

View saved version →

---
name: search-boluda-courses
description: Search and inspect the public Boluda.com course and lesson catalog when users ask what Boluda teaches, where to learn a topic, what the current course is, which lessons are new, or what a known course or lesson contains.
---

## Route the request

- Use `buscar_cursos` for broad topics, skills, and learning goals.
- Use `buscar_clases` for a specific concept, task, or technique.
- Use `curso_actual`, `ultimas_clases`, or `categorias_cursos` for those exact catalog questions.
- Use `listar_cursos_categoria` when the user wants the courses in a named category.
- Use `obtener_curso` or `obtener_clase` for a known ID or Boluda.com URL.

## Search well

1. Start with the user's wording.
2. The server broadens a strict search automatically when it finds no results. If the broader results are still not useful, try one close synonym or a more specific query.
3. Inspect a result with `obtener_curso` or `obtener_clase` before making detailed claims about it.

## Answer

- Reply in the user's language.
- Distinguish courses from individual classes and include canonical links.
- Ground descriptions in the returned public copy and metadata.
- If no relevant result exists, say so and mention the query used.
- Treat lesson descriptions as public catalog copy, not as the lesson body or transcript.
- Never imply access to videos, paid transcripts, subscriber status, progress, or other user data.

When the user asks to browse visually or open the explorer, call `abrir_boluda` with an optional query and verified selected course IDs. Continue using the existing search tools for ordinary search questions that do not benefit from a panel.

View saved version →

---
name: search-boluda-podcasts
description: Search and inspect public Boluda.com podcast episodes when users ask what the podcast covers, want episodes about a topic, concept, person, or problem, request recent episodes, or refer to a known episode number or URL.
---

## Route the request

- Use `buscar_podcasts` for a topic, concept, person, business problem, or question.
- Use `ultimos_podcasts` when the user asks for the most recently published episodes.
- Use `obtener_podcast` for a known episode number or canonical Boluda.com URL, or to inspect a search result before making detailed claims.

## Search well

1. Start with the user's wording.
2. If results are weak or empty, try one close synonym or a shorter query focused on the main concept.
3. Inspect the strongest result with `obtener_podcast` when the user wants a summary or detailed explanation.

## Answer

- Reply in the user's language.
- Include episode numbers, publication dates, and canonical links when available.
- Ground claims in the returned public episode copy and metadata.
- If no relevant episode exists, say so and mention the query used.
- Treat the episode copy as a public summary, not as an audio transcript.
- Do not invent quotations, timestamps, speakers, private content, or claims that require listening to the audio.