@cubis/foundry 0.3.62 → 0.3.64

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/nestjs-expert/references/secure-sessions.md

@@ -52,5 +52,5 @@ Do not store tokens, passwords, raw PII, or authorization policy blobs.
 
 ## Related
 
-- `references/authentication.md`
-- `references/services-di.md`
+- [authentication.md](authentication.md)
+- [services-di.md](services-di.md)

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/nestjs-expert/references/strangler-fig-pattern.md

@@ -43,5 +43,5 @@ Move route groups from legacy to NestJS in controlled slices while preserving be
 
 ## Related
 
-- `references/migration-from-express.md`
-- `references/authentication.md`
+- [migration-from-express.md](migration-from-express.md)
+- [authentication.md](authentication.md)

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/next-best-practices/SKILL.md

@@ -1,16 +1,16 @@
 ---
 name: next-best-practices
 description: "Rulebook for reviewing/generating Next.js code against Vercel best practices (conventions, RSC boundaries, async APIs, metadata, bundling). Not a migration or feature-implementation skill by itself."
-user-invocable: false
+metadata:
+  user-invocable: false
 ---
-
 # Next.js Best Practices
 
 Apply these rules when writing or reviewing Next.js code.
 
 ## File Conventions
 
-See [file-conventions.md](./file-conventions.md) for:
+See [file-conventions.md](references/file-conventions.md) for:
 - Project structure and special files
 - Route segments (dynamic, catch-all, groups)
 - Parallel and intercepting routes
@@ -20,7 +20,7 @@ See [file-conventions.md](./file-conventions.md) for:
 
 Detect invalid React Server Component patterns.
 
-See [rsc-boundaries.md](./rsc-boundaries.md) for:
+See [rsc-boundaries.md](references/rsc-boundaries.md) for:
 - Async client component detection (invalid)
 - Non-serializable props detection
 - Server Action exceptions
@@ -29,33 +29,33 @@ See [rsc-boundaries.md](./rsc-boundaries.md) for:
 
 Next.js 15+ async API changes.
 
-See [async-patterns.md](./async-patterns.md) for:
+See [async-patterns.md](references/async-patterns.md) for:
 - Async `params` and `searchParams`
 - Async `cookies()` and `headers()`
 - Migration codemod
 
 ## Runtime Selection
 
-See [runtime-selection.md](./runtime-selection.md) for:
+See [runtime-selection.md](references/runtime-selection.md) for:
 - Default to Node.js runtime
 - When Edge runtime is appropriate
 
 ## Directives
 
-See [directives.md](./directives.md) for:
+See [directives.md](references/directives.md) for:
 - `'use client'`, `'use server'` (React)
 - `'use cache'` (Next.js)
 
 ## Functions
 
-See [functions.md](./functions.md) for:
+See [functions.md](references/functions.md) for:
 - Navigation hooks: `useRouter`, `usePathname`, `useSearchParams`, `useParams`
 - Server functions: `cookies`, `headers`, `draftMode`, `after`
 - Generate functions: `generateStaticParams`, `generateMetadata`
 
 ## Error Handling
 
-See [error-handling.md](./error-handling.md) for:
+See [error-handling.md](references/error-handling.md) for:
 - `error.tsx`, `global-error.tsx`, `not-found.tsx`
 - `redirect`, `permanentRedirect`, `notFound`
 - `forbidden`, `unauthorized` (auth errors)
@@ -63,14 +63,14 @@ See [error-handling.md](./error-handling.md) for:
 
 ## Data Patterns
 
-See [data-patterns.md](./data-patterns.md) for:
+See [data-patterns.md](references/data-patterns.md) for:
 - Server Components vs Server Actions vs Route Handlers
 - Avoiding data waterfalls (`Promise.all`, Suspense, preload)
 - Client component data fetching
 
 ## Route Handlers
 
