القائمة
Automate Adobe tasks via Rube MCP (Composio). Always search tools first for current schemas.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | adobe-automation |
| description | Automate Adobe tasks via Rube MCP (Composio). Always search tools first for current schemas. |
| requires | {"mcp":["rube"]} |
Automate Adobe operations through Composio's Adobe toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/adobe
RUBE_MANAGE_CONNECTIONS with toolkit adobeRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit adobeAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Adobe operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Adobe task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["adobe"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Adobe-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit adobe |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git worktree fallback, or non-git copy fallback
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Put your AI on a Performance Improvement Plan. Forces exhaustive problem-solving with Western big-tech performance culture rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.
Use when you have a spec or requirements for a multi-step task, before touching code