بنقرة واحدة
docs-studio-ops
Use the `docs-studio` Maverick app through its declared CLI and MCP surfaces.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use the `docs-studio` Maverick app through its declared CLI and MCP surfaces.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create and manage workspace checklists through the Checklist app CLI and MCP surfaces.
Create an image with the image generation tool, save it into the active workspace with a suitable filename, and verify it through Storage.
Use the Storage app to inspect workspace uploaded files and generated artifacts through official Maverick app surfaces.
Manage Maverick agent roles, agent types, prompt previews, and agent catalog data through the Agents app.
Use the Maverick App Store app to inspect catalogs, install apps, and submit app source to the external public App Store.
Use Chat UI surfaces with core-owned workspace conversation threads and runtime turn operations.
| name | docs-studio-ops |
| description | Use the `docs-studio` Maverick app through its declared CLI and MCP surfaces. |
Use the app's official CLI or MCP surfaces for targeted documentation lookup, status, state reads, and reference discovery. The mounted frontend is the primary editing experience.
Do not read or write another app's private data.
Prefer targeted documentation calls before broad core developer-context reads:
maverick app docs-studio cli run docs-studio --subcommand manifest --section_id core-architecture
maverick app docs-studio cli run docs-studio --subcommand search --query "provider credentials" --limit 5
maverick app docs-studio cli run docs-studio --subcommand read --page_id provider-credentials --max_chars 12000
MCP equivalents:
docs_studio_docs_manifestdocs_studio_docs_searchdocs_studio_docs_readUse docs_studio_state only when the caller really needs the composed UI state.