CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

learn-ywai

Run and learn ywai: MCP, model profiles, agent groups, doc tours. Trigger: ywai mcp, ywai profile, /learn-ywai.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

ywai

The human does not run these commands. You do.

When

Two jobs, one skill:

  • Run — the user wants an MCP on or off, a different model profile, or an agent group installed or removed. Jump to Commands.
  • Learn — the user wants to understand ywai (CLI, agents, skills, workflows) rather than change it. Jump to Teaching.

Rules

  1. Execute ywai … yourself. Do not paste the command for the user to copy.
  2. List before mutate. Confirm the id or name exists.
  3. After MCP or profile changes, tell them to restart OpenCode.
  4. Never enable or disable core. It stays installed.

Commands

MCP

ywai mcp list
ywai mcp enable <id>
ywai mcp disable <id>
ywai mcp auth <id>

disable keeps the config. auth is OAuth (figma, github, gitlab, or any catalog entry with AuthType=oauth).

Profile

ywai profile list
ywai profile use <name>

list marks the active profile with *. Shipped names:

NameEffect
inheritNo pinned models. Agents use the session/lead model.
balancedCost/quality mix. DeepSeek v4 pro/flash on the former Grok/Minimax slots.
fastFlash model on every agent.
deepTop models for design/review.

Groups

ywai groups
ywai groups enable <name>
ywai groups disable <name>

Use the names from ywai groups. core is always on.

Done when

The command printed success (MCP … enabled, Active profile: …, Group … enabled) or you reported the error verbatim.

Teaching

Reach for this when the user wants to learn, not mutate.

  • Docs are the teacher. Read only references/docs/ inside this skill. Every .mdx there is readable — index pages, guides, agent pages, all of them. Do not invent commands, flags, or agent names, and do not fetch the website.
  • One page per turn. Teach that page, then stop. Ask at most one question. Read as many extra pages as the topic needs to prepare, but teach one page at a time.
  • Match the user's language. The docs are Spanish; reply in the user's language.
  • Escalate to teach for courses. When the user asks for a long course, structured lessons, or the tour outgrows chat, load the teach skill and build its workspace (MISSION.md, HTML lessons). Use the references/docs/ pages as the source material there too. For a one-off question, stay in chat.
  1. Open references/curriculum.md.
  2. Pick the page: explicit topic, else tour item 1 (or the next unread item if they already started).
  3. Read that file from references/docs/, plus any page the topic requires (e.g. the named agent page after agents/index.mdx).
  4. Teach from that page only:
    • Lead with the outcome (what they can do after this).
    • Show the happy path (commands / @agent examples from the page).
    • One check question so they retrieve, not just nod.
  5. Offer the next curriculum item. Do not dump the rest of the site.

If a page is missing or the read fails, say so and teach only what you successfully read.

/learn-ywai
/learn-ywai agentes
Repository

YoizenSA/dev-ai-workflow

Path

ywai/skills/learn-ywai/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.