-See [route-handlers.md](./route-handlers.md) for:
+See [route-handlers.md](references/route-handlers.md) for:
 - `route.ts` basics
 - GET handler conflicts with `page.tsx`
 - Environment behavior (no React DOM)
@@ -78,7 +78,7 @@ See [route-handlers.md](./route-handlers.md) for:
 
 ## Metadata & OG Images
 
-See [metadata.md](./metadata.md) for:
+See [metadata.md](references/metadata.md) for:
 - Static and dynamic metadata
 - `generateMetadata` function
 - OG image generation with `next/og`
@@ -86,7 +86,7 @@ See [metadata.md](./metadata.md) for:
 
 ## Image Optimization
 
-See [image.md](./image.md) for:
+See [image.md](references/image.md) for:
 - Always use `next/image` over `<img>`
 - Remote images configuration
 - Responsive `sizes` attribute
@@ -95,7 +95,7 @@ See [image.md](./image.md) for:
 
 ## Font Optimization
 
-See [font.md](./font.md) for:
+See [font.md](references/font.md) for:
 - `next/font` setup
 - Google Fonts, local fonts
 - Tailwind CSS integration
@@ -103,7 +103,7 @@ See [font.md](./font.md) for:
 
 ## Bundling
 
-See [bundling.md](./bundling.md) for:
+See [bundling.md](references/bundling.md) for:
 - Server-incompatible packages
 - CSS imports (not link tags)
 - Polyfills (already included)
@@ -112,7 +112,7 @@ See [bundling.md](./bundling.md) for:
 
 ## Scripts
 
-See [scripts.md](./scripts.md) for:
+See [scripts.md](references/scripts.md) for:
 - `next/script` vs native script tags
 - Inline scripts need `id`
 - Loading strategies
@@ -120,34 +120,33 @@ See [scripts.md](./scripts.md) for:
 
 ## Hydration Errors
 
-See [hydration-error.md](./hydration-error.md) for:
+See [hydration-error.md](references/hydration-error.md) for:
 - Common causes (browser APIs, dates, invalid HTML)
 - Debugging with error overlay
 - Fixes for each cause
 
 ## Suspense Boundaries
 
-See [suspense-boundaries.md](./suspense-boundaries.md) for:
+See [suspense-boundaries.md](references/suspense-boundaries.md) for:
 - CSR bailout with `useSearchParams` and `usePathname`
 - Which hooks require Suspense boundaries
 
 ## Parallel & Intercepting Routes
 
-See [parallel-routes.md](./parallel-routes.md) for:
+See [parallel-routes.md](references/parallel-routes.md) for:
 - Modal patterns with `@slot` and `(.)` interceptors
 - `default.tsx` for fallbacks
 - Closing modals correctly with `router.back()`
 
 ## Self-Hosting
 
-See [self-hosting.md](./self-hosting.md) for:
+See [self-hosting.md](references/self-hosting.md) for:
 - `output: 'standalone'` for Docker
 - Cache handlers for multi-instance ISR
 - What works vs needs extra setup
 
 ## Debug Tricks
 
-See [debug-tricks.md](./debug-tricks.md) for:
+See [debug-tricks.md](references/debug-tricks.md) for:
 - MCP endpoint for AI-assisted debugging
 - Rebuild specific routes with `--debug-build-paths`
-

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/next-cache-components/SKILL.md

@@ -2,7 +2,6 @@
 name: next-cache-components
 description: "Use only for Next.js 16 Cache Components and PPR implementation (use cache, cacheLife, cacheTag, updateTag, Suspense boundaries)."
 ---
-
 # Cache Components (Next.js 16+)
 
 Cache Components enable Partial Prerendering (PPR) - mix static, cached, and dynamic content in a single route.

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

@@ -1,9 +1,9 @@
 ---
 name: next-upgrade
 description: "Use only for upgrading Next.js versions with official migration guides and codemods; includes dependency/version planning and upgrade validation."
-argument-hint: "[target-version]"
+metadata:
+  argument-hint: "[target-version]"
 ---
