@cubis/foundry 0.3.49 → 0.3.51

package/workflows/workflows/agent-environment-setup/platforms/antigravity/rules/GEMINI.md

@@ -100,6 +100,15 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 4. `skill_get <id>` — load full skill content; only when committed to using it
 5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
 
+### Postman Intent Trigger (Required)
+
+When user intent includes Postman workflows (for example: workspace, collection, environment, runCollection, monitor, mock, or "run Postman tests"):
+
+1. Run `skill_search "postman"` first.
+2. If `postman` skill exists, load `skill_get "postman"` before workflow/agent routing.
+3. Prefer Postman MCP tools (`postman.*`) over Newman/CLI fallback unless the user explicitly asks for fallback.
+4. If `--postman` was installed but `postman` skill cannot be found, report installation drift and suggest reinstall with `cbx workflows install ... --postman`.
+
 **Hard rules:**
 
 - Never call `skill_get` without a prior `skill_search` or `skill_browse_category`
@@ -264,7 +273,7 @@ The Foundry MCP server provides progressive-disclosure skill discovery and integ
 ### Skill Vault
 
 - **123** skills across **22** categories
-- Estimated full catalog: ~108,488 tokens
+- Estimated full catalog: ~109,067 tokens
 
 Categories:
 - `ai`: 1 skill(s)

package/workflows/workflows/agent-environment-setup/platforms/codex/rules/AGENTS.md

@@ -98,6 +98,15 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 4. `skill_get <id>` — load full skill content; only when committed to using it
 5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
 
+### Postman Intent Trigger (Required)
+
+When user intent includes Postman workflows (for example: workspace, collection, environment, runCollection, monitor, mock, or "run Postman tests"):
+
+1. Run `skill_search "postman"` first.
+2. If `postman` skill exists, load `skill_get "postman"` before workflow/agent routing.
+3. Prefer Postman MCP tools (`postman.*`) over Newman/CLI fallback unless the user explicitly asks for fallback.
+4. If `--postman` was installed but `postman` skill cannot be found, report installation drift and suggest reinstall with `cbx workflows install ... --postman`.
+
 **Hard rules:**
 
 - Never call `skill_get` without a prior `skill_search` or `skill_browse_category`
@@ -257,7 +266,7 @@ The Foundry MCP server provides progressive-disclosure skill discovery and integ
 ### Skill Vault
 
 - **123** skills across **22** categories
-- Estimated full catalog: ~108,488 tokens
+- Estimated full catalog: ~109,067 tokens
 
 Categories:
 - `ai`: 1 skill(s)

package/workflows/workflows/agent-environment-setup/platforms/copilot/rules/AGENTS.md

@@ -104,6 +104,15 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 4. `skill_get <id>` — load full skill content; only when committed to using it
 5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
 
+### Postman Intent Trigger (Required)
+
+When user intent includes Postman workflows (for example: workspace, collection, environment, runCollection, monitor, mock, or "run Postman tests"):
+
+1. Run `skill_search "postman"` first.
+2. If `postman` skill exists, load `skill_get "postman"` before workflow/agent routing.
+3. Prefer Postman MCP tools (`postman.*`) over Newman/CLI fallback unless the user explicitly asks for fallback.
+4. If `--postman` was installed but `postman` skill cannot be found, report installation drift and suggest reinstall with `cbx workflows install ... --postman`.
+
 **Hard rules:**
 
 - Never call `skill_get` without a prior `skill_search` or `skill_browse_category`
@@ -263,7 +272,7 @@ The Foundry MCP server provides progressive-disclosure skill discovery and integ
 ### Skill Vault
 
 - **123** skills across **22** categories
-- Estimated full catalog: ~108,488 tokens
+- Estimated full catalog: ~109,067 tokens
 
 Categories:
 - `ai`: 1 skill(s)

package/workflows/workflows/agent-environment-setup/platforms/copilot/rules/copilot-instructions.md

@@ -104,6 +104,15 @@ Stop at the earliest step that gives enough signal. Do not jump ahead.
 4. `skill_get <id>` — load full skill content; only when committed to using it
 5. `skill_budget_report` — verify token cost after loading; triggers the compact ctx stamp
 
