opencode-skills-collection 4.1.14 → 4.1.16

package/bundled-skills/cost-optimization/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/cost-optimization/UPSTREAM-NOTICE.md

@@ -0,0 +1,11 @@
+# Upstream helpers for cost-optimization
+
+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/tagging-standards.md` | `plugins/cloud-infrastructure/skills/cost-optimization/references/tagging-standards.md` | `7f8965297049678434db181affb20f1505ff904f` | text-only trailing whitespace and EOF blank lines normalized |

package/bundled-skills/cost-optimization/references/tagging-standards.md

@@ -0,0 +1,23 @@
+# Cloud Tagging Standards
+
+## Required Tags
+
+- `Environment`: dev, staging, production
+- `Owner`: team or individual responsible for the workload
+- `CostCenter`: finance or reporting identifier
+- `Project`: product or initiative name
+- `ManagedBy`: terraform, opentofu, pulumi, or manual
+
+## Provider Notes
+
+- AWS: standardize tags for Cost Explorer, CUR, and automation policies
+- Azure: align tags with management groups, subscriptions, and Azure Policy
+- GCP: combine labels and resource hierarchy for billing attribution
+- OCI: apply defined tags at the compartment and resource level for chargeback
+
+## Best Practices
+
+1. Publish an approved tag dictionary and naming rules.
+2. Enforce tags with policy and CI validation.
+3. Inherit tags from shared modules whenever possible.
+4. Audit for missing or inconsistent tags weekly.

package/bundled-skills/cowork-to-code-bridge/SKILL.md

@@ -9,6 +9,15 @@ license: MIT
 license_source: https://github.com/abhinaykrupa/cowork-to-code-bridge/blob/97f515d425df587c281effb02cda9ad0fd470790/LICENSE
 date_added: "2026-07-30"
 ---
+## 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>/scripts/git_status.sh`
+- `<support-root>/scripts/run_claude.sh`
+
+Obtain the required material from the [declared upstream source](https://github.com/abhinaykrupa/cowork-to-code-bridge), or from a user-provided installation of that source. 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.
+
 
 # cowork-to-code-bridge
 

package/bundled-skills/create-issue-gate/SKILL.md

@@ -10,9 +10,9 @@ date_added: "2026-03-12"
 
 ## Overview
 
-Create GitHub issues as the single tracking entrypoint for tasks, with a hard gate on acceptance criteria.
+Use this issue-gating workflow only when the user or current project explicitly requires it. It is not a universal prerequisite for implementation or permission to create public issues.
 
-Core rule: **no explicit, testable acceptance criteria from user => issue stays `draft` and execution is blocked.**
+Core rule: **within an explicitly required issue gate, dependent execution requires valid acceptance criteria.** Derive them from available authorized task context when possible; only indispensable unresolved decisions need clarification.
 
 ## When to Use
 - You are starting a new implementation task and want a GitHub issue to be the required tracking entrypoint.
@@ -39,14 +39,14 @@ Examples:
 - invalid: "fix checkout" / "improve UX" / "make it better"
 
 If criteria are missing or non-testable:
-- still create the issue
+- prepare a reviewable draft; create a public issue only when that repository action is authorized
 - set `Status: draft`
 - add `Execution Gate: blocked (missing valid acceptance criteria)`
 - do not move task to execution
 
 ## Issue Creation Mode
 
-Default mode is direct GitHub creation using `gh issue create`.
+Default to preparing the exact issue body for review. If issue creation is authorized, use the named repository and existing template; a skill invocation does not grant permission to post to an unrelated repository.
 
 Use a body template like:
 
@@ -91,7 +91,7 @@ Execution workflows (for example `closed-loop-delivery`) may start only when:
 - issue status is `ready`
 - execution gate is `allowed`
 
-If issue is `draft`, stop and request user-provided acceptance criteria.
+If an applicable required issue remains draft due to an indispensable missing decision, pause that dependent step and continue independent safe work. Do not ask again for criteria already clear in the user’s request.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/bundled-skills/create-pr/SKILL.md

@@ -17,6 +17,8 @@ This skill name is kept for compatibility.
 
 Use the available `pr-writer` skill as the canonical workflow for creating and editing pull requests. If the client requires qualified skill names, use the qualifier for the plugin that supplied this skill rather than assuming an external namespace.
 
+Confirm that `pr-writer` is actually installed; otherwise report the dependency missing. Repository-native maintainer and merge rules still apply.
+
 If invoked via `create-pr`, run the same workflow and conventions documented in `pr-writer`.
 
 ## Example

package/bundled-skills/crossframe-suite/SKILL.md

@@ -21,6 +21,14 @@ tags:
   - multi-skill
   - structural-diagnosis
 ---
+## 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:
+
+- `crossframe-essay/templates/article-type-selection-dialog.md`
+
+Obtain the required material from the [declared upstream source](https://github.com/xi-kari/crossframe-skill), or from a user-provided installation of that source. 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.
+
 # CrossFrame Suite
 
 

package/bundled-skills/crypto-bd-agent/SKILL.md

@@ -1,9 +1,8 @@
 ---
 name: crypto-bd-agent
-description: "Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges."
+description: "Production-tested patterns for building AI agents that autonomously discover, evaluate, and acquire token listings for cryptocurrency exchanges."
 risk: safe
 source: community
-tags: null
 date_added: '2026-02-27'
 ---
 

package/bundled-skills/csharp-pro/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: csharp-pro
-description: Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing.
+description: Write modern C# code with advanced features like records, pattern matching, and async/await. Use for version-compatible .NET implementation and evidence-based testing/performance review.
 risk: critical
 source: community
 date_added: '2026-02-27'
@@ -8,8 +8,7 @@ date_added: '2026-02-27'
 
 ## Use this skill when
 
-- Working on csharp pro tasks or workflows
-- Needing guidance, best practices, or checklists for csharp pro
+Implement or review C#/.NET application code, async workflows, nullable contracts, performance-sensitive allocation or testable ASP.NET/EF boundaries.
 
 ## Do not use this skill when
 
@@ -18,10 +17,9 @@ date_added: '2026-02-27'
 
 ## Instructions
 
-- Clarify goals, constraints, and required inputs.
+- Read actual project/runtime versions, current instructions and existing code before choosing changes; clarify only indispensable unknowns.
 - 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 C# expert specializing in modern .NET development and enterprise-grade applications.
 
@@ -37,7 +35,7 @@ You are a C# expert specializing in modern .NET development and enterprise-grade
 
 ## Approach
 
-1. Leverage modern C# features for clean, expressive code
+1. Use only language/runtime features supported by the actual project; distinguish a proposed optimization from a measured BenchmarkDotNet result
 2. Follow SOLID principles and favor composition over inheritance
 3. Use nullable reference types and comprehensive error handling
 4. Optimize for performance with span, memory, and value types
@@ -63,6 +61,6 @@ Follow .NET coding standards and include comprehensive XML documentation.
 > Review this C# implementation for correctness, idiomatic design, performance, and test coverage.
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
+- This single-file guide is the available local procedure; no external reference pack or implementation-playbook is bundled or required. Keep existing framework/version constraints and report real verification separately from proposed code.
 - 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.

package/bundled-skills/csv-manual-export/SKILL.md

@@ -11,7 +11,6 @@ tags: [csv, export, import, template, operations, data, helper]
 tools: []
 source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
 ---
-
 # CSV Manual Export
 
 **What it is:** a clean, empty CSV of a field list someone already confirmed - the
@@ -199,7 +198,7 @@ that module already confirmed. Read that section - field names, types, order,
 requiredness, options and calculations - and render exactly that. The list below is
 every module that owns a field list, grouped by the layer its catalog gives it, and it
 is generated from those catalogs and the module files, so it cannot name a module that
-does not exist. `references/catalog.md` is the index to show a user; the module's own
+does not exist. `<support-root>/references/catalog.md` is an external collection index, not bundled here; locate and inspect it before depending on it. Do not claim an unavailable lookup succeeded; the module's own
 `SKILL.md` holds the field list.
 
 **Layer 1: Foundation** - 6 modules

package/bundled-skills/customer-psychographic-profiler/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: customer-psychographic-profiler
-description: "One sentence - what this skill does and when to invoke it"
+description: "Build an evidence-grounded customer profile of motivations, fears, identity, and trust barriers before positioning, copywriting, or funnel design."
 risk: safe
 source: community
 date_added: "2026-04-04"
 ---
-You are a **Consumer Psychologist**. Your task is to build a deep psychological profile of a target customer including desires, fears, identity, worldview, and emotional drivers. You do not produce generic audience summaries. You infer the psychological structure that downstream skills will use as their foundation.
+Use a marketing planning and audience-research lens. Your task is to build a deep psychological profile of a target customer including desires, fears, identity, worldview, and emotional drivers. You do not produce generic audience summaries. You infer the psychological structure that downstream skills will use as their foundation.
 
 Before producing any output, complete the diagnostic protocol below. Then apply the framework. Then produce the profile.
 
@@ -13,6 +13,12 @@ Before producing any output, complete the diagnostic protocol below. Then apply
 - Use when you need a deep psychographic profile before positioning, copy, or funnel design.
 - Use when demographics are not enough and you need motivations, anxieties, and identity cues.
 
+## Evidence and scope
+
+Use observed audience research and verified product facts. Psychological interpretations and the author-year references below are inherited conceptual context, not validated evidence for this exact workflow or a guaranteed conversion effect. Before using a scientific claim externally, verify the actual publication, method and applicability; omit unsupported claims. This is marketing planning, not clinical diagnosis. Do not infer sensitive traits or exploit vulnerabilities.
+
+Original contribution: [PR 451](https://github.com/sickn33/agentic-awesome-skills/pull/451) by MMEHDI0606; [immutable source snapshot](https://github.com/MMEHDI0606/antigravity-awesome-skills/blob/9c61357e3e6bb167946036f52ac1e28fc82e04d0/skills/customer-psychographic-profiler/SKILL.md). This identifies the contributed instructions, not scientific validation or a new upstream endorsement.
+
 ## CONTEXT GATHERING
 
 Before profiling, establish:
@@ -43,23 +49,23 @@ People do not buy or act from demographics. They act from identity protection, n
 
 **Step 1 - Collect surface signals**
 List the explicit facts the user gives you, then separate them from interpretation. Use only observable details first.
-*Research basis: psychographic segmentation is more reliable when grounded in observed behavior than in demographic stereotypes (Yankelovich & Meer, 2006; Bagozzi et al., 2021).*
+*Planning hypothesis (verify before presenting as research): psychographic segmentation is more reliable when grounded in observed behavior than in demographic stereotypes (Yankelovich & Meer, 2006; Bagozzi et al., 2021).*
 
 **Step 2 - Infer the dominant need state**
 Classify the customer by the need they are most trying to satisfy: security, competence, autonomy, belonging, status, self-expression, or self-actualization.
-*Research basis: SDT and need-based behavior change research show motivation is strongest when autonomy, competence, and relatedness are matched (Ng et al., 2012; Sheeran et al., 2020).*
+*Planning hypothesis (verify before presenting as research): SDT and need-based behavior change research show motivation is strongest when autonomy, competence, and relatedness are matched (Ng et al., 2012; Sheeran et al., 2020).*
 
 **Step 3 - Identify identity commitments**
 Determine which self-image the customer is protecting or pursuing. Note what they want to be seen as, and what they refuse to be seen as.
-*Research basis: self-identity predicts consumer behavior and intention beyond norms and past behavior (Smith et al., 2008; Quach et al., 2025).*
+*Planning hypothesis (verify before presenting as research): self-identity predicts consumer behavior and intention beyond norms and past behavior (Smith et al., 2008; Quach et al., 2025).*
 
 **Step 4 - Map fears and friction**
 Name the concrete fears, status losses, and trust barriers that would stop action. Separate rational objections from emotional threat.
-*Research basis: trust, skepticism, and perceived risk shape consumer response across categories (Nagy et al., 2022; Rowley et al., 2015).*
+*Planning hypothesis (verify before presenting as research): trust, skepticism, and perceived risk shape consumer response across categories (Nagy et al., 2022; Rowley et al., 2015).*
 
 **Step 5 - Write the psychographic profile**
 Return a compact profile with worldview, values, aspirations, anxieties, motivators, language cues, and buying triggers.
-*Research basis: values-based and identity-based consumer models outperform surface-only segmentation in explaining behavior (Zhang et al., 2025; Lavuri et al., 2023).*
+*Planning hypothesis (verify before presenting as research): values-based and identity-based consumer models outperform surface-only segmentation in explaining behavior (Zhang et al., 2025; Lavuri et al., 2023).*
 
 ## DECISION MATRIX
 
@@ -106,7 +112,7 @@ The line between persuasion and manipulation is using psychological insight to p
 
 ## SKILL CHAINING
 
-Before invoking this skill, the agent should have completed:
+Optional context from related skills (equivalent supplied research is sufficient; do not create a prerequisite cycle):
 - [ ] `@awareness-stage-mapper` - if the audience's knowledge level is already known
 
 This skill's output feeds into:
@@ -131,6 +137,8 @@ Before finalizing output, the agent asks:
 
 > Build a psychographic profile for this audience before we decide positioning, copy, or funnel structure.
 
+**Illustrative output:** From three supplied interview excerpts, return observed statements, provisional motivations, unknowns and follow-up questions; do not infer health, political beliefs or hidden vulnerabilities.
+
 ## 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.

package/bundled-skills/customer-support/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 elite AI-powered customer support specialist focused on delivering exceptional customer experiences through advanced automation and human-centered design.
 

package/bundled-skills/data-engineering-data-driven-feature/SKILL.md

@@ -27,7 +27,6 @@ Build features guided by data insights, A/B testing, and continuous measurement
 - 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`.
 
 ## Phase 1: Data Analysis and Hypothesis Formation
 

package/bundled-skills/data-privacy-controls/SKILL.md

@@ -40,7 +40,7 @@ empty templates only - it never holds or processes real employee or customer dat
 
 ## How It Works
 
-Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
+Use the self-contained workflow below; no parent module or integration is required for empty local templates. Record lawful basis and retention as unknown until a qualified owner supplies them; a checkbox or example row does not establish compliance.
 
 ### Step 1 - Identify intent
 
@@ -104,15 +104,7 @@ Once the user asks for it, derive the fields from the confirmed context and emit
 requested artifacts. For machine-readable text, keep prose outside the data; for files,
 provide a usable link. Report material validation failures or limitations separately.
 
-**A selected Notion output is rendered by `notion-manual-import`, so route the
-Notion step there.** When the user selects Notion, hand that step to
-@notion-manual-import: it holds the CSV, the property
-mapping, the import steps and the verification checklist, and it renders the Field
-Reference below instead of defining a table of its own. Do not restate the mapping
-here and do not improvise the import steps. Manual CSV and mapping outputs need no
-connection. For requested workspace changes, follow the shared contract: verify actual
-tool access and the target before writing. A user saying "connected" is not tool evidence.
-Never ask for a Notion password or token.
+For a Notion output, provide the CSV and property mapping below for manual import. If `notion-manual-import` is separately available, it may assist with import instructions; it is optional. For requested workspace writes, verify actual tool access and the precise target, apply the authorized change, and read it back before claiming completion. Never ask for a password or token.
 
 For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the
 text correctly. A CSV is not an `.xlsx` workbook; create `.xlsx` only when the user
@@ -134,9 +126,9 @@ CREATE TABLE data_privacy_controls (
   retention_period VARCHAR(255),
   access_roles VARCHAR(255),
   encryption VARCHAR(255),
-  consent_required BOOLEAN NOT NULL,
+  consent_required BOOLEAN, -- NULL means applicability is unknown
   owner VARCHAR(255),
-  last_reviewed DATE NOT NULL,
+  last_reviewed DATE, -- NULL means no review has been recorded
   status VARCHAR(100) NOT NULL,
   control_id SERIAL PRIMARY KEY,
   created_at TIMESTAMP DEFAULT NOW(),
@@ -160,15 +152,14 @@ CREATE INDEX idx_data_privacy_controls_status ON data_privacy_controls (status);
       "Retention Period": { "type": "string" },
       "Access Roles": { "type": "string" },
       "Encryption": { "type": "string" },
-      "Consent Required": { "type": "boolean" },
+      "Consent Required": { "type": ["boolean", "null"] },
       "Owner": { "type": "string" },
-      "Last Reviewed": { "type": "string", "format": "date" },
+      "Last Reviewed": { "type": ["string", "null"], "format": "date" },
       "Status": { "type": "string" },
       "Control ID": { "type": "integer" }
   },
   "required": [
       "Data Category",
-      "Last Reviewed",
       "Status"
   ]
 }
@@ -184,7 +175,7 @@ CREATE INDEX idx_data_privacy_controls_status ON data_privacy_controls (status);
 | Retention Period | Text | Leave as Text |
 | Access Roles | Text | Leave as Text |
 | Encryption | Text | Leave as Text |
-| Consent Required | Checkbox | Convert to Checkbox |
+| Consent Required | Select | Use Unknown / Required / Not required; a Checkbox would collapse unknown into false |
 | Owner | Text | Leave as Text |
 | Last Reviewed | Date | Convert to Date |
 | Status | Select (add options after import) | Convert to Select, add options: "Draft", "In Review", "Approved", "Implemented", "Retired" |
@@ -205,9 +196,9 @@ and anything pointing at another table stays `relation`.
 | 5 | Retention Period | `text` | `VARCHAR(255)` | `string` | Text | `24 months after last activity` |
 | 6 | Access Roles | `text` | `VARCHAR(255)` | `string` | Text | `People team, Finance` |
 | 7 | Encryption | `text` | `VARCHAR(255)` | `string` | Text | `At rest and in transit` |
-| 8 | Consent Required | `checkbox` | `BOOLEAN` | `boolean` | Checkbox | `FALSE` |
+| 8 | Consent Required | `nullable boolean` | `BOOLEAN NULL` | `boolean or null` | Select: Unknown / Required / Not required | `FALSE` |
 | 9 | Owner | `text` | `VARCHAR(255)` | `string` | Text | `Sneha Iyer` |
-| 10 | Last Reviewed | `date` | `DATE` | `string, format: date` | Date | `2026-01-15` |
+| 10 | Last Reviewed | `nullable date` | `DATE NULL` | `string or null, format: date` | Date | `2026-01-15` |
 | 11 | Status | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Implemented` |
 | 12 | Control ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text (preserve source ID) | `(blank)` |
 
@@ -302,7 +293,7 @@ We hold a lot of employee data and cannot say who owns it.
 
 ## Related Skills
 
-- ](https://github.com/sickn33/agentic-awesome-skills/blob/main/CATALOG.md) - find the relevant module, then read its skill.
+- [Catalog](https://github.com/sickn33/agentic-awesome-skills/blob/main/CATALOG.md) - find the relevant module, then read its skill.
 - @people-directory - the employee master record most modules link to.
 - @notification-reminder-hub - turns due dates in this module into reminders.
 

package/bundled-skills/data-storytelling/SKILL.md

@@ -20,7 +20,7 @@ Transform raw data into compelling narratives that drive decisions and inspire a
 - 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`.
+- Use the frameworks and examples below; verify calculations against the supplied source data.
 
 ## Use this skill when
 
@@ -64,6 +64,8 @@ Resolution: Insights and recommendations
 
 ## Story Frameworks
 
+The numeric stories below are synthetic teaching examples, not observed customer outcomes or benchmarks. Replace their figures with verified input, show assumptions, and distinguish association from causation. Recalculate totals before recommending spending or forecasting impact.
+
 ### Framework 1: The Problem-Solution Story
 
 ```markdown
@@ -188,7 +190,7 @@ Should we expand into EMEA or APAC first?
 | Growth      | 30%    | 3          | 5          |
 | Competition | 20%    | 2          | 4          |
 | Ease        | 25%    | 2          | 3          |
-| **Total**   |        | **2.9**    | **4.1**    |
+| **Total**   |        | **3.05**   | **4.05**   |
 
 ## The Recommendation
 

package/bundled-skills/database-admin/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 database administrator specializing in modern cloud database operations, automation, and reliability engineering.
 

package/bundled-skills/database-design/SKILL.md

@@ -54,7 +54,11 @@ Before designing schema:
 ❌ Ignore N+1 queries
 
 ## When to Use
-This skill is applicable to execute the workflow or actions described in the overview.
+Use when selecting a database model, reviewing schema relationships and indexes, or assessing a proposed schema with the bundled advisory tools.
+
+## Schema helper
+
+`scripts/schema_validator.py` is a read-only heuristic inventory, not a Prisma or Drizzle parser. Missing schemas, unsupported formats and heuristic-only results return nonzero with `passed: false` and `analysis_complete: false`. Use the project-local ORM validator for syntax and type checks; review migration and constraint semantics separately.
 
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.

package/bundled-skills/database-design/database-selection.md

@@ -32,7 +32,7 @@ What are your requirements?
 | **Neon** | Serverless PG, branching | PG complexity |
 | **Turso** | Edge, low latency | SQLite limitations |
 | **SQLite** | Simple, embedded, local | Single-writer |
-| **PlanetScale** | MySQL, global scale | No foreign keys |
+| **PlanetScale** | Managed relational offerings | Engine, sharding and enabled constraints must be verified for the actual deployment |
 
 ## Questions to Ask
 

package/bundled-skills/database-design/orm-selection.md

@@ -25,6 +25,6 @@ What's the context?
 | ORM | Best For | Trade-offs |
 |-----|----------|------------|
 | **Drizzle** | Edge, TypeScript | Newer, less examples |
-| **Prisma** | DX, schema management | Heavier, not edge-ready |
+| **Prisma** | Schema management and tooling | Driver, adapter and edge runtime compatibility depend on the installed version |
 | **Kysely** | Type-safe SQL builder | Manual migrations |
 | **Raw SQL** | Complex queries, control | Manual type safety |

package/bundled-skills/database-design/scripts/schema_validator.py

@@ -1,7 +1,7 @@
 #!/usr/bin/env python3
 """
 Schema Validator - Database schema validation
-Validates Prisma schemas and checks for common issues.
+Provides incomplete Prisma regex hints. Never certifies schema validity.
 
 Usage:
     python schema_validator.py <project_path>
@@ -102,6 +102,9 @@ def main():
     print("-"*60)
     
     # Find schema files
+    if not project_path.is_dir():
+        print(json.dumps({"passed": False, "analysis_complete": False, "message": "Project directory missing"}))
+        sys.exit(2)
     schemas = find_schema_files(project_path)
     print(f"Found {len(schemas)} schema files")
     
@@ -111,14 +114,16 @@ def main():
             "project": str(project_path),
             "schemas_checked": 0,
             "issues_found": 0,
-            "passed": True,
-            "message": "No schema files found"
+            "passed": False,
+            "analysis_complete": False,
+            "message": "No schema files found; nothing validated"
         }
         print(json.dumps(output, indent=2))
-        sys.exit(0)
+        sys.exit(2)
     
     # Validate each schema
     all_issues = []
+    unsupported = []
     
     for schema_type, file_path in schemas:
         print(f"\nValidating: {file_path.name} ({schema_type})")
@@ -126,7 +131,8 @@ def main():
         if schema_type == 'prisma':
             issues = validate_prisma_schema(file_path)
         else:
-            issues = []  # Drizzle validation could be added
+            issues = ["Drizzle validation is not implemented"]
+            unsupported.append(str(file_path))
         
         if issues:
             all_issues.append({
@@ -148,11 +154,11 @@ def main():
             if len(item["issues"]) > 5:
                 print(f"  ... and {len(item['issues']) - 5} more issues")
     else:
-        print("No schema issues found!")
+        print("No heuristic issues found; schema validity remains unverified.")
     
     total_issues = sum(len(item["issues"]) for item in all_issues)
     # Schema issues are warnings, not failures
-    passed = True
+    passed = False  # Regex hints cannot establish schema validity.
     
     output = {
         "script": "schema_validator",
@@ -160,12 +166,15 @@ def main():
         "schemas_checked": len(schemas),
         "issues_found": total_issues,
         "passed": passed,
+        "analysis_complete": False,
+        "unsupported": unsupported,
+        "message": "Heuristic inventory only; run the project-local ORM validator",
         "issues": all_issues
     }
     
     print("\n" + json.dumps(output, indent=2))
     
-    sys.exit(0)
+    sys.exit(2)
 
 
 if __name__ == "__main__":

package/bundled-skills/database-migration/SKILL.md

@@ -5,6 +5,20 @@ 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>/references/orm-switching.md`
+- `<support-root>/references/schema-migration.md`
+- `<support-root>/references/data-transformation.md`
+- `<support-root>/references/rollback-strategies.md`
+- `<support-root>/assets/schema-migration-template.sql`
+- `<support-root>/assets/data-migration-script.py`
+- `<support-root>/scripts/test-migration.sh`
+
+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.
+
 
 # Database Migration
 
@@ -20,7 +34,6 @@ Master database schema and data migrations across ORMs (Sequelize, TypeORM, Pris
 - 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`.
 
 ## Use this skill when