@contextium/cli
Advanced tools
@contextium/cli - npm Package Compare versions
+1
-1
| { | ||
| "name": "@contextium/cli", | ||
| "version": "1.0.3", | ||
| "version": "1.0.4", | ||
| "description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants", | ||
@@ -5,0 +5,0 @@ "keywords": [ |
@@ -6,2 +6,7 @@ --- | ||
| - Bash | ||
| - mcp__contextium__search_marketplace | ||
| - mcp__contextium__get_marketplace_listing | ||
| - mcp__contextium__install_marketplace_listing | ||
| - mcp__contextium__list_agents | ||
| - mcp__contextium__list_skills | ||
| - AskUserQuestion | ||
@@ -11,3 +16,3 @@ --- | ||
| <objective> | ||
| Interact with the Contextium Marketplace — browse what's available, install tools into your workspace, or publish your own skills, agents, and MCP servers. | ||
| Help the user find and install the right tools from the Contextium Marketplace using natural language. Do not dump category lists — understand what they're trying to do and surface the best 5 matches across all types (skills, agents, MCP servers). | ||
| </objective> | ||
@@ -18,36 +23,57 @@ | ||
| <step name="choose_action"> | ||
| Ask the user what they want to do using AskUserQuestion: | ||
| - Question: "What would you like to do on the Marketplace?" | ||
| Ask: "What would you like to do on the Marketplace?" | ||
| - Options: | ||
| - "Browse & install — find skills, agents, or MCP servers to add to my workspace" | ||
| - "Publish — share a skill, agent, or MCP server with the community" | ||
| - "My installs — see what's installed in my workspace" | ||
| - "Find & install — I'll describe what I need" | ||
| - "Publish — share a skill, agent, or MCP server" | ||
| - "My installs — see what's in my workspace" | ||
| </step> | ||
| <step name="browse_and_install"> | ||
| If Browse & install selected: | ||
| <step name="find_and_install"> | ||
| If Find & install selected: | ||
| Ask: "What type of tool are you looking for?" | ||
| - Options: "Skill", "Agent", "MCP Server", "Any" | ||
| Ask: "What are you looking for? Describe what you want to do or what problem you want to solve." | ||
| Ask: "Any keywords to search for? (or press enter to browse all)" | ||
| Wait for a natural language response. Examples: "I want to plan and research my project", "I need something to help with writing", "I want to analyse customer feedback". | ||
| Run the search: | ||
| ```bash | ||
| contextium marketplace list -t <skill|agent|mcp_server> -q "<query>" | ||
| ``` | ||
| From their description, infer intent and search intelligently: | ||
| Omit `-t` if "Any" was selected. Omit `-q` if no keywords given. | ||
| 1. Silently fetch what the user already has in their workspace: | ||
| - **CLI:** `contextium skills list -w <workspace> 2>/dev/null` and `contextium agents list -w <workspace> 2>/dev/null` | ||
| - **MCP:** call list_skills and list_agents | ||
| To see full details of a specific listing: | ||
| ```bash | ||
| contextium marketplace show <slug> | ||
| 2. Search the marketplace across all types using the user's keywords: | ||
| - **CLI:** `contextium marketplace list -q "<extracted keywords>" 2>/dev/null` | ||
| - **MCP:** call mcp__contextium__search_marketplace with the extracted keywords | ||
| 3. Decide which type(s) to prioritise based on what the user described: | ||
| - If they want to extend Claude's capabilities (web access, file parsing, external APIs) → prioritise MCP servers | ||
| - If they want a specialist assistant persona → prioritise agents | ||
| - If they want reusable knowledge or instructions → prioritise skills | ||
| - If something relevant already exists in their workspace → flag it as "you already have this" and skip suggesting it | ||
| 4. From all results, pick the top 5 that best match the intent. If fewer than 5 good matches exist, only show what's relevant — do not pad with irrelevant results. | ||
| Present results like this: | ||
| ``` | ||
| Here are the best matches for what you described: | ||
| Once the user picks a listing, install it: | ||
| ```bash | ||
| contextium marketplace install <slug> -w <workspace> | ||
| 1. **Name** (type: skill / agent / mcp) | ||
| What it does and why it fits what you described. | ||
| 2. **Name** (type: ...) | ||
| ... | ||
| ↗ Already in your workspace: "Name" — this already covers part of what you need. | ||
| ``` | ||
| Confirm installed and tell the user where to find it (Skills page, Agents page, etc.). | ||
| Ask: "Which would you like to install? Give me a number, or say skip." | ||
| If the user picks one, fetch full details and install: | ||
| - **CLI:** `contextium marketplace show <slug>` then `contextium marketplace install <slug> -w <workspace>` | ||
| - **MCP:** call get_marketplace_listing then install_marketplace_listing | ||
| Confirm: `✓ Installed "<Name>" into your workspace.` | ||
| Ask if they want to install another from the list or search for something different. | ||
| </step> | ||
@@ -58,4 +84,2 @@ | ||
| The CLI does not support publishing — direct the user to the web marketplace. | ||
| "Publishing is done via the web UI. Go to https://contextium.io/marketplace and click 'Publish' to share your skill, agent, or MCP server." | ||
@@ -67,12 +91,17 @@ </step> | ||
| The CLI does not have a list-installed command. List the workspace's skills and agents instead: | ||
| Silently fetch the workspace's skills and agents: | ||
| - **CLI:** `contextium skills list -w <workspace> 2>/dev/null` and `contextium agents list -w <workspace> 2>/dev/null` | ||
| - **MCP:** call list_skills and list_agents | ||
| ```bash | ||
| contextium skills list -w <workspace> | ||
| contextium agents list -w <workspace> | ||
| ``` | ||
| Show what's available and offer to install more from the marketplace. | ||
| Show a clean list grouped by type. Offer to search for more. | ||
| </step> | ||
| </process> | ||
| <rules> | ||
| - Never ask the user to pick a type (skill / agent / MCP) — infer it from what they describe | ||
| - Never show all marketplace items — always filter to top 5 relevant results | ||
| - Always check what the user already has before suggesting installs | ||
| - Do not show raw CLI output, IDs, or slugs to the user | ||
| - If search returns nothing useful, say so and ask them to rephrase | ||
| </rules> |
@@ -173,2 +173,11 @@ --- | ||
| <step name="load_workflow"> | ||
| After all resources are created, automatically load the workflow without asking the user. Run silently: | ||
| **CLI:** `contextium workflow load "<workflow-name>" --workspace <slug> 2>/dev/null` | ||
| **MCP:** call mcp__contextium__load_workflow with the workflow name and workspace. | ||
| Do not tell the user to load it themselves — just load it as part of setup. | ||
| </step> | ||
| <step name="summary"> | ||
@@ -185,5 +194,3 @@ Show a clean final summary: | ||
| Tags: <list, or none> | ||
| Workflow: <name> | ||
| Load it anytime with /ium:workflow. | ||
| Workflow: <name> — loaded and ready | ||
| ``` | ||
@@ -190,0 +197,0 @@ |
New alerts
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Fixed alerts
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
Improved metrics
- Total package byte prevSize
499163
0.49%No dependency changes