+### Postman Intent Trigger (Required)
+
+When user intent includes Postman workflows (for example: workspace, collection, environment, runCollection, monitor, mock, or "run Postman tests"):
+
+1. Run `skill_search "postman"` first.
+2. If `postman` skill exists, load `skill_get "postman"` before workflow/agent routing.
+3. Prefer Postman MCP tools (`postman.*`) over Newman/CLI fallback unless the user explicitly asks for fallback.
+4. If `--postman` was installed but `postman` skill cannot be found, report installation drift and suggest reinstall with `cbx workflows install ... --postman`.
+
 **Hard rules:**
 
 - Never call `skill_get` without a prior `skill_search` or `skill_browse_category`
@@ -263,7 +272,7 @@ The Foundry MCP server provides progressive-disclosure skill discovery and integ
 ### Skill Vault
 
 - **123** skills across **22** categories
-- Estimated full catalog: ~108,488 tokens
+- Estimated full catalog: ~109,067 tokens
 
 Categories:
 - `ai`: 1 skill(s)

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/postman/SKILL.md

@@ -1,17 +1,80 @@
 ---
 name: postman
-description: Automate API testing and collection management with Postman MCP. Use for workspace, collection, environment, and mock operations.
+description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
 ---
 
 # Postman MCP
 
 Use this skill when you need to work with Postman through MCP tools.
 
+## MCP-First Rule
+
+- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
+- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+
 ## Required Environment Variables
 
-- `POSTMAN_API_KEY_<PROFILE>` for authenticated Postman access.
+- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
+- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+
+## Preflight Checklist
+
+1. Read Postman status first:
+   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
+2. Validate connectivity and mode:
+   - If not configured, report missing env alias/config and stop.
+   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+3. Discover upstream tools:
+   - Prefer `postman.getEnabledTools` when available.
+   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+
+## Default Workspace ID Policy
+
+Resolve workspace in this order:
+
+1. User-provided workspace ID.
+2. `postman_get_status.defaultWorkspaceId`.
+3. Auto-detect from `postman.getWorkspaces`:
+   - If exactly one workspace exists, use it and state that choice.
+4. If multiple workspaces and no default:
+   - Ask user to choose one.
+   - Recommend persisting it with:
+     - `cbx workflows config --scope global --workspace-id <workspace-id>`
+
+When a Postman tool requires a workspace argument, always pass the resolved workspace ID explicitly.
+
+## Common Workflows
+
+### List/Inspect
+
+- `postman.getWorkspaces`
+- `postman.getCollections` (with resolved workspace ID)
+- `postman.getEnvironments` (with resolved workspace ID)
+
+### Collection Run
+
+1. Resolve workspace ID (policy above).
+2. Resolve `collectionId` and optional `environmentId`.
+3. Call `postman.runCollection`.
+4. Return a concise run summary:
+   - total requests
+   - passed/failed tests
+   - failing request/test names
+   - proposed fix path for failures
+
+## Failure Handling
+
+If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+
+1. Verify env alias expected by config is set.
+2. Resync catalog:
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
+3. Recreate runtime if needed:
+   - `cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
 
-## Notes
+## Security Notes
 
 - Use environment variables for secrets. Do not inline API keys.
-- Prefer tool discovery (`getEnabledTools`) before making assumptions about available tool sets.
+- Never print or persist raw key values in logs, docs, or responses.

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/postman/SKILL.md

@@ -1,17 +1,80 @@
 ---
 name: postman
-description: Automate API testing and collection management with Postman MCP. Use for workspace, collection, environment, and mock operations.
+description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
 ---
 
 # Postman MCP
 
 Use this skill when you need to work with Postman through MCP tools.
 
+## MCP-First Rule
+
+- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
+- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+
 ## Required Environment Variables
 
-- `POSTMAN_API_KEY_<PROFILE>` for authenticated Postman access.
+- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
+- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+
+## Preflight Checklist
+
+1. Read Postman status first:
+   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
+2. Validate connectivity and mode:
+   - If not configured, report missing env alias/config and stop.
+   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+3. Discover upstream tools:
+   - Prefer `postman.getEnabledTools` when available.
+   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+
+## Default Workspace ID Policy
+
+Resolve workspace in this order:
+
+1. User-provided workspace ID.
+2. `postman_get_status.defaultWorkspaceId`.
+3. Auto-detect from `postman.getWorkspaces`:
+   - If exactly one workspace exists, use it and state that choice.
+4. If multiple workspaces and no default:
+   - Ask user to choose one.
+   - Recommend persisting it with:
+     - `cbx workflows config --scope global --workspace-id <workspace-id>`
+
+When a Postman tool requires a workspace argument, always pass the resolved workspace ID explicitly.
+
+## Common Workflows
+
+### List/Inspect
+
+- `postman.getWorkspaces`
+- `postman.getCollections` (with resolved workspace ID)
+- `postman.getEnvironments` (with resolved workspace ID)
+
+### Collection Run
+
+1. Resolve workspace ID (policy above).
+2. Resolve `collectionId` and optional `environmentId`.
+3. Call `postman.runCollection`.
+4. Return a concise run summary:
+   - total requests
+   - passed/failed tests
+   - failing request/test names
+   - proposed fix path for failures
+
+## Failure Handling
+
+If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+
+1. Verify env alias expected by config is set.
+2. Resync catalog:
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
+3. Recreate runtime if needed:
+   - `cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
 
