Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/open-software-network/os-clovy --skill clovy-obsidianEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Run live, agent-driven end-to-end QA for os-clovy by opening the real app or web preview, clicking through changed flows, inspecting visible state, recording and compressing video, attaching QA videos to PRs through os-platform file uploads, capturing screenshots/logs, and reporting pass/fail evidence. Use when a user asks for full integration testing, live app QA, visual inspection, "open the app and use it", "click through it", "record the QA run", "attach the video to the PR", native Tauri verification, WKWebView inspection, onboarding smoke tests, HUD/tray/hotkey checks, or manual QA replacement by an agent. Compose Browser, Chrome, Computer Use, terminal commands, and repo tests as appropriate.
Test, screenshot, and debug a Tauri or Vite frontend in a real browser using Playwright or Chrome DevTools MCP. Use when asked to run/screenshot a desktop-app or web UI, verify a frontend change visually, debug rendering without the native build, or when the native webview (macOS WKWebView) can't be driven by Playwright/CDP. Covers faking the Tauri IPC bridge so surfaces render with no backend.
Stand up design-featuring work the Open Software way. Use when building, redesigning, or polishing any UI surface in an OS repo (os-clovy, os-scribe, os-marketing-page, os-platform), when a feature needs visual design decisions before or during implementation, when reviewing interface work for house taste, or when someone asks to "stand up the design", "design this feature", "make it feel like ours", "make it feel better", or wants the Open Software design sensibility applied. Orchestrates specialist design skills (impeccable, emil-design-eng, make-interfaces-feel-better, transitions-dev, mobbin) when installed, but is fully self-sufficient without them. Core commitments it enforces - compose from the repo's existing design-system blocks rather than inventing new ones, and quiet, subtle, elegant over loud.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | clovy-obsidian |
| description | Work with the Obsidian vault currently selected in Clovy. |
| platforms | ["linux","macos","windows"] |
Use this skill for Obsidian note work. Before every distinct Obsidian task, call
get_obsidian_vault to discover the current vault.
connected is false, tell the user that no Obsidian vault is connected in
Clovy. Do not guess a default path.available is false, tell the user that the connected vault is currently
unavailable. Do not infer or reconstruct its absolute path.Use the returned absolute path with the generic filesystem tools. In Sandboxed
mode, use only list_files, read_file, and search_files on the returned
vault path. Do not call write_file or patch_file for vault paths in
Sandboxed mode; the host denies external writes. In Unrestricted mode, writing
still requires an explicit user request and normal tool approval; receiving the
vault path alone is not permission to write.
Prefer file read/search/write tools over shell commands when practical. Follow
Obsidian Markdown conventions: use YAML frontmatter only when the note already
uses it or the user asks for it, preserve valid frontmatter, and link related
notes with [[Note Name]] wikilinks.