opencode-skills-collection 4.1.15 → 4.1.16

package/bundled-skills/mcp-server-security/references/details.md

@@ -13,7 +13,7 @@ Define strict schemas for every tool's input. Reject anything that does not conf
 import Ajv from "ajv";
 import addFormats from "ajv-formats";
 
-const ajv = new Ajv({ allErrors: true, removeAdditional: true });
+const ajv = new Ajv({ allErrors: true, removeAdditional: false });
 addFormats(ajv);
 
 // Schema registry keyed by tool name
@@ -23,7 +23,7 @@ const toolSchemas: Record<string, object> = {
     properties: {
       path: {
         type: "string",
-        pattern: "^[a-zA-Z0-9_/\\-.]+$",  // No path traversal chars
+        pattern: "^[a-zA-Z0-9_/\\-.]+$",  // Character filter only; resolveSafePath enforces containment
         maxLength: 256,
       },
     },
@@ -33,15 +33,10 @@ const toolSchemas: Record<string, object> = {
   query_database: {
     type: "object",
     properties: {
-      query: { type: "string", maxLength: 2048 },
-      database: { type: "string", enum: ["analytics", "public_catalog"] },
-      parameters: {
-        type: "array",
-        items: { type: ["string", "number", "boolean"] },
-        maxItems: 20,
-      },
+      queryId: { type: "string", enum: ["public_item"] },
+      itemId: { type: "string", minLength: 1, maxLength: 128 },
     },
-    required: ["query", "database"],
+    required: ["queryId", "itemId"],
     additionalProperties: false,
   },
 };
@@ -65,46 +60,28 @@ statement-level restrictions.
 
 ```typescript
 // src/safeSql.ts
-const FORBIDDEN_PATTERNS = [
-  /;\s*(DROP|ALTER|TRUNCATE|DELETE|UPDATE|INSERT|CREATE|GRANT|REVOKE)/i,
-  /UNION\s+SELECT/i,
-  /INTO\s+OUTFILE/i,
-  /LOAD_FILE\s*\(/i,
-  /xp_cmdshell/i,
-];
-
-export function sanitizeSqlQuery(query: string): { safe: boolean; reason?: string } {
-  for (const pattern of FORBIDDEN_PATTERNS) {
-    if (pattern.test(query)) {
-      return { safe: false, reason: `Query matches forbidden pattern: ${pattern}` };
-    }
-  }
-
-  // Only allow SELECT statements
-  const trimmed = query.trim().toUpperCase();
-  if (!trimmed.startsWith("SELECT")) {
-    return { safe: false, reason: "Only SELECT queries are permitted" };
-  }
-
-  return { safe: true };
-}
+// Illustrative handler: db must be a dedicated read-only role with scoped views,
+// statement timeout, and revoked unsafe function privileges. No arbitrary SQL input.
+const QUERIES = {
+  public_item: "SELECT id, name FROM public_catalog WHERE id = $1 LIMIT 1",
+};
 
-// Usage in a database tool handler
-export async function handleDatabaseQuery(params: { query: string; parameters?: any[] }, db: any) {
-  const check = sanitizeSqlQuery(params.query);
-  if (!check.safe) {
-    throw new Error(`Query rejected: ${check.reason}`);
-  }
-  // Always use parameterized execution
-  return db.query(params.query, params.parameters || []);
+export async function handleDatabaseQuery(
+  params: { queryId: string; itemId: string }, db: any
+) {
+  if (params.queryId !== "public_item") throw new Error("Unknown query ID");
+  return db.query(QUERIES.public_item, [params.itemId]);
 }
 ```
 
+The fixed queries, schema and database role must agree. A keyword blacklist cannot establish read-only SQL.
+
 ### 6.3 Filesystem Path Injection Prevention
 
 ```typescript
 // src/safePath.ts
 import path from "path";
+import { realpathSync } from "fs";
 
 const SANDBOX_ROOT = "/home/mcpuser/workspace";
 
@@ -117,45 +94,28 @@ export function resolveSafePath(userPath: string): string {
   }
 
   // Block symlink escape
-  const real = require("fs").realpathSync.native(resolved);
-  if (!real.startsWith(SANDBOX_ROOT)) {
+  const real = realpathSync.native(resolved);
+  const rootReal = realpathSync.native(SANDBOX_ROOT);
+  if (real !== rootReal && !real.startsWith(rootReal + path.sep)) {
     throw new Error(`Symlink escape blocked: "${userPath}" -> "${real}"`);
   }
 
-  return resolved;
+  return real;
 }
 ```
 
 ---
 
 
+Containment applies to existing read targets only. A concurrently mutable directory can still race between checking and opening; use OS confinement and descriptor-based APIs for hostile writers. Do not reuse this helper for creation or writes.
+
 ## 7. Resource Access Control
 
 ### 7.1 Filesystem Sandboxing
 
 Use OS-level controls in addition to application-level path validation.
 
-```bash
-#!/usr/bin/env bash
-# run-mcp-sandboxed.sh - Launch MCP server with Linux namespace sandboxing
-
-exec unshare --map-root-user --mount --pid --fork -- bash -c '
-  # Create a read-only bind mount for the workspace
-  mount --bind /home/mcpuser/workspace /home/mcpuser/workspace
-  mount -o remount,ro,bind /home/mcpuser/workspace
-
-  # Make the writable output directory available
-  mount --bind /home/mcpuser/output /home/mcpuser/output
-
-  # Block access to sensitive host paths
-  mount -t tmpfs tmpfs /etc/ssh
-  mount -t tmpfs tmpfs /root
-  mount -t tmpfs tmpfs /home/mcpuser/.ssh
-
-  # Run the MCP server
-  exec node /opt/mcp-server/dist/index.js
-'
-```
+Use a reviewed container or sandbox policy with a minimal filesystem, scoped mounts, no host credentials, enforced egress and a nonprivileged user. User/mount namespaces alone do not hide the rest of the host or deny networking. Verify denied-path and egress tests in the actual environment before claiming confinement. This guide does not bundle a complete Linux launcher.
 
 ### 7.2 Database Query Restrictions
 
@@ -167,8 +127,8 @@ CREATE ROLE mcp_readonly WITH LOGIN PASSWORD 'use-a-vault-generated-secret';
 
 -- Grant read-only access to specific schemas only
 GRANT USAGE ON SCHEMA public TO mcp_readonly;
-GRANT SELECT ON ALL TABLES IN SCHEMA public TO mcp_readonly;
-ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO mcp_readonly;
+GRANT SELECT ON public.public_catalog TO mcp_readonly;
+-- No blanket present/future-table grants. Review each exposed view and function.
 
 -- Restrict row-level access where needed
 ALTER TABLE customer_data ENABLE ROW LEVEL SECURITY;
@@ -188,16 +148,6 @@ Prevent MCP tools from reaching internal services (SSRF mitigation):
 ```typescript
 // src/networkPolicy.ts
 import { URL } from "url";
-import net from "net";
-
-const BLOCKED_CIDRS = [
-  "10.0.0.0/8",
-  "172.16.0.0/12",
-  "192.168.0.0/16",
-  "127.0.0.0/8",
-  "169.254.169.254/32",   // Cloud metadata endpoint
-  "fd00::/8",
-];
 
 const ALLOWED_DOMAINS = [
   "api.github.com",
@@ -213,7 +163,8 @@ export function validateOutboundUrl(urlString: string): { allowed: boolean; reas
   }
 
   // Block non-HTTPS
-  if (parsed.protocol !== "https:") {
+  if (parsed.protocol !== "https:" || parsed.username || parsed.password ||
+      (parsed.port && parsed.port !== "443")) {
     return { allowed: false, reason: "Only HTTPS is allowed" };
   }
 
@@ -226,8 +177,9 @@ export function validateOutboundUrl(urlString: string): { allowed: boolean; reas
 }
 ```
 
----
+This helper checks URL syntax and exact hosts only. The actual client must disable redirects or revalidate each hop, resolve and reject every private/reserved address, bind the connection to validated addresses, and enforce proxy/egress controls. An allowlisted hostname alone cannot prevent DNS rebinding.
 
+---
 
 ## 8. Rate Limiting
 
@@ -367,13 +319,15 @@ function redactSensitive(params: Record<string, unknown>): Record<string, unknow
 export function logToolInvocation(entry: Omit<AuditEntry, "id" | "timestamp">): AuditEntry {
   const full: AuditEntry = {
     ...entry,
+    error: entry.error ? "tool_failed" : undefined,
     id: randomUUID(),
     timestamp: new Date().toISOString(),
-    parameters: redactSensitive(entry.parameters),
+    // Do not retain tool values: free-text/body/path fields may contain secrets.
+    parameters: { keys: Object.keys(entry.parameters).filter(k => !REDACT_KEYS.some(r => k.toLowerCase().includes(r))) },
   };
 
-  // Write structured JSON to stdout for collection by log aggregator
-  process.stdout.write(JSON.stringify(full) + "\n");
+  // stdio stdout is reserved for MCP protocol frames; send audit to stderr.
+  process.stderr.write(JSON.stringify(full) + "\n");
   return full;
 }
 ```
@@ -388,6 +342,8 @@ import { OTLPTraceExporter } from "@opentelemetry/exporter-trace-otlp-http";
 import { BatchSpanProcessor } from "@opentelemetry/sdk-trace-base";
 import { Resource } from "@opentelemetry/resources";
 
+// SDK-version-specific setup: bind resource/provider APIs to the installed version.
+// Configure a verified collector and authorized telemetry retention before export.
 const provider = new NodeTracerProvider({
   resource: new Resource({
     "service.name": "mcp-server",
@@ -420,8 +376,8 @@ export async function traceToolCall<T>(
       span.setStatus({ code: SpanStatusCode.OK });
       return result;
     } catch (err: any) {
-      span.setStatus({ code: SpanStatusCode.ERROR, message: err.message });
-      span.recordException(err);
+      span.setStatus({ code: SpanStatusCode.ERROR, message: "tool_failed" });
+      // Do not export raw exception messages or stacks containing tool data.
       throw err;
     } finally {
       span.end();
@@ -465,6 +421,8 @@ RUN mkdir -p /home/mcp/workspace /home/mcp/output && \
 
 USER mcp
 
+# HTTP transport example only: implement the authorized health endpoint first.
+# A stdio server does not expose this port. Pin a reviewed base-image digest.
 # Health check
 HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
   CMD node -e "fetch('http://localhost:3001/health').then(r => process.exit(r.ok ? 0 : 1))"
@@ -513,7 +471,7 @@ spec:
       ports:
         - protocol: TCP
           port: 5432
-    # Allow HTTPS outbound to specific external APIs
+    # Broad public IPv4 HTTPS; this cannot restrict destinations by hostname.
     - to:
         - ipBlock:
             cidr: 0.0.0.0/0
@@ -552,7 +510,7 @@ spec:
 }
 ```
 
-Apply the seccomp profile in your Kubernetes pod spec:
+The profile is an illustrative starting point, not a tested Node sandbox. Validate architecture/runtime syscall needs and install the profile on each node before using Localhost. Prefer the platform RuntimeDefault profile unless a measured custom profile is maintained. Apply only after that validation:
 
 ```yaml
 # k8s/deployment.yaml (relevant snippet)
@@ -634,7 +592,12 @@ describe("Input Validation", () => {
   for (const input of maliciousInputs) {
     it(`should reject malicious read_file input: ${JSON.stringify(input)}`, () => {
       const result = validateToolInput("read_file", input);
-      expect(result.valid).toBe(false);
+      // Character validation is separate from existing-target containment.
+      if (input.path === "../../../etc/passwd" || input.path === "/etc/shadow") {
+        expect(result.valid).toBe(true); // resolveSafePath must then reject this target
+      } else {
+        expect(result.valid).toBe(false);
+      }
     });
   }
 
@@ -652,9 +615,7 @@ describe("Input Validation", () => {
   for (const input of sqlInjections) {
     it(`should reject SQL injection: ${input.query.slice(0, 40)}...`, () => {
       const result = validateToolInput("query_database", input);
-      // Even if schema validation passes, the SQL sanitizer should catch it
-      expect(result.valid).toBe(true); // schema is valid
-      // The SQL check happens at the handler level - tested separately
+      expect(result.valid).toBe(false); // raw SQL is not part of the accepted schema
     });
   }
 });

package/bundled-skills/memory-forensics/SKILL.md

@@ -25,7 +25,6 @@ Comprehensive techniques for acquiring, analyzing, and extracting artifacts from
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Memory Acquisition
 

package/bundled-skills/mermaid-expert/SKILL.md

@@ -8,8 +8,8 @@ date_added: '2026-02-27'
 
 ## Use this skill when
 
-- Working on mermaid expert tasks or workflows
-- Needing guidance, best practices, or checklists for mermaid expert
+- Converting verified processes, interactions, schemas or state transitions into a Mermaid diagram.
+- Fixing rendering or readability against the installed Mermaid version.
 
 ## Do not use this skill when
 
@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are a Mermaid diagram expert specializing in clear, professional visualizations.
 
@@ -55,9 +54,11 @@ gitGraph, journey, quadrantChart, timeline
 - Accessibility considerations
 - Export recommendations
 
-Always provide both basic and styled versions. Include comments explaining complex syntax.
+Provide the requested version; add alternatives only when useful. Include comments explaining complex syntax.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
 - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+Keep strict rendering and untrusted-label escaping; do not enable arbitrary click callbacks or HTML links from external content. Diagram structure must follow verified system facts. Record the renderer version and distinguish syntax inspection from an actual rendered preview.

package/bundled-skills/minecraft-bukkit-pro/SKILL.md

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are a Minecraft plugin development master specializing in Bukkit, Spigot, and Paper server APIs with deep knowledge of internal mechanics and modern development patterns.
 

package/bundled-skills/mirrord/SKILL.md

@@ -2,7 +2,7 @@
 name: mirrord
 description: "Run a local process inside a live Kubernetes cluster's network, env and traffic with mirrord, so changes are tested against real services without deploying."
 category: devops
-risk: safe
+risk: critical
 source: "https://github.com/metalbear-co/skills"
 source_repo: "metalbear-co/skills"
 source_type: official
@@ -57,10 +57,10 @@ Incoming traffic is mirrored by default. To take over the target's traffic inste
 ### Step 4: Verify
 
 ```bash
-mirrord exec --target deployment/<name> -- env
+# Verify an explicitly selected non-secret variable or service identity without printing the pod environment.
 ```
 
-The output should include the pod's environment variables.
+Confirm the exact target and mode through sanitized configuration/status, then an approved synthetic read. Never dump environment credentials.
 
 ## Examples
 
@@ -88,3 +88,5 @@ mirrord exec --target deployment/api -- python main.py
 
 - Needs kubectl access to the target cluster and a Linux node kernel 4.20+
 - Team features (concurrent steal on one target, database branching, queue splitting, preview environments) need the mirrord Operator. On a cluster without a license, an agent can offer the user a trial; see https://metalbear.com/agents.md and ask before starting it.
+
+Running locally can still modify shared databases, send messages, consume queues or incur provider charges through mirrored network/environment access. Confirm a staging context/namespace and isolated data, inspect the actual mirrord mode/version, and disable unneeded filesystem/environment/network capabilities. Mirror mode is not an automatic read-only sandbox; stealing traffic or trial/license activation needs specific authorization. Reconcile side effects before retries.

package/bundled-skills/ml-engineer/SKILL.md

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are an ML engineer specializing in production machine learning systems, model serving, and ML infrastructure.
 

package/bundled-skills/ml-pipeline-workflow/SKILL.md

@@ -5,6 +5,16 @@ risk: critical
 source: community
 date_added: "2026-02-27"
 ---
+## Supporting material availability
+
+This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
+
+- `<support-root>/assets/pipeline-dag.yaml.template`
+- `<support-root>/references/data-preparation.md`
+- `<support-root>/references/model-training.md`
+
+Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
+
 
 # ML Pipeline Workflow
 
@@ -20,7 +30,6 @@ Complete end-to-end MLOps pipeline orchestration from data preparation through m
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Overview
 

package/bundled-skills/mlops-engineer/SKILL.md

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are an MLOps engineer specializing in ML infrastructure, automation, and production ML systems across cloud platforms.
 

package/bundled-skills/mobile-security-coder/SKILL.md

@@ -21,7 +21,6 @@ date_added: '2026-02-27'
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 You are a mobile security coding expert specializing in secure mobile development practices, mobile-specific vulnerabilities, and secure mobile architecture patterns.
 

package/bundled-skills/monopoly/SKILL.md

@@ -6,6 +6,18 @@ risk: none
 source: community
 date_added: "2026-09-04"
 ---
+## Supporting material availability
+
+This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files:
+
+- `<support-root>/references/patterns.md`
+- `<support-root>/references/tech-matrix.md`
+- `<support-root>/references/scale-benchmarks.md`
+- `<support-root>/references/security-checklist.md`
+- `<support-root>/references/cost-estimation.md`
+
+Ask for the original supporting material or an existing installation before using a step that depends on these paths; this catalog does not identify a verified download source for them. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable.
+
 
 # MONOPOLY — Senior System Design Engineer
 

package/bundled-skills/monopoly/security-checklist/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: security-checklist
-description: Reference document for monopoly security-checklist.
+description: Review a scoped architecture against evidence-based network, identity, data, secrets, dependency and incident-response controls.
 source: community
 date_added: "2026-09-04"
 risk: safe
@@ -10,7 +10,7 @@ reports-to: monopoly
 # MONOPOLY — Security Hardening Checklist
 
 ## When to Use
-- Use this skill when the task matches this description: Reference document for monopoly security-checklist.
+- Use this skill when the task matches this description: Review a scoped architecture against evidence-based network, identity, data, secrets, dependency and incident-response controls.
 
 ## Network Security
 - [ ] All services inside private VPC; only LB/API GW exposed publicly
@@ -21,7 +21,7 @@ reports-to: monopoly
 - [ ] VPN or Private Link for inter-service communication in multi-region
 
 ## Authentication & Authorization
-- [ ] JWT tokens with short expiry (15 min access, 7 day refresh)
+- [ ] Token lifetimes, renewal and revocation follow a threat model; sample lifetimes are not universal requirements
 - [ ] OAuth 2.0 / OIDC for third-party auth
 - [ ] MFA enforced for admin accounts
 - [ ] RBAC or ABAC for authorization
@@ -34,7 +34,7 @@ reports-to: monopoly
 - [ ] SQL injection prevention (parameterized queries, ORM)
 - [ ] XSS prevention (output encoding, CSP headers)
 - [ ] CSRF protection (SameSite cookies, CSRF tokens)
-- [ ] CORS policy locked down (not wildcard `*`)
+- [ ] CORS matches the trust model; private credentialed APIs differ from public non-credentialed resources
 - [ ] HTTP security headers (HSTS, X-Frame-Options, X-Content-Type-Options)
 
 ## Data Security
@@ -60,12 +60,12 @@ reports-to: monopoly
 - [ ] Audit logs for all admin actions and data access
 - [ ] Alerting on anomalous access patterns
 - [ ] Incident response runbook documented
-- [ ] Data breach notification process defined (GDPR 72-hour rule)
+- [ ] Breach assessment and notification process matches the applicable jurisdiction, trigger, recipient and legal timeframe
 - [ ] Regular penetration testing scheduled
 
 ## Compliance (as applicable)
-- [ ] GDPR: data residency, right to deletion, consent tracking
-- [ ] PCI-DSS: if handling card data — never store raw PANs
+- [ ] GDPR: lawful basis, transparency, rights, retention and lawful transfer safeguards where applicable
+- [ ] PCI-DSS: establish card-data scope and current storage, masking, encryption and sensitive-authentication-data restrictions
 - [ ] HIPAA: if health data — encryption, audit logs, BAA with vendors
 - [ ] SOC 2 Type II: access control, availability, confidentiality evidence
 
@@ -77,3 +77,5 @@ reports-to: monopoly
 
 ## Limitations
 - This is a reference document and may not cover all edge cases. Always verify architectures before production.
+
+This checklist is not certification, legal advice or permission to apply controls. Verify current primary standards and actual architecture before marking compliance; a WAF, ORM, token or encrypted database does not prove the corresponding control. Do not force every cloud product onto a smaller system. Link each finding to exact revision, reachable risk and observed evidence.

package/bundled-skills/monorepo-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: monorepo-architect
-description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,"
+description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use for scoped monorepo setup, build or dependency review."
 risk: safe
 source: community
 date_added: "2026-02-27"
@@ -8,7 +8,7 @@ date_added: "2026-02-27"
 
 # Monorepo Architect
 
-Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
+Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use for scoped monorepo setup, build or dependency review. build optimization, or scaling development workflows across teams.
 
 ## Do not use this skill when
 
@@ -20,7 +20,6 @@ Expert in monorepo architecture, build systems, and dependency management at sca
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
 
 ## Capabilities
 
@@ -56,7 +55,7 @@ Expert in monorepo architecture, build systems, and dependency management at sca
 
 - Start with clear project boundaries
 - Use consistent naming conventions
-- Implement remote caching early
+- Use remote caching only when authorized and justified; review private artifact/credential transmission and cross-tenant cache integrity
 - Keep shared libraries focused
 - Use tags for dependency constraints
 - Automate dependency updates
@@ -73,3 +72,5 @@ Expert in monorepo architecture, build systems, and dependency management at sca
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
 - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+Preserve the existing build/package manager unless migration is requested. Verify cache keys cover sources, lockfiles, tools and relevant environment; never cache secrets. Check affected-build detection against a full build for cross-project changes before trusting it to omit required checks.

package/bundled-skills/monte-carlo-analyze-root-cause/SKILL.md

@@ -9,6 +9,10 @@ date_added: 2026-07-01
 license: Apache-2.0
 license_source: https://github.com/monte-carlo-data/mc-agent-toolkit/blob/main/LICENSE
 ---
+## Bundled upstream support
+
+Supporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.
+
 ## When to Use
 
 - Use when the user goal matches this upstream workflow.