opencode-skills-collection 4.1.15 → 4.1.17

package/bundled-skills/multi-cloud-architecture/SKILL.md

@@ -5,6 +5,9 @@ risk: safe
 source: community
 date_added: "2026-02-27"
 ---
+## 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.
 
 # Multi-Cloud Architecture
 
@@ -20,7 +23,6 @@ Decision framework and patterns for architecting applications across AWS, Azure,
 - 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`.
 
 ## Purpose
 

package/bundled-skills/multi-cloud-architecture/UPSTREAM-LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Seth Hobson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/bundled-skills/multi-cloud-architecture/UPSTREAM-NOTICE.md

@@ -0,0 +1,12 @@
+# Upstream helpers for multi-cloud-architecture
+
+The files listed below were recovered from [wshobson/agents](https://github.com/wshobson/agents) at commit `46891e7e60da0e52baf1050b7b6391b64e84c6d9`. The repository ID is `1025856648`.
+
+They retain the upstream **MIT** license reproduced in [UPSTREAM-LICENSE.txt](UPSTREAM-LICENSE.txt). This notice applies to the listed support files; it does not replace the license metadata of other catalog files. Preserve the upstream license and this attribution when redistributing them.
+
+License wording is unchanged; text-only trailing whitespace and EOF blank lines are normalized. Original license: https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE
+
+| Local file | Original upstream path | Original Git blob SHA | Import changes |
+| --- | --- | --- | --- |
+| `references/service-comparison.md` | `plugins/cloud-infrastructure/skills/multi-cloud-architecture/references/service-comparison.md` | `2843cb976a8ff953001bad53ef8f508ee5c7e6a3` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/multi-cloud-patterns.md` | `plugins/cloud-infrastructure/skills/multi-cloud-architecture/references/multi-cloud-patterns.md` | `34c696be23adc0b38451bd509547637dddabe9ff` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/multi-cloud-architecture/references/multi-cloud-patterns.md

@@ -0,0 +1,26 @@
+# Multi-Cloud Architecture Patterns
+
+## Active-Active Regional Split
+
+- Run customer-facing services in two providers for resiliency
+- Use global DNS and traffic steering to shift load during incidents
+- Keep shared data replicated asynchronously unless low-latency writes are mandatory
+
+## Best-of-Breed Service Mix
+
+- Analytics and ML on GCP
+- Enterprise identity and Microsoft workloads on Azure
+- Broad ecosystem integrations on AWS
+- Oracle-centric databases and regulated transaction systems on OCI
+
+## Primary / DR Pairing
+
+- Keep primary infrastructure in the provider closest to operational expertise
+- Use a second provider for cold or warm disaster recovery
+- Validate RPO/RTO assumptions with regular failover exercises
+
+## Portable Platform Baseline
+
+- Standardize on Kubernetes, Terraform/OpenTofu, PostgreSQL, Redis, and OpenTelemetry
+- Abstract cloud differences behind modules, golden paths, and service catalogs
+- Document provider-specific exceptions such as IAM, networking, and managed database behavior

package/bundled-skills/multi-cloud-architecture/references/service-comparison.md

@@ -0,0 +1,35 @@
+# Multi-Cloud Service Comparison
+
+## Compute
+
+| Use Case | AWS | Azure | GCP | OCI |
+| -------- | --- | ----- | --- | --- |
+| General-purpose VMs | EC2 | Virtual Machines | Compute Engine | Compute |
+| Managed Kubernetes | EKS | AKS | GKE | OKE |
+| Serverless functions | Lambda | Functions | Cloud Functions | Functions |
+| Containers without cluster management | ECS/Fargate | Container Apps / Container Instances | Cloud Run | Container Instances |
+
+## Storage
+
+| Use Case | AWS | Azure | GCP | OCI |
+| -------- | --- | ----- | --- | --- |
+| Object storage | S3 | Blob Storage | Cloud Storage | Object Storage |
+| Block storage | EBS | Managed Disks | Persistent Disk | Block Volumes |
+| File storage | EFS | Azure Files | Filestore | File Storage |
+| Archive storage | Glacier / Deep Archive | Archive Storage | Archive Storage | Archive Storage |
+
+## Data Services
+
+| Use Case | AWS | Azure | GCP | OCI |
+| -------- | --- | ----- | --- | --- |
+| Managed relational database | RDS | SQL Database | Cloud SQL | MySQL HeatWave |
+| Distributed / globally resilient SQL | Aurora Global Database | Cosmos DB for PostgreSQL / SQL patterns | Cloud Spanner | Autonomous Database |
+| NoSQL | DynamoDB | Cosmos DB | Firestore | NoSQL Database |
+| Streaming | Kinesis / MSK | Event Hubs | Pub/Sub / Confluent | Streaming |
+
+## Platform Selection Notes
+
+1. Prefer provider-native managed services when team expertise and lock-in tolerance are high.
+2. Prefer Kubernetes, PostgreSQL, Redis, and open observability stacks when portability matters.
+3. Use OCI when Oracle database affinity, predictable networking, or regulated workload isolation are primary drivers.
+4. Compare egress, managed service premiums, and support plans before splitting workloads across providers.

