Omp Roles logo

Omp Roles

OrganizationPopular
agentscope-ai
omp-roles

Use this skill whenever you need the allowed_tools / skills preset for a sub-agent role before calling spawn_subagent. Trigger especially when user mentions: "role", "spawn_subagent", "allowed_tools", or any OMP role name (executor, architect, analyst, critic, security-reviewer, code-reviewer, qa-tester, planner, explore, debugger, verifier). Also use when a /ultrawork, /ralph, /autopilot, /ultraqa, or /team workflow step asks for role tool/skill configuration.

Overview

Publisheragentscope-ai
RepositoryQwenPaw
Skill nameomp-roles
Stars
35.6K
Forks
3.2K
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by agentscope-ai on GitHub. Read the source before you install it.

Installation

Install the Omp Roles AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/agentscope-ai/QwenPaw/tree/main/plugins/bundle/omp_workflows/skills/omp-roles
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/agentscope-ai/QwenPaw.git /tmp/QwenPaw
mkdir -p .claude/skills
cp -r /tmp/QwenPaw/plugins/bundle/omp_workflows/skills/omp-roles .claude/skills/omp-roles
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Omp Roles in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Omp Roles on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Omp Roles is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OMP Role Tool Configuration

When using spawn_subagent (single or batch mode) to dispatch sub-agents, set the corresponding allowed_tools and skills parameters based on the sub-agent's role.

Canonical source of truth in code: plugins/bundle/omp_workflows/shared/constants.py (ROLE_ALLOWED_TOOLS, ROLE_SKILLS, TOOL_* names) and shared/role_prompts.py (ROLE_PROMPTS, build_worker_prompt, format_spawn_call). Tool strings must match registered ToolRegistry names — do not invent aliases.

Role Definitions

executor (Code Executor)

  • allowed_tools: null (inherits all tools)
  • skills: null (inherits all skills)
  • Boundary: Implement features, run quality checks. Follow existing patterns.

architect (System Architect)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "write_file", "ast_search", "execute_shell_command"]
  • skills: []
  • Boundary: Design interfaces and module boundaries, diagnose complex issues. No implementation code.

analyst (Requirements Analyst)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "write_file", "execute_shell_command"]
  • skills: []
  • Boundary: Extract requirements, identify constraints, define acceptance criteria. No code.

critic (Plan/Design Critic)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "ast_search"]
  • skills: []
  • Boundary: Review plans and designs, challenge assumptions. No plans, no code.

security-reviewer (Security Reviewer)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "execute_shell_command", "ast_search"]
  • skills: []
  • Boundary: Identify vulnerabilities, injection vectors, auth weaknesses. No file modifications.

code-reviewer (Code Reviewer)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "execute_shell_command", "ast_search"]
  • skills: []
  • Boundary: Review code quality, maintainability, convention adherence. No file modifications.

qa-tester (QA Tester)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "execute_shell_command"]
  • skills: []
  • Boundary: Interactive CLI/service testing — start services and verify behavior.

planner (Strategic Planner)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "write_file", "ast_search"]
  • skills: []
  • Boundary: Create implementation plans, define task breakdown and dependencies. No implementation code.

explore (Code Explorer)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "ast_search"]
  • skills: []
  • Boundary: Read-only exploration. Map codebase structure and dependencies.

debugger (Debugging Expert)

  • allowed_tools: null (inherits all tools)
  • skills: []
  • Boundary: Root cause analysis, fix build/test failures. No new features.

verifier (Adversarial Verifier)

  • allowed_tools: ["read_file", "grep_search", "glob_search", "execute_shell_command", "ast_search"]
  • skills: []
  • Boundary: Verification only — no file modifications. Physical isolation via read-only tool set.

Usage

text
spawn_subagent(
    task="<role identity from ROLE_PROMPTS>\n\n## Task\n<task description>",
    allowed_tools=<ROLE_ALLOWED_TOOLS[role] or omit if null>,
    skills=<ROLE_SKILLS[role] or omit if null>,
    fork=True,         # if worktree isolation needed
    background=True,   # if background execution needed
)

When allowed_tools or skills is null, omit the parameter (uses default None). For batch mode, pass task="" and put per-item role config in each batch dict.

Frequently asked questions

What does the Omp Roles AI skill do?

Use this skill whenever you need the allowed_tools / skills preset for a sub-agent role before calling spawn_subagent. Trigger especially when user mentions: "role", "spawn_subagent", "allowed_tools", or any OMP role name (executor, architect, analyst, critic, security-reviewer, code-reviewer, qa-tester, planner, explore, debugger, verifier). Also use when a /ultrawork, /ralph, /autopilot, /ultraqa, or /team workflow step asks for role tool/skill configuration.

Why use Omp Roles on TypingMind?

Because you install it once and use it with any model. Omp Roles is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Omp Roles in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/agentscope-ai/QwenPaw/tree/main/plugins/bundle/omp_workflows/skills/omp-roles. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Omp Roles?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Omp Roles?

As many as you like. As long as a model supports skills, you can use Omp Roles with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Omp Roles AI skill free?

Yes. It is published on GitHub by agentscope-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