-
 # Upgrade Next.js
 
 Upgrade the current project to the latest Next.js version following official migration guides.

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

@@ -1,6 +1,5 @@
 ---
 name: "nextjs-developer"
-displayName: "Next.js Developer"
 description: "Use for implementing/refactoring Next.js App Router features, React Server Components/Actions, SEO, and production architecture."
 license: MIT
 metadata:
@@ -10,7 +9,6 @@ metadata:
   stack: "nextjs"
   baseline: "Next.js 16 + React 19"
 ---
-
 # Next.js Developer
 
 ## Scope

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/nextjs-react-expert/SKILL.md

@@ -7,7 +7,6 @@ metadata:
   removal_target: "v0.6.0"
   alias_of: "react-best-practices"
 ---
-
 # nextjs-react-expert (Compatibility Alias)
 
 This skill is deprecated and kept for backward compatibility.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/nodejs-best-practices/SKILL.md

@@ -9,7 +9,6 @@ metadata:
   stack: "nodejs"
   baseline: "Node 22/24 LTS era"
 ---
-
 # Node.js Best Practices
 
 ## Purpose

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

@@ -1,10 +1,7 @@
 ---
 name: "oneup-design"
-displayName: "OneUp Design System"
 description: "OneUp HR design system with One* components, colors, spacing, and typography tokens"
-keywords: ["design", "ui", "component", "color", "spacing", "padding", "typography", "OneText", "OneButton", "OneCard", "widget", "theme"]
 ---
-
 # OneUp Design System
 
 ## Onboarding
@@ -16,9 +13,11 @@ import '../../../../core/design_system/one_design_system.dart';
 
 ## When to Load Steering Files
 
-- Working with colors → `colors.md`
-- Working with spacing/padding → `spacing.md`
-- Using One* components → `components.md`
+| File | Load when |
+| --- | --- |
+| `references/colors.md` | Choosing semantic colors, surface roles, and token-safe palette usage. |
+| `references/spacing.md` | Replacing hard-coded spacing/padding and aligning with token spacing rules. |
+| `references/components.md` | Selecting or reviewing One* components and their expected usage patterns. |
 
 ## MCP Tools (Use Before Writing UI)
 

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

@@ -2,8 +2,6 @@
 name: "openapi-docs"
 description: "Use when writing or updating OpenAPI specifications, defining request/response schemas, or configuring Stoplight Elements (Swagger-style) documentation UI."
 ---
-
-
 # OpenAPI Docs & Stoplight UI
 
 ## Overview

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

@@ -1,9 +1,7 @@
 ---
 name: parallel-agents
 description: Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Native Parallel Agents
 
 > Orchestration through Antigravity's built-in Agent Tool

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

@@ -1,9 +1,7 @@
 ---
 name: performance-profiling
 description: Performance profiling principles. Measurement, analysis, and optimization techniques.
-allowed-tools: Read, Glob, Grep, Bash
 ---
-
 # Performance Profiling
 
 > Measure, analyze, optimize - in that order.

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

@@ -1,9 +1,7 @@
 ---
 name: plan-writing
 description: Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Plan Writing
 
 > Source: obra/superpowers
@@ -31,7 +29,7 @@ This skill provides a framework for breaking down work into clear, actionable ta
 
 ### 4. Dynamic Naming in Project Root
 - Plan files are saved as `{task-slug}.md` in the PROJECT ROOT
-- Name derived from task (e.g., "add auth" → `auth-feature.md`)
+- Name derived from task (e.g., "add auth" -> auth-feature markdown plan in the project root)
 - **NEVER** inside `.claude/`, `docs/`, or temp folders
 
 ## Planning Principles (NOT Templates!)

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

@@ -12,7 +12,6 @@ metadata:
   output-format: code
   related-skills: test-master, react-expert, devops-engineer
 ---
-
 # Playwright Expert
 
 Senior E2E testing specialist with deep expertise in Playwright for robust, maintainable browser automation.

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