package/bundled-skills/nanobanana-ppt-skills/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: nanobanana-ppt-skills
 description: "AI-powered PPT generation with document analysis and styled images"
-risk: safe
+risk: critical
 source: "https://github.com/op7418/NanoBanana-PPT-Skills"
 date_added: "2026-02-27"
 ---
@@ -16,11 +16,20 @@ AI-powered PPT generation with document analysis and styled images
 
 Use this skill when you need to work with ai-powered ppt generation with document analysis and styled images.
 
-## Instructions
+## Procedure
 
-This skill provides guidance and patterns for ai-powered ppt generation with document analysis and styled images.
+Resolve audience, purpose, slide count, language, supplied sources, brand and output
+format. Build an evidence-linked outline before generating visual assets; do not
+invent business data, citations or image licensing. This entrypoint does not bundle
+the upstream generator, image model access or a slide-export runtime. Inspect a
+reviewed actual installation before using its commands, and authorize private-file
+uploads and paid generation explicitly.
 
-For more information, see the [source repository](https://github.com/op7418/NanoBanana-PPT-Skills).
+Create one representative slide before a large run. Preserve editable text when
+required; a set of slide images is not automatically an editable PPTX. Inspect all
+rendered slides for clipping, text legibility, aspect ratio and factual consistency.
+Deliver actual generated files, report export format and missing checks, and retain
+source materials and originals. No external publication is implied.
 
 ## Example
 

package/bundled-skills/native-data-fetching/references/detailed-guide.md

@@ -12,11 +12,17 @@ references/
 ```
 
 
+The snippets are separate integration examples: supply application types/components, React/Expo imports, verified API origins, schema parsers and an actual refresh adapter. A generic TypeScript return type does not validate JSON. Scope query keys to the authenticated tenant/user and clear private cached/persisted data on logout or identity changes. SecureStore requires a supported native platform; web needs a separately reviewed session strategy. Persistence does not make mutations a durable offline queue.
+
 ## Preferences
 
 - Avoid axios, prefer expo/fetch
 
 
+## Loading, empty, failure and saved content
+
+Restore the separate screen states from the current [upstream fetching skill](https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-data-fetching/SKILL.md): treat absent data separately from a resolved empty response, retain saved content during a failed refresh, and preserve an unsaved form after failed submission. Hydrate identity before private requests. These are application responsibilities, not states supplied by this guide.
+
 ## Common Issues & Solutions
 
 ### 1. Basic Fetch Usage
@@ -24,8 +30,8 @@ references/
 **Simple GET request**:
 
 ```tsx
-const fetchUser = async (userId: string) => {
-  const response = await fetch(`https://api.example.com/users/${userId}`);
+const fetchUser = async (userId: string, signal?: AbortSignal) => {
+  const response = await fetch(`https://api.example.com/users/${encodeURIComponent(userId)}`, { signal });
 
   if (!response.ok) {
     throw new Error(`HTTP error! status: ${response.status}`);
@@ -91,15 +97,20 @@ export default function RootLayout() {
 import { useQuery } from "@tanstack/react-query";
 
 function UserProfile({ userId }: { userId: string }) {
-  const { data, isLoading, error, refetch } = useQuery({
+  const { data, fetchStatus, error, refetch } = useQuery({
     queryKey: ["user", userId],
-    queryFn: () => fetchUser(userId),
+    queryFn: ({ signal }) => fetchUser(userId, signal),
   });
 
-  if (isLoading) return <Loading />;
-  if (error) return <Error message={error.message} />;
-
-  return <Profile user={data} />;
+  if (data === undefined) {
+    if (error) return <ErrorState onRetry={refetch} />;
+    if (fetchStatus === "paused") return <OfflineState />;
+    return <Loading />;
+  }
+  return <>
+    {error && <RefreshWarning onRetry={refetch} />}
+    {data === null ? <EmptyState /> : <Profile user={data} />}
+  </>;
 }
 ```
 
@@ -120,10 +131,10 @@ function CreateUserForm() {
   });
 
   const handleSubmit = (data: UserData) => {
-    mutation.mutate(data);
+    if (!mutation.isPending) mutation.mutate(data);
   };
 
-  return <Form onSubmit={handleSubmit} isLoading={mutation.isPending} />;
+  return <Form onSubmit={handleSubmit} isLoading={mutation.isPending} error={mutation.error} />;
 }
 ```
 
@@ -159,7 +170,8 @@ const fetchWithErrorHandling = async (url: string, options?: RequestInit) => {
     if (error instanceof ApiError) {
       throw error;
     }
-    // Network error (no internet, timeout, etc.)
+    if (options?.signal?.aborted || !(error instanceof TypeError)) throw error;
+    // Fetch rejects network failures with TypeError; do not classify JSON parse errors as retryable.
     throw new ApiError("Network error", 0, "NETWORK_ERROR");
   }
 };
@@ -173,11 +185,17 @@ const fetchWithRetry = async (
   options?: RequestInit,
   retries = 3
 ) => {
+  if (!Number.isInteger(retries) || retries < 1 || retries > 5) throw new Error("Invalid attempt limit");
   for (let i = 0; i < retries; i++) {
+    options?.signal?.throwIfAborted();
     try {
       return await fetchWithErrorHandling(url, options);
     } catch (error) {
-      if (i === retries - 1) throw error;
+      const method = (options?.method ?? "GET").toUpperCase();
+      const status = error instanceof ApiError ? error.status : -1;
+      const transient = status === 0 || status === 408 || status >= 500;
+      if (!["GET", "HEAD"].includes(method) || !transient ||
+          options?.signal?.aborted || i === retries - 1) throw error;
       // Exponential backoff
       await new Promise((r) => setTimeout(r, Math.pow(2, i) * 1000));
     }
@@ -206,13 +224,14 @@ export const auth = {
 const authFetch = async (url: string, options: RequestInit = {}) => {
   const token = await auth.getToken();
 
-  return fetch(url, {
-    ...options,
-    headers: {
-      ...options.headers,
-      Authorization: token ? `Bearer ${token}` : "",
-    },
-  });
+  const target = new URL(url);
+  if (target.origin !== "https://api.example.com" || target.username || target.password) {
+    throw new Error("Untrusted authenticated API destination");
+  }
+  const headers = new Headers(options.headers);
+  if (!token) throw new Error("Authentication required");
+  headers.set("Authorization", `Bearer ${token}`);
+  return fetch(target, { ...options, headers, redirect: "error" });
 };
 ```
 
@@ -376,9 +395,9 @@ useEffect(() => {
 
   fetch(url, { signal: controller.signal })
     .then((response) => response.json())
-    .then(setData)
+    .then((data) => { if (!controller.signal.aborted) setData(data); })
     .catch((error) => {
-      if (error.name !== "AbortError") {
+      if (!controller.signal.aborted && error.name !== "AbortError") {
         setError(error);
       }
     });
@@ -390,8 +409,8 @@ useEffect(() => {
 **With React Query** (automatic):
 
 ```tsx
-// React Query automatically cancels requests when queries are invalidated
-// or components unmount
+// Pass the query function signal to fetch; unmount/invalidation alone
+// does not guarantee cancellation of the underlying network operation.
 ```
 
 ---

package/bundled-skills/native-data-fetching/references/expo-router-loaders.md

@@ -9,6 +9,10 @@ Route-level data loading for web apps using Expo SDK 55+. Loaders are async func
 
 You write one function and the framework manages when and how it executes.
 
+## Version boundary
+
+Bind these examples to the installed SDK. The [official loader guide](https://docs.expo.dev/router/web/data-loaders/) distinguishes stable SDK 58+ from experimental SDK 55–57: enable the unstable loader flag only on those earlier versions. Current typed loader imports come from `expo-router/server`. Check rendering configuration and cache behavior for that exact SDK. The historical configurations below illustrate SDK 55–57 and must not be copied unchanged into every newer project.
+
 ## Configuration
 
 **Requirements:** Expo SDK 55+, web output mode (`npx expo serve` or `npx expo export --platform web`) set in `app.json` or `app.config.js`.
@@ -61,7 +65,7 @@ You write one function and the framework manages when and how it executes.
 Loaders use two packages:
 
 - **`expo-router`** — `useLoaderData` hook
-- **`expo-server`** — `LoaderFunction` type, `StatusError`, `setResponseHeaders`. Always available (dependency of `expo-router`), no install needed.
+- **`expo-router/server`** — current `LoaderFunction` type; **`expo-server`** — runtime utilities such as `StatusError` and `setResponseHeaders`. Verify installed exports.
 
 ## Basic Loader
 
@@ -75,6 +79,7 @@ import { ActivityIndicator, View, Text } from "react-native";
 
 export async function loader() {
   const response = await fetch("https://api.example.com/posts");
+  if (!response.ok) throw new Error("Posts unavailable");
   const posts = await response.json();
   return { posts };
 }
@@ -110,7 +115,8 @@ For loaders with params, use the `LoaderFunction<T>` type from `expo-server`. Th
 // app/posts/[id].tsx
 import { Suspense } from "react";
 import { useLoaderData } from "expo-router";
-import { StatusError, type LoaderFunction } from "expo-server";
+import { StatusError } from "expo-server";
+import { type LoaderFunction } from "expo-router/server";
 import { ActivityIndicator, View, Text } from "react-native";
 
 type Post = {
@@ -123,8 +129,9 @@ export const loader: LoaderFunction<{ post: Post }> = async (
   request,
   params,
 ) => {
-  const id = params.id as string;
-  const response = await fetch(`https://api.example.com/posts/${id}`);
+  if (typeof params.id !== "string" || !params.id) throw new Error("Invalid ID");
+  const id = params.id;
+  const response = await fetch(`https://api.example.com/posts/${encodeURIComponent(id)}`);
 
   if (!response.ok) {
     throw new StatusError(404, `Post ${id} not found`);
@@ -158,7 +165,7 @@ Catch-all routes access `params.slug` the same way:
 
 ```tsx
 // app/docs/[...slug].tsx
-import { type LoaderFunction } from "expo-server";
+import { type LoaderFunction } from "expo-router/server";
 
 type Doc = { title: string; content: string };
 
@@ -174,7 +181,7 @@ Query parameters are available via the `request` object (server output mode only
 
 ```tsx
 // app/search.tsx
-import { type LoaderFunction } from "expo-server";
+import { type LoaderFunction } from "expo-router/server";
 
 export const loader: LoaderFunction<{ results: any[]; query: string }> = async (request) => {
   // Assuming request.url is `/search?q=expo&page=2`
@@ -191,27 +198,24 @@ export const loader: LoaderFunction<{ results: any[]; query: string }> = async (
 
 Loaders run on the server, so you can access secrets and server-only resources directly:
 
-```tsx
-// app/dashboard.tsx
-import { type LoaderFunction } from "expo-server";
-
-export const loader: LoaderFunction<{ balance: any; isAuthenticated: boolean }> = async (
-  request,
-  params,
-) => {
-  const data = await fetch("https://api.stripe.com/v1/balance", {
-    headers: {
-      Authorization: `Bearer ${process.env.STRIPE_SECRET_KEY}`,
-    },
-  });
-
-  const sessionToken = request?.headers.get("cookie")?.match(/session=([^;]+)/)?.[1];
-
-  const balance = await data.json();
-  return { balance, isAuthenticated: !!sessionToken };
-};
+The following JavaScript is a dependency-injected server handler, not a claim about an installed Expo SDK signature. Wire it into the verified version's loader API. `verifySession` must verify expiry, revocation and identity server-side; cookie presence is insufficient. `authorizeAccount` must bind that identity to the requested account. These project functions are prerequisites, not bundled implementations.
+
+```javascript
+export async function loadPrivateBalance(request, {
+  verifySession, authorizeAccount, fetchBalance,
+}) {
+  if (!request) throw new Error("Server request required");
+  const session = await verifySession(request);
+  if (!session) throw new Error("Unauthenticated");
+  const account = await authorizeAccount(session);
+  if (!account) throw new Error("Forbidden");
+  const balance = await fetchBalance(account);
+  return { balance }; // Return only fields this user may view.
+}
 ```
 
+Disable shared caching (`Cache-Control: private, no-store`), protect client caches by identity and clear them on sign-out. Never prerender private account data into static HTML. Verify loader APIs and caching behavior against the installed version and [official data-loader documentation](https://docs.expo.dev/router/web/data-loaders/).
+
 The `request` object is available in server output mode. In static output mode, `request` is always `undefined`.
 
 ## Response Utilities
@@ -236,10 +240,12 @@ export async function loader() {
 
 ```tsx
 // app/products/[id].tsx
-import { StatusError, type LoaderFunction } from "expo-server";
+import { StatusError } from "expo-server";
+import { type LoaderFunction } from "expo-router/server";
 
 export const loader: LoaderFunction<{ product: Product }> = async (request, params) => {
-  const id = params.id as string;
+  if (typeof params.id !== "string" || !params.id) throw new Error("Invalid ID");
+  const id = params.id;
   const product = await fetchProduct(id);
 
   if (!product) {
@@ -264,6 +270,7 @@ import { ActivityIndicator, View, Text } from "react-native";
 
 export async function loader() {
   const response = await fetch("https://api.example.com/posts");
+  if (!response.ok) throw new Error("Posts unavailable");
   return { posts: await response.json() };
 }
 
@@ -329,7 +336,7 @@ When a loader throws (including `StatusError`), the nearest `ErrorBoundary` catc
 
 - Loaders are web-only; use client-side fetching (React Query, fetch) for native
 - Loaders cannot be used in `_layout` files — only in route files
-- Use `LoaderFunction<T>` from `expo-server` to type loaders that use params
+- Use the installed SDK’s `LoaderFunction<T>` (currently `expo-router/server`) to type loaders that use params
 - The request object is immutable — use optional chaining (`request?.headers`) as it may be `undefined` in static mode
 - Return only JSON-serializable values (no `Date`, `Map`, `Set`, class instances, functions)
 - Use non-prefixed `process.env` vars for secrets in loaders, not `EXPO_PUBLIC_` (which is embedded in the client bundle)
@@ -338,4 +345,4 @@ When a loader throws (including `StatusError`), the nearest `ErrorBoundary` catc
 - Export `ErrorBoundary` from route files to handle loader failures gracefully
 - Validate and sanitize user input (params, query strings) before using in database queries or API calls
 - Handle errors gracefully with try/catch; log server-side for debugging
-- Loader data is currently cached for the session. This is a known limitation that will be lifted in a future release
+- SDK 55–57 retain client loader data during navigation. SDK 58+ re-fetches after route unmount/revisit under HTTP cache rules; mounted-route invalidation still needs an explicit design. Verify identity changes and error retries on the installed version.

package/bundled-skills/nerdzao-elite/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: nerdzao-elite
-description: "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation."
+description: "Software engineering and product design workflow and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation."
 risk: safe
 source: community
 date_added: "2026-02-27"
@@ -8,13 +8,13 @@ date_added: "2026-02-27"
 
 # @nerdzao-elite
 
-Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior.
+Você é um Engenheiro de Software cuidadoso + Designer de Produto Senior.
 
-Ative automaticamente TODAS as skills abaixo em toda tarefa:
+Selecione apenas as skills pertinentes à tarefa autorizada:
 
 @concise-planning @brainstorming @senior-architect @architecture @test-driven-development @testing-patterns @refactor-clean-code @clean-code @lint-and-validate @ui-visual-validator @ui-ux-pro-max @frontend-design @web-design-guidelines @production-code-audit @code-reviewer @systematic-debugging @error-handling-patterns @kaizen @verification-before-completion
 
-Workflow obrigatório (sempre na ordem):
+Workflow proporcional ao escopo e às regras atuais do repositório:
 
 1. Planejamento (@concise-planning + @brainstorming)
 2. Arquitetura sólida
@@ -34,9 +34,13 @@ Use when you need a full senior engineering workflow with planning, architecture
 
 **User request:**
 
-> Use @nerdzao-elite for this task: Senior Elite Software Engineer (15+) and Senior Product Designer.
+> Use @nerdzao-elite for this task: Software engineering and product design workflow and Senior Product Designer.
 
 ## 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.
+
+## Limites operacionais
+
+O nome histórico não seleciona um modelo nem autoriza subagentes, chamadas pagas, publicação ou mudanças globais. Reuse o plano/contexto existente, confirme que cada skill indicada está instalada e preserve os limites de aprovação e a cadência de trabalho do usuário. Qualidade visual e produção precisam de testes observados; não são garantidas por uma persona.

package/bundled-skills/nerdzao-elite-gemini-high/SKILL.md

@@ -8,9 +8,9 @@ date_added: "2026-02-27"
 
 # @nerdzao-elite-gemini-high
 
-Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior, operando no modo Gemini 3.1 Pro (High).
+Você é um Engenheiro de Software cuidadoso + Designer de Produto Senior, seguindo o modelo e as ferramentas realmente configurados no host.
 
-Ative automaticamente este workflow completo em TODA tarefa:
+Use as fases pertinentes ao escopo solicitado; não execute todas automaticamente:
 
 1. **Planejamento ultra-rápido**  
    @concise-planning + @brainstorming
@@ -38,7 +38,7 @@ Ative automaticamente este workflow completo em TODA tarefa:
 
 **Regras específicas para Gemini 3.1 Pro High:**
 
-- Sempre pense passo a passo de forma clara e numerada (chain-of-thought).
+- Apresente evidências e uma justificativa breve; não peça nem exponha raciocínio interno oculto.
 - Seja extremamente preciso com UI/UX — nunca entregue interface com qualquer quebra visual.
 - Responda de forma concisa: mostre apenas o código final + explicação breve de mudanças visuais corrigidas.
 - Nunca adicione comentários ou texto longo desnecessário.
@@ -59,3 +59,7 @@ Use when you need maximum quality output with Gemini 3.1 Pro High, pixel-perfect
 - 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.
+
+## Limites operacionais
+
+O nome histórico não seleciona um modelo nem autoriza subagentes, chamadas pagas, publicação ou mudanças globais. Reuse o plano/contexto existente, confirme que cada skill indicada está instalada e preserve os limites de aprovação e a cadência de trabalho do usuário. Qualidade visual e produção precisam de testes observados; não são garantidas por uma persona.

package/bundled-skills/network-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 a network engineer specializing in modern cloud networking, security, and performance optimization.
 

package/bundled-skills/networkx/SKILL.md

@@ -8,6 +8,9 @@ risk: critical
 source: "https://github.com/networkx/networkx"
 date_added: "2026-09-04"
 ---
+## 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.
 
 # NetworkX
 

package/bundled-skills/networkx/UPSTREAM-LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 K-Dense Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/bundled-skills/networkx/UPSTREAM-NOTICE.md

@@ -0,0 +1,15 @@
+# Upstream helpers for networkx
+
+The files listed below were recovered from [K-Dense-AI/scientific-agent-skills](https://github.com/K-Dense-AI/scientific-agent-skills) at commit `0481567238838a6598f2ffcf720fa120ed644cb5`. The repository ID is `1079456184`.
+
+They retain the upstream **MIT** license reproduced in [UPSTREAM-LICENSE.txt](UPSTREAM-LICENSE.txt). This notice applies to the listed support files; it does not replace the license metadata of other catalog files. Preserve the upstream license and this attribution when redistributing them.
+
+License wording is unchanged; text-only trailing whitespace and EOF blank lines are normalized. Original license: https://github.com/K-Dense-AI/scientific-agent-skills/blob/0481567238838a6598f2ffcf720fa120ed644cb5/LICENSE.md
+
+| Local file | Original upstream path | Original Git blob SHA | Import changes |
+| --- | --- | --- | --- |
+| `references/graph-basics.md` | `skills/networkx/references/graph-basics.md` | `05d7de3752584bb37fc584ec3413a1546c8436ed` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/algorithms.md` | `skills/networkx/references/algorithms.md` | `9ad94243facce7f5037fb98ecdd4ae6966985fdd` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/generators.md` | `skills/networkx/references/generators.md` | `0f92b2b43c3323d2447b97ea5b00ef298c446281` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/io.md` | `skills/networkx/references/io.md` | `b12aee621a577e21c6c5a8521b871e30794bfd49` | text-only trailing whitespace and EOF blank lines normalized |
+| `references/visualization.md` | `skills/networkx/references/visualization.md` | `caf9b7a3fc55adee546bd9ec57f56a840115693c` | text-only trailing whitespace and EOF blank lines normalized |