> ## Documentation Index > Fetch the complete documentation index at: https://docs.oqoqo.ai/llms.txt > Use this file to discover all available pages before exploring further. # Skills, MCP servers, CLIs, and SDKs > Create skills, MCP servers, CLIs, and SDKs, import from GitHub, and attach them to treatments. Plugins coming soon. **Assets** are what you attach to a **treatment**. Tasks own files and machines. Treatments own the interfaces you are testing. See [Core concepts](/core-concepts). Create assets under **Manage → Assets**. Attach them under **Manage → Treatments**. Assets page with Skills, MCP servers, CLIs, and SDKs. Assets page with Skills, MCP servers, CLIs, and SDKs. This page is about catalog assets you evaluate as product interfaces. It is separate from the [Oqoqo MCP](/operate/mcp) server that operates your workspace. ## What each asset is for | Asset | Typical use | What to test | | -------------- | ----------------------------------------------------------------- | ------------------------------------------------------------- | | **Skill** | Instructions and helpers the agent should follow for your product | Description match, load behavior, pass-rate lift | | **MCP server** | Tools your product exposes to agents over MCP | Distinct names, clear descriptions, correct first tool choice | | **CLI** | A command-line interface agents install and call | Help text, error messages, discoverable subcommands | | **SDK** | A library agents import and use | Method names, examples, errors that point to the right fix | ## Create an asset 1. Open **Manage**, then Skills, MCP servers, CLIs, or SDKs. 2. Create the asset and fill in the definition the agent will see. 3. Save. These assets are versioned, so past experiments keep the version they launched with. For remote MCP servers, enter URLs and headers in the dashboard. Secret header values stay in the web app. Remote MCP servers can connect with OAuth when the server supports it. ## Import from GitHub For **Skills** and **Files**, you can add content from GitHub as well as upload. 1. Open the import dialog and choose **From GitHub**. 2. Paste a public `github.com` URL. 3. Oqoqo snapshots the content at the resolved commit. Later, use **Check for updates** on a GitHub-sourced skill or folder. Skills get a new version when content changes. Folders replace the live record. Private-repo GitHub import is not available. CLI and MCP can also apply GitHub-sourced resources. See [Machines and files](/experiments/machines-and-files) for Files. ## Attach to a treatment 1. Open **Manage → Treatments**. 2. Create or edit a treatment. 3. Attach the skills, MCP servers, CLIs, or SDKs for that condition. 4. Keep a baseline treatment (usually the raw agent) so you can measure lift. See [Treatments](/experiments/treatments). ## Compare Add the baseline and your treatment to the same experiment, on the same tasks. Those tasks already carry their files and machines. Launch with enough trials to trust the pass rate. Read **Matrix** for lift and **Frictions** for what still blocks agents. ## Plugins **Manage → Assets → Plugins** is in the product navigation and marked **Coming soon**. Plugins will bundle skills, agents, hooks, MCP servers, and other capabilities into one versioned package. Do not treat Plugins as available today. ## Related pages Attach assets and measure lift. Start from Stripe interface evals and skill lift. Operate Oqoqo itself from an agent host. Compare treatments in an experiment.