@@ -2,7 +2,6 @@
 name: postman
 description: Automate API testing and collection management with Postman MCP using full-mode defaults and workspace-aware execution.
 ---
-
 # Postman MCP Skill
 
 Use this skill when you need Postman workspace, collection, environment, or run operations through MCP.

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

@@ -1,9 +1,7 @@
 ---
 name: powershell-windows
 description: PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 ---
-
 # PowerShell Windows Patterns
 
 > Critical patterns and pitfalls for Windows PowerShell.

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

@@ -1,19 +1,18 @@
 ---
 name: "prompt-engineer"
-displayName: "Prompt Engineer"
 description: "Design and optimize LLM prompts with chain-of-thought, few-shot learning, and evaluation frameworks"
-keywords: ["prompt", "llm", "ai", "chain-of-thought", "few-shot", "evaluation", "gpt", "claude"]
 ---
-
 # Prompt Engineer
 
 ## When to Load Steering Files
 
-- Prompt patterns (zero-shot, few-shot, CoT) → `prompt-patterns.md`
-- Optimization techniques → `prompt-optimization.md`
-- Evaluation frameworks → `evaluation-frameworks.md`
-- Structured outputs (JSON, function calling) → `structured-outputs.md`
-- System prompt design → `system-prompts.md`
+| File | Load when |
+| --- | --- |
+| `references/prompt-patterns.md` | Choosing zero-shot, few-shot, chain-of-thought, or decomposition patterns. |
+| `references/prompt-optimization.md` | Iterating on failures, reducing ambiguity, or tightening prompts for latency/cost. |
+| `references/evaluation-frameworks.md` | Building prompt test cases, eval loops, or regression checks. |
+| `references/structured-outputs.md` | Designing JSON outputs, schema-constrained outputs, or tool/function calling prompts. |
+| `references/system-prompts.md` | Defining durable system prompts, role constraints, or behavioral guardrails. |
 
 ## Core Workflow
 

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

@@ -6,7 +6,6 @@ metadata:
   replaced_by: python-pro
   removal_target: v0.6.0
 ---
-
 # Python Patterns
 
 ## Compatibility Alias

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

@@ -9,7 +9,6 @@ metadata:
   stack: "python"
   baseline: "Python 3.14"
 ---
-
 # Python Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Migrating legacy Python to typed and testable architecture.
 - Implementing async I/O with predictable behavior.
 
+## When not to use
+
+- Frontend-only tasks with no Python runtime involved.
+- Database-only tuning or migration work with no Python code change.
+- Tiny shell-first automation where Python adds unnecessary packaging/runtime cost.
+
 ## Core workflow
 
 1. Establish interpreter/runtime constraints.
@@ -41,6 +46,18 @@ metadata:
 - Keep I/O async and CPU work isolated where needed.
 - Treat free-threaded mode as opt-in until dependencies are validated.
 
+## Debugging and observability
+
+- Preserve exception context and structured log fields at service boundaries.
+- Reproduce async bugs with deterministic fixtures before widening scope.
+- Use profiling and trace tooling before speculative concurrency changes.
+
+## Performance and reliability
+
+- Set timeout/retry budgets explicitly for external I/O.
+- Isolate CPU-heavy work from event loops or request handlers.
+- Keep dependency and packaging state reproducible with `pyproject.toml` tooling.
+
 ## Avoid
 
 - Untyped public APIs in shared modules.
@@ -49,8 +66,10 @@ metadata:
 
 ## Reference files
 
-- `references/type-system.md`
-- `references/async-patterns.md`
-- `references/testing.md`
-- `references/packaging.md`
-- `references/standard-library.md`
+| File | Load when |
+| --- | --- |
+| `references/type-system.md` | Typing strategy, protocols, generics, or boundary models need detail. |
+| `references/async-patterns.md` | Async I/O, task groups, or cancellation semantics need detail. |
+| `references/testing.md` | Pytest strategy, fixtures, or concurrency-safe tests are needed. |
+| `references/packaging.md` | Packaging, dependency layout, or toolchain reproducibility is in scope. |
+| `references/standard-library.md` | Standard-library-first options need review before adding dependencies. |

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/react-best-practices/SKILL.md

