├── README.md ├── marketplace-sources.md ├── mcps ├── brave-search-npx │ └── metadata.en.yml └── context7-npx │ └── metadata.en.yml ├── metadata.en.yml ├── modes └── roo-diagnose │ └── metadata.en.yml └── packages ├── maestro ├── mcps │ └── metadata.en.yml ├── metadata.en.yml └── modes │ ├── AccessibilityGuardian │ └── metadata.en.yml │ ├── ApiArchitect │ └── metadata.en.yml │ ├── Artisan │ └── metadata.en.yml │ ├── AuthGuardian │ └── metadata.en.yml │ ├── BackendForge │ └── metadata.en.yml │ ├── BackendInspector │ └── metadata.en.yml │ ├── Blueprinter │ └── metadata.en.yml │ ├── CloudForge │ └── metadata.en.yml │ ├── CodeReviewer │ └── metadata.en.yml │ ├── ContentWriter │ └── metadata.en.yml │ ├── DataArchitect │ └── metadata.en.yml │ ├── DeploymentMaster │ └── metadata.en.yml │ ├── DesignSystemForge │ └── metadata.en.yml │ ├── DevSecOps │ └── metadata.en.yml │ ├── Documentarian │ └── metadata.en.yml │ ├── FrontCrafter │ └── metadata.en.yml │ ├── FrontendInspector │ └── metadata.en.yml │ ├── GitMaster │ └── metadata.en.yml │ ├── InfraPlanner │ └── metadata.en.yml │ ├── Maestro │ └── metadata.en.yml │ ├── MobileDeveloper │ └── metadata.en.yml │ ├── MotionDesigner │ └── metadata.en.yml │ ├── NoSqlSmith │ └── metadata.en.yml │ ├── NodeSmith │ └── metadata.en.yml │ ├── Pathfinder │ └── metadata.en.yml │ ├── PerformanceEngineer │ └── metadata.en.yml │ ├── PlanReviewer │ └── metadata.en.yml │ ├── PythonMaster │ └── metadata.en.yml │ ├── ReactMaster │ └── metadata.en.yml │ ├── Researcher │ └── metadata.en.yml │ ├── SecurityStrategist │ └── metadata.en.yml │ ├── SecurityTester │ └── metadata.en.yml │ ├── SelfReflection │ └── metadata.en.yml │ ├── SqlMaster │ └── metadata.en.yml │ ├── Strategist │ └── metadata.en.yml │ ├── TestCrafter │ └── metadata.en.yml │ └── Visionary │ └── metadata.en.yml └── smartsheet-project-manager ├── mcps └── smartsheet │ └── metadata.en.yml ├── metadata.en.yml └── modes └── ProjectManager └── metadata.yml /README.md: -------------------------------------------------------------------------------- 1 | # Roo Code Marketplace 2 | 3 | * [Roo Code Marketplace](#roo-code-marketplace) 4 | * [Welcome](#welcome) 5 | * [Item Structure, Metadata, and Features](#item-structure-metadata-and-features) 6 | * [Overview](#overview) 7 | * [Directory Structure](#directory-structure) 8 | * [Metadata File Format](#metadata-file-format) 9 | * [`registry`:](#registry) 10 | * [`item`:](#item) 11 | * [Localization Support](#localization-support) 12 | * [Configurable Support](#configurable-support) 13 | * [Contributing Process](#contributing-process) 14 | * [1. Fork the Repository](#1-fork-the-repository) 15 | * [2. Clone Your Fork](#2-clone-your-fork) 16 | * [3. Create Your Item](#3-create-your-item) 17 | * [4. Test Your Package](#4-test-your-package) 18 | * [5. Commit and Push Your Changes](#5-commit-and-push-your-changes) 19 | * [6. Create a Pull Request](#6-create-a-pull-request) 20 | * [7. Review Process](#7-review-process) 21 | * [Best Practices](#best-practices) 22 | * [Example package metadatas](#example-package-metadatas) 23 | * [Data Science Toolkit](#data-science-toolkit) 24 | * [Adding Custom Marketplace Sources](#adding-custom-marketplace-sources) 25 | 26 | 27 | ## Welcome 28 | 29 | Roo Code Marketplace is an un-released work in progress..... 30 | 31 | Imagine effortlessly gliding through your projects with the agility of a kangaroo on Roo mode! 🦘 Picture your data flowing seamlessly and powerfully through our mighty MCP servers, like a vibrant river of information! 🌊 And get ready to craft spells of efficiency and innovation with the perfect prompts – your secret incantations for mastery! 32 | 33 | Sharing is caring, and when you share your knowledge of Roo modes, MCP servers, and brilliant prompts, you're not just helping your team – you're spreading happiness throughout the Roo community! 😊 Watch as collaboration soars, productivity skyrockets, and smiles bloom across faces. It's a roovolution of joy and empowerment! 34 | 35 | So, dive in, explore the wonders of Roo modes, harness the strength of MCP servers, and play with the power of prompts. Unleash your superpowers and let the happiness flow! 🚀 You've got this! 💪 36 | 37 | This guide explains how to create and share Modes, MCPs, and Prompts to Roo Code users conviniently available right inside Roo. 38 | 39 | [Learn more about using Roo Code Marketplace](https://github.com/Smartsheet-JB-Brown/Roo-Code/blob/jbbrown/marketplace/cline_docs/marketplace/README.md) 40 | 41 | ## Item Structure, Metadata, and Features 42 | 43 | ### Overview 44 | 45 | * Every component on the registry is an `item`. 46 | * An `item` can be of type: `mcp`, `mode`, `prompt`, `package` 47 | * Each item apart from `package` is a singular object, i.e: one mode, one mcp server. 48 | * A `package` contains multiple other `item`s 49 | * All internal sub-items of a `package` is contained in the binary on the `package` item metadata itself. 50 | * Each `item` requires specific metadata files and follows a consistent directory structure. 51 | 52 | ### Directory Structure 53 | 54 | The `registry` structure could be the root or placed in a `registry` directory of any `git` repository, a sample structure for a registry is: 55 | 56 | ``` 57 | registry/ 58 | ├── metadata.en.yml # Required metadata for the registry 59 | │ 60 | ├── modes/ # `mode` items 61 | │ └── a-mode-name/ 62 | │ └── metadata.en.yml 63 | ├── mcps/ # `mcp` items 64 | ├── prompts/ # `prompt` items 65 | │ 66 | └── packages/ # `package` items 67 | └── a-package-name/ 68 | ├── metadata.en.yml # Required metadata 69 | ├── metadata.fr.yml # Optional localized metadata (French) 70 | ├── modes/ # `a-package-name`'s internal `mode` items 71 | │ └── my-mode/ 72 | │ └── metadata.en.yml 73 | ├── mcps/ # `a-package-name`'s internal `mcp` items 74 | │ └── my-server/ 75 | │ └── metadata.en.yml 76 | └── prompts/ # `a-package-name`'s internal `prompt` items 77 | └── my-prompt/ 78 | └── metadata.en.yml 79 | ``` 80 | 81 | ### Metadata File Format 82 | 83 | Metadata files use YAML format and must include specific fields: 84 | 85 | #### `registry`: 86 | ```yaml 87 | name: "My Registry" 88 | description: "A concise description for your registry" 89 | version: "0.0.0" 90 | author: "your name" # optional 91 | authorUrl: "http://your.profile.url/" # optional 92 | ``` 93 | 94 | #### `item`: 95 | ```yaml 96 | name: "My Package" 97 | description: "A concise description for your package" 98 | version: "0.0.0" 99 | type: "package" # One of: package, mode, mcp, prompt 100 | sourceUrl: "https://url.to/source-repository" # Optional 101 | binaryUrl: "https://url.to/binary.zip" 102 | binaryHash: "SHA256-of-binary" 103 | binarySource: "https://proof.of/source" # Optional, proof-of-source for the binary (tag/hash reference, build job, etc) 104 | tags: 105 | - tag1 106 | - tag2 107 | author: "your name" # optional 108 | authorUrl: "http://your.profile.url/" # optional 109 | ``` 110 | 111 | ### Localization Support 112 | 113 | You can provide metadata in multiple languages by using locale-specific files: 114 | 115 | **Important Notes on Localization:** 116 | 117 | - Only files with the pattern `metadata.{locale}.yml` are supported 118 | - The Marketplace will display metadata in the user's locale if available 119 | - If the user's locale is not available, it will fall back to English 120 | - The English locale (`metadata.en.yml`) is required as a fallback 121 | - Files without a locale code (e.g., just `metadata.yml`) are not supported 122 | 123 | ### Configurable Support 124 | 125 | Powered with [**`Roo Rocket`**](https://github.com/NamesMT/roo-rocket), the registry supports configurable items like: 126 | + `mcp` with access token inputs. 127 | + `mode` / `prompt` with feature flags. 128 | + And further customizations that a creator can imagine. 129 | + E.g: a `package` could prompt you for the location of its context folder. 130 | 131 | ## Contributing Process 132 | 133 | To contribute your package to the official repository, follow these steps: 134 | 135 | ### 1. Fork the Repository 136 | 137 | 1. Visit the official Roo Code Packages repository: [https://github.com/RooCodeInc/Roo-Code-Marketplace](https://github.com/RooCodeInc/Roo-Code-Marketplace) 138 | 2. Click the "Fork" button in the top-right corner 139 | 3. This creates your own copy of the repository where you can make changes 140 | 141 | ### 2. Clone Your Fork 142 | 143 | Clone your forked repository to your local machine: 144 | 145 | ```bash 146 | git clone https://github.com/YOUR-USERNAME/Roo-Code-Marketplace.git 147 | cd Roo-Code-Marketplace 148 | ``` 149 | 150 | ### 3. Create Your Item 151 | 152 | 1. Create a new directory for your item with an appropriate name 153 | 2. Add the required metadata files (and subitem directories for `package`) 154 | 3. Follow the structure and format described above 155 | 4. Add `sourceUrl` that points to a repository or post with info/document for the item. 156 | 157 | Example of creating a simple package: 158 | 159 | ```bash 160 | mkdir -p my-package/modes/my-mode 161 | touch my-package/metadata.en.yml 162 | touch my-package/README.md 163 | touch my-package/modes/my-mode/metadata.en.yml 164 | ``` 165 | 166 | ### 4. Test Your Package 167 | 168 | Before submitting, test your package by adding your fork as a custom source in the Marketplace: 169 | 170 | 1. In VS Code, open the Marketplace 171 | 2. Go to the "Settings" tab 172 | 3. Click "Add Source" 173 | 4. Enter your fork's URL (e.g., `https://github.com/YOUR-USERNAME/Roo-Code-Marketplace`) 174 | 5. Click "Add" 175 | 6. Verify that your package appears and functions correctly 176 | 177 | ### 5. Commit and Push Your Changes 178 | 179 | Once you're satisfied with your package: 180 | 181 | ```bash 182 | git add . 183 | git commit -m "Add my-package with mode component" 184 | git push origin main 185 | ``` 186 | 187 | ### 6. Create a Pull Request 188 | 189 | 1. Go to the original repository: [https://github.com/RooCodeInc/Roo-Code-Marketplace](https://github.com/RooCodeInc/Roo-Code-Marketplace) 190 | 2. Click "Pull Requests" and then "New Pull Request" 191 | 3. Click "Compare across forks" 192 | 4. Select your fork as the head repository 193 | 5. Click "Create Pull Request" 194 | 6. Provide a clear title and description of your package 195 | 7. Submit the pull request 196 | 197 | ### 7. Review Process 198 | 199 | After submitting your pull request: 200 | 201 | 1. Maintainers will review your package 202 | 2. They may request changes or improvements 203 | 3. Once approved, your package will be merged into the main repository 204 | 4. Your package will be available to all users of the Marketplace 205 | 206 | ## Best Practices 207 | 208 | - **Clear Documentation**: Include detailed documentation in your README.md 209 | - **Descriptive Metadata**: Write clear, informative descriptions 210 | - **Appropriate Tags**: Use relevant tags to make your package discoverable 211 | - **Testing**: Thoroughly test your package before submitting 212 | - **Localization**: Consider providing metadata in multiple languages 213 | - **Semantic Versioning**: Follow semantic versioning for version numbers 214 | - **Consistent Naming**: Use clear, descriptive names for components 215 | 216 | ## Example package metadatas 217 | 218 | ### Data Science Toolkit 219 | 220 | Here's an example of a data science package: 221 | 222 | **data-science-toolkit/metadata.en.yml**: 223 | 224 | ```yaml 225 | name: "Data Science Toolkit" 226 | description: "A comprehensive collection of tools for data science workflows" 227 | version: "1.0.0" 228 | type: "package" 229 | tags: 230 | - data 231 | - science 232 | - analysis 233 | - visualization 234 | - machine learning 235 | ``` 236 | 237 | **data-science-toolkit/modes/data-scientist-mode/metadata.en.yml**: 238 | 239 | ```yaml 240 | name: "Data Scientist Mode" 241 | description: "A specialized mode for data science tasks" 242 | version: "1.0.0" 243 | type: "mode" 244 | tags: 245 | - data 246 | - science 247 | - analysis 248 | ``` 249 | 250 | **data-science-toolkit/prompts/data-cleaning/metadata.en.yml**: 251 | 252 | ```yaml 253 | name: "Data Cleaning Prompt" 254 | description: "A prompt for cleaning and preprocessing datasets" 255 | version: "1.0.0" 256 | type: "prompt" 257 | tags: 258 | - data 259 | - cleaning 260 | - preprocessing 261 | ``` 262 | 263 | ## Adding Custom Marketplace Sources 264 | 265 | The Marketplace allows you to extend its functionality by adding custom sources. [**This guide**](./marketplace-sources.md) explains how to set up and manage your own Marktplace repositories to access additional components beyond the default offerings. 266 | -------------------------------------------------------------------------------- /marketplace-sources.md: -------------------------------------------------------------------------------- 1 | # Adding Custom Marketplace Sources 2 | 3 | The Marketplace allows you to extend its functionality by adding custom sources. This guide explains how to set up and manage your own Marktplace repositories to access additional components beyond the default offerings. 4 | 5 | ## Setting up a Marketplace Source Repository 6 | 7 | A Marketplace source repository is a Git repository that contains Marketplace items organized in a specific structure. You can create your own repository to host custom packages: 8 | 9 | ### Repository Requirements 10 | 11 | 1. **Proper Structure**: The repository must follow the required directory structure 12 | 2. **Valid Metadata**: Each package must include properly formatted metadata files 13 | 3. **Git Repository**: The source must be a Git repository accessible via HTTPS 14 | 15 | ### Building your registry repository 16 | 17 | #### Start from a sample registry repository 18 | 19 | Check the branches of the [**rm-samples**](https://github.com/NamesMT/rm-samples) repository here. 20 | 21 | #### Creating a New Repository 22 | 23 | 1. Create a new repository on GitHub, GitLab, or another Git hosting service 24 | 2. Initialize the repository with a README.md file 25 | 3. Clone the repository to your local machine: 26 | 27 | ```bash 28 | git clone https://github.com/your-username/your-registry-repo.git 29 | cd your-registry-repo 30 | ``` 31 | 32 | 4. Create the basic registry structure: 33 | 34 | ```bash 35 | mkdir -p packages modes mcps prompts 36 | touch metadata.en.yml 37 | ``` 38 | 39 | 5. Add repository metadata to `metadata.en.yml`: 40 | 41 | ```yaml 42 | name: "Your Repository Name" 43 | description: "A collection of custom packages for Roo Code" 44 | version: "1.0.0" 45 | ``` 46 | 47 | 6. Commit and push the initial structure: 48 | 49 | ```bash 50 | git add . 51 | git commit -m "Initialize package repository structure" 52 | git push origin main 53 | ``` 54 | 55 | ## Adding Sources to Roo Code 56 | 57 | Once you have a properly structured source repository, you can add it to your Roo Code Marketplace as a source: 58 | 59 | ### Default Package Source 60 | 61 | Roo Code comes with a default package source: 62 | 63 | - URL: `https://github.com/RooCodeInc/Roo-Code-Marketplace` 64 | - This source is enabled by default, and anytime all sources have been deleted. 65 | 66 | ### Adding a New Source 67 | 68 | 1. Open VS Code with the Roo Code extension 69 | 2. Navigate to the Marketplace 70 | 3. Switch to the "Sources" tab 71 | 4. Click the "Add Source" button 72 | 5. Enter the repository URL: 73 | - Format: `https://github.com/username/repository.git` 74 | - Example: `https://github.com/your-username/your-registry-repo.git` 75 | 6. Click "Add" to save the source 76 | 77 | ### Managing Sources 78 | 79 | The "Sources" tab provides several options for managing your registry sources: 80 | 81 | 1. **Remove**: Delete a source from your configuration 82 | 2. **Refresh**: Update the item list from a source - this is forced git clone/pull to override local caching of data 83 | 84 | ### Source Caching and Refreshing 85 | 86 | Marketplace sources are cached to improve performance: 87 | 88 | - **Cache Duration**: Sources are cached for 1 hour (3600000 ms) 89 | - **Force Refresh**: To force an immediate refresh of a source: 90 | 1. Go to the "Sources" tab 91 | 2. Click the "Refresh" button next to the source you want to update 92 | 3. This will bypass the cache and fetch the latest data from the repository 93 | 94 | ### Troubleshooting Sources 95 | 96 | If a source isn't loading properly: 97 | 98 | 1. Check that the repository URL is correct 99 | 2. Ensure the repository follows the required structure 100 | 3. Look for error messages in the Marketplace interface 101 | 4. Try refreshing the sources list 102 | 5. Disable and re-enable the source 103 | 104 | ## Creating Private Sources 105 | 106 | For team or organization use, you might want to create private sources: 107 | 108 | ### Private Repository Setup 109 | 110 | 1. Create a private repository on your Git hosting service 111 | 2. Follow the same structure requirements as public repositories 112 | 3. Set up appropriate access controls for your team members 113 | 114 | ### Authentication Options 115 | 116 | To access private repositories, you may need to: 117 | 118 | 1. Configure Git credentials on your system 119 | 2. Use a personal access token with appropriate permissions 120 | 3. Set up SSH keys for authentication 121 | 122 | ### Organization Best Practices 123 | 124 | For teams and organizations: 125 | 126 | 1. Designate maintainers responsible for the source 127 | 2. Establish quality standards for contributed items and packages 128 | 3. Create a review process for new additions 129 | 4. Document usage guidelines for team members 130 | 5. Consider implementing versioning for your items and packages 131 | 132 | ## Using Multiple Sources 133 | 134 | The Marketplace supports multiple sources simultaneously: 135 | 136 | ### Benefits of Multiple Sources 137 | 138 | - Access components from different providers 139 | - Separate internal and external components 140 | - Test new work before contributing them to the main repository 141 | - Create specialized sources for different projects or teams 142 | 143 | ### Source Management Strategy 144 | 145 | 1. Keep the default source enabled for core components 146 | 2. Add specialized sources for specific needs 147 | 3. Create a personal source for testing and development 148 | 4. Refresh sources after you've pushed changes to them to get the latest items 149 | -------------------------------------------------------------------------------- /mcps/brave-search-npx/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Brave Search (npx)" 2 | description: "The \"Brave Search\" MCP" 3 | type: "mcp" 4 | version: "0.5.0" 5 | binaryUrl: "https://github.com/NamesMT/config-packs/releases/download/v0.0.0/roo-brave-search-mcp-new.zip" 6 | binaryHash: "Oqi2yk26T_6k1YSwlOESFsYy0xWbfIcaigav2zCm93k" 7 | sourceUrl: "https://github.com/NamesMT/config-packs" 8 | tags: ["Brave", "MCP"] 9 | author: "NamesMT" 10 | -------------------------------------------------------------------------------- /mcps/context7-npx/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Context7 (npx)" 2 | description: "Up-to-date code documentation for LLMs and AI code editors" 3 | type: "mcp" 4 | version: "0.0.20250522" 5 | sourceUrl: "https://github.com/NamesMT/rm-samples/tree/context7" 6 | binaryUrl: "https://github.com/NamesMT/rm-samples/raw/refs/heads/context7/binaries/context7-0522.zip" 7 | binaryHash: "r5ZZJDJO9ZXko5YrGuW7z4pFiAEu-pnFlsVj7Y7aZng" 8 | tags: ["upstash", "context7", "document"] 9 | author: "NamesMT" 10 | authorUrl: "https://github.com/NamesMT" 11 | -------------------------------------------------------------------------------- /metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "The official Roo Marketplace" 2 | description: "The official registry source for Roo Code ecosystem stuff!" 3 | version: "1.0.0" 4 | author: "JB Brown" 5 | authorUrl: "https://www.linkedin.com/in/jbbrown1/" 6 | -------------------------------------------------------------------------------- /modes/roo-diagnose/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Roo Issue Diagnoser" 2 | description: "This mode helps you generate detailed diagnostic reports for Roo issues." 3 | type: "mode" 4 | version: "0.0.20250522" 5 | sourceUrl: "https://github.com/NamesMT/rm-samples/tree/roo-diagnose" 6 | binaryUrl: "https://raw.githubusercontent.com/NamesMT/rm-samples/refs/heads/roo-diagnose/roo-diagnose-0522.zip" 7 | binaryHash: "i73t72S9CAkBI-w40Kr_kJm8RzLoZUstoDzWJYFcM3I" 8 | tags: ["diagnostic"] 9 | author: "d.o.it" 10 | authorUrl: https://github.com/d-oit 11 | -------------------------------------------------------------------------------- /packages/maestro/mcps/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Vertex AI by shariqriazz" 2 | description: "This MCP server provides a comprehensive suite of tools for interacting with Google Cloud's Vertex AI Gemini models, focusing on coding assistance and general query answering." 3 | type: "mcp" 4 | version: "0.0.0" 5 | tags: ["maestro", "vertex"] 6 | author: "shariqriazz" 7 | -------------------------------------------------------------------------------- /packages/maestro/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Maestro" 2 | description: "A collection of highly specialized Roo modes designed to work together as an integrated system. Each mode is an expert in a specific domain, with clear responsibilities, boundaries, and collaboration protocols. Also includes Vertex AI MCP server" 3 | type: "package" 4 | version: "0.0.20250522" 5 | sourceUrl: "https://github.com/NamesMT/rm-samples/tree/maestro" 6 | binaryUrl: "https://github.com/NamesMT/rm-samples/raw/dd47cf3/binaries/maestro-0522.zip" 7 | binaryHash: "jivc5YcUWPNLsHbUCcQHJC3nefsUuS5-Ywy_Pnmdzrk" 8 | tags: ["specialized"] 9 | author: "shariqriazz" 10 | authorUrl: https://github.com/shariqriazz 11 | -------------------------------------------------------------------------------- /packages/maestro/modes/AccessibilityGuardian/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "AccessibilityGuardian" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/ApiArchitect/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "ApiArchitect" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Artisan/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Artisan" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/AuthGuardian/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "AuthGuardian" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/BackendForge/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "BackendForge" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/BackendInspector/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "BackendInspector" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Blueprinter/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Blueprinter" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/CloudForge/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "CloudForge" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/CodeReviewer/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "CodeReviewer" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/ContentWriter/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "ContentWriter" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/DataArchitect/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "DataArchitect" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/DeploymentMaster/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "DeploymentMaster" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/DesignSystemForge/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "DesignSystemForge" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/DevSecOps/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "DevSecOps" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Documentarian/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Documentarian" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/FrontCrafter/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "FrontCrafter" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/FrontendInspector/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "FrontendInspector" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/GitMaster/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "GitMaster" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/InfraPlanner/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "InfraPlanner" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Maestro/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Maestro" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/MobileDeveloper/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "MobileDeveloper" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/MotionDesigner/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "MotionDesigner" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/NoSqlSmith/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "NoSqlSmith" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/NodeSmith/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "NodeSmith" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Pathfinder/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Pathfinder" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/PerformanceEngineer/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "PerformanceEngineer" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/PlanReviewer/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "PlanReviewer" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/PythonMaster/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "PythonMaster" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/ReactMaster/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "ReactMaster" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Researcher/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Researcher" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/SecurityStrategist/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "SecurityStrategist" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/SecurityTester/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "SecurityTester" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/SelfReflection/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "SelfReflection" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/SqlMaster/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "SqlMaster" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Strategist/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Strategist" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/TestCrafter/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "TestCrafter" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/maestro/modes/Visionary/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Visionary" 2 | description: "" 3 | type: "mode" 4 | version: "0.0.0" 5 | tags: ["maestro"] 6 | author: "shariqriazz" -------------------------------------------------------------------------------- /packages/smartsheet-project-manager/mcps/smartsheet/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Smartsheet Project Management" 2 | description: "Track and update your tasks and assignments, and update status for your team's work in Roo." 3 | type: "mcp" 4 | version: "1.0.0" 5 | tags: ["project management", "agile", "work managemnt", "tasks", "team", "spreadsheet", "kanban"] 6 | author: "Smartsheet" 7 | -------------------------------------------------------------------------------- /packages/smartsheet-project-manager/metadata.en.yml: -------------------------------------------------------------------------------- 1 | name: "Project Manager by Smartsheet" 2 | description: "An experienced software Project Manager who excels at amplifying positive impact through effective team coordination and resource allocation, + deep integration with Smartsheet ecosystem" 3 | type: "package" 4 | version: "1.0.0" 5 | sourceUrl: "https://github.com/smartsheet-platform/config-packs" 6 | binaryUrl: "https://github.com/smartsheet-platform/config-packs/raw/f4c18f9/binary/smartsheet-mcp.zip" 7 | binaryHash: "LItpaOyDqfASJF7TkYTX6X3CpJ7_2lt-aw19KSnJYJQ" 8 | tags: ["project management", "agile", "work managemnt", "tasks", "team", "spreadsheet", "kanban"] 9 | author: "Smartsheet" 10 | -------------------------------------------------------------------------------- /packages/smartsheet-project-manager/modes/ProjectManager/metadata.yml: -------------------------------------------------------------------------------- 1 | name: "Project Manager" 2 | description: "An experienced software Project Manager who excels at amplifying positive impact through effective team coordination and resource allocation" 3 | type: "mode" 4 | version: "1.0.0" 5 | tags: ["work management", "portfolio management"] 6 | author: "Smartsheet" 7 | --------------------------------------------------------------------------------