-## Notes
+## Security Notes
 
 - Use environment variables for secrets. Do not inline API keys.
-- Prefer tool discovery (`getEnabledTools`) before making assumptions about available tool sets.
+- Never print or persist raw key values in logs, docs, or responses.

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/postman/SKILL.md

@@ -1,17 +1,80 @@
 ---
 name: postman
-description: Automate API testing and collection management with Postman MCP. Use for workspace, collection, environment, and mock operations.
+description: Use Postman MCP tools for workspace, collection, environment, and run workflows with explicit default-workspace handling.
 ---
 
 # Postman MCP
 
 Use this skill when you need to work with Postman through MCP tools.
 
+## MCP-First Rule
+
+- Prefer Postman MCP tools (`postman.*`) for all Postman operations.
+- Do not use Newman/Postman CLI fallback unless the user explicitly asks for fallback.
+- If required Postman MCP tools are unavailable, stop and report the MCP discovery issue with remediation steps.
+
 ## Required Environment Variables
 
-- `POSTMAN_API_KEY_<PROFILE>` for authenticated Postman access.
+- Active profile key alias must be set (typically `POSTMAN_API_KEY_DEFAULT`).
+- `POSTMAN_API_KEY_<PROFILE>` aliases are also valid if the active profile uses them.
+
+## Preflight Checklist
+
+1. Read Postman status first:
+   - Call `postman_get_status` (`scope: auto` unless user requires a scope).
+2. Validate connectivity and mode:
+   - If not configured, report missing env alias/config and stop.
+   - If mode is not `full`, call `postman_set_mode` with `mode: full`.
+3. Discover upstream tools:
+   - Prefer `postman.getEnabledTools` when available.
+   - Confirm required tool names before proceeding (for example `getWorkspaces`, `getCollections`, `runCollection`).
+
+## Default Workspace ID Policy
+
+Resolve workspace in this order:
+
+1. User-provided workspace ID.
+2. `postman_get_status.defaultWorkspaceId`.
+3. Auto-detect from `postman.getWorkspaces`:
+   - If exactly one workspace exists, use it and state that choice.
+4. If multiple workspaces and no default:
+   - Ask user to choose one.
+   - Recommend persisting it with:
+     - `cbx workflows config --scope global --workspace-id <workspace-id>`
+
+When a Postman tool requires a workspace argument, always pass the resolved workspace ID explicitly.
+
+## Common Workflows
+
+### List/Inspect
+
+- `postman.getWorkspaces`
+- `postman.getCollections` (with resolved workspace ID)
+- `postman.getEnvironments` (with resolved workspace ID)
+
+### Collection Run
+
+1. Resolve workspace ID (policy above).
+2. Resolve `collectionId` and optional `environmentId`.
+3. Call `postman.runCollection`.
+4. Return a concise run summary:
+   - total requests
+   - passed/failed tests
+   - failing request/test names
+   - proposed fix path for failures
+
+## Failure Handling
+
+If dynamic Postman tools are missing (only `postman_get_*` / `postman_set_mode` visible):
+
+1. Verify env alias expected by config is set.
+2. Resync catalog:
+   - `cbx mcp tools sync --service postman --scope global`
+   - `cbx mcp tools list --service postman --scope global`
+3. Recreate runtime if needed:
+   - `cbx mcp runtime up --scope global --name cbx-mcp --replace --port 3310 --skills-root ~/.agents/skills`
 
-## Notes
+## Security Notes
 
 - Use environment variables for secrets. Do not inline API keys.
-- Prefer tool discovery (`getEnabledTools`) before making assumptions about available tool sets.
+- Never print or persist raw key values in logs, docs, or responses.