@@ -8,7 +8,6 @@ metadata:
   domain: "frontend"
   role: "review-checklist"
 ---
-
 # React Best Practices
 
 ## Purpose

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

@@ -9,7 +9,6 @@ metadata:
   stack: "react"
   baseline: "React 19"
 ---
-
 # React Expert
 
 ## Scope

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/react-expert/references/migration-class-to-modern.md

@@ -924,7 +924,7 @@ export default async function UserProfile({ params }: { params: { id: string } }
 - SEO-critical content? → Server Component
 - Large dependencies? → Server Component (smaller client bundle)
 
-See reference: `react-expert/references/server-components.md`
+See reference: [server-components.md](server-components.md)
 
 ---
 

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/red-team-tactics/SKILL.md

@@ -1,9 +1,7 @@
 ---
 name: red-team-tactics
 description: Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.
-allowed-tools: Read, Glob, Grep
 ---
-
 # Red Team Tactics
 
 > Adversary simulation principles based on MITRE ATT&CK framework.

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

@@ -1,10 +1,7 @@
 ---
 name: "refactor"
-displayName: "Refactor - OneUp HR"
 description: "Migrate legacy code to new architecture while maintaining behavior"
-keywords: ["refactor", "migrate", "clean", "improve", "legacy", "architecture"]
 ---
-
 # Refactor - OneUp HR
 
 ## Migration Patterns

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

@@ -1,20 +1,7 @@
 ---
 name: "riverpod-3"
-displayName: "Riverpod 3 Expert"
 description: "Riverpod 3 best practices for codegen, UI interaction boundaries, caching, paging, lifecycle, and testing"
-keywords:
-  [
-    "riverpod",
-    "riverpod 3",
-    "flutter",
-    "state management",
-    "asyncnotifier",
-    "codegen",
-    "keepalive",
-    "testing",
-  ]
 ---
-
 # Riverpod 3 Expert
 
 ## Overview
@@ -125,19 +112,25 @@ Avoid keepAlive for:
 
 ## Steering Files
 
-- `loop-avoidance.md` - Loop diagnostics and safe patterns
-- `minimal-rebuild.md` - `select`, widget splitting, item-level providers
-- `provider-layout.md` - Generic provider organization and boundaries
-- `refresh-cache-paging.md` - Refresh/paging/cache recipes
-- `testing.md` - ProviderContainer and widget test patterns
+| File | Load when |
+| --- | --- |
+| `references/loop-avoidance.md` | Diagnosing provider loops, invalidation storms, or notifier recursion. |
+| `references/minimal-rebuild.md` | Reducing rebuilds with `select`, widget splitting, or item-level providers. |
+| `references/provider-layout.md` | Organizing provider boundaries, layers, and ownership. |
+| `references/refresh-cache-paging.md` | Designing refresh, cache TTL, paging, or stale-while-revalidate flows. |
+| `references/testing.md` | Writing `ProviderContainer` or widget tests for Riverpod behavior. |
 
 ## Examples
 
-- `attendance_paging.md` - Complete paging example
-- `profile_edit.md` - Form workflow example
+| File | Load when |
+| --- | --- |
+| `examples/attendance_paging.md` | You need a concrete paginated list example. |
+| `examples/profile_edit.md` | You need a form/editing workflow example. |
 
 ## Templates
 
-- `cache_policy.dart` - TTL helper for repository cache policy
-- `paged_controller.dart` - Cursor/page-based infinite list controller
-- `riverpod_controller_test` - Provider/controller test template
+| File | Load when |
+| --- | --- |
+| `templates/cache_policy.dart.md` | Creating a TTL helper for repository caching. |
+| `templates/paged_controller.dart.md` | Bootstrapping a cursor/page-based controller. |
+| `templates/riverpod_controller_test.md` | Starting a provider/controller test template. |

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

@@ -6,7 +6,6 @@ metadata:
   replaced_by: rust-pro
   removal_target: v0.6.0
 ---
-
 # Rust Engineer
 
 ## Compatibility Alias

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

@@ -9,7 +9,6 @@ metadata:
   stack: "rust"
   baseline: "Rust stable 1.91"
 ---
-
 # Rust Pro
 
 ## When to use
@@ -18,6 +17,12 @@ metadata:
 - Solving ownership/lifetime design problems.
 - Optimizing memory safety and runtime performance together.
 
+## When not to use
+
+- Browser/frontend-only work with no Rust component.
+- Database-only tuning without Rust service or library changes.
+- Small scripts where shell or existing project tooling is the intended path.
+
 ## Core workflow
 
 1. Define ownership and error model first.
@@ -42,6 +47,24 @@ metadata:
 - Keep borrow scopes tight to improve readability and compile times.
 - Separate transport DTOs from domain types.
 
+## Debugging and observability
+
+- Prefer reproducible failing tests and `tracing` instrumentation before redesigning ownership or async structure.
+- Make task cancellation, retries, and error chains visible in logs/telemetry.
+- Use `cargo test`, `clippy`, and targeted benchmarks to isolate regressions.
+
+## Performance and reliability
+
+- Keep async flows cancellation-safe and backpressure-aware.
+- Measure allocations, lock contention, and tail latency before unsafe or low-level tuning.
+- Bound work queues and connection pools explicitly.
+
+## References
+
+| File | Load when |
+| --- | --- |
+| `references/operational-baseline.md` | You need service-level guardrails for async, errors, tracing, and test discipline. |
+
 ## Avoid
 
 - Premature `unsafe` optimization.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/rust-pro/references/operational-baseline.md

@@ -0,0 +1,9 @@
+## Operational baseline
+
+Load when: async service safety, tracing, error handling, or release guardrails need explicit guidance.
+
+- Keep error chains actionable and visible in logs/traces.
+- Use `cargo fmt`, `clippy`, and focused tests as a release baseline.
+- Make cancellation, queue bounds, and backpressure explicit.
+- Treat `unsafe` as an exception with documented invariants.
+- Profile before low-level optimization.

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

@@ -2,7 +2,6 @@
 name: "saas-builder"
 description: "Build or review production-ready multi-tenant SaaS systems on AWS serverless architecture with React + TypeScript frontend, tenant-isolated DynamoDB data models, JWT/RBAC authorization, Stripe subscriptions, and usage-based billing. Use for SaaS architecture design, implementation planning, API/Lambda patterns, billing workflows, and tenant isolation audits."
 ---
-
 # SaaS Builder
 
 Implement multi-tenant SaaS systems with serverless-first architecture, strict tenant isolation, and billing-grade data handling.

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

@@ -1,13 +1,7 @@
 ---
 name: sarif-parsing
 description: Parse, analyze, and process SARIF (Static Analysis Results Interchange Format) files. Use when reading security scan results, aggregating findings from multiple tools, deduplicating alerts, extracting specific vulnerabilities, or integrating SARIF data into CI/CD pipelines.
-allowed-tools:
-  - Bash
-  - Read
-  - Glob
-  - Grep
 ---
-
 # SARIF Parsing Best Practices
 
 You are a SARIF parsing expert. Your role is to help users effectively read, analyze, and process SARIF files from static analysis tools.

package/workflows/workflows/agent-environment-setup/platforms/copilot/skills/secure-code-guardian/SKILL.md

@@ -12,7 +12,6 @@ metadata:
   output-format: code
   related-skills: fullstack-guardian, security-reviewer, architecture-designer
 ---
-
 # Secure Code Guardian
 
 Security-focused developer specializing in writing secure code and preventing vulnerabilities.