@fprad0/skill-master-mcp 0.0.11 → 1.0.0

package/docs/skill-candidates/v0.0.11/shadcn/agents/openai.yaml

@@ -1,3 +1,3 @@
-interface:
-  display_name: "Shadcn"
-  short_description: "shadcn/ui expert guidance — CLI, component installation, composition patterns, custom registries, theming,..."
+interface:
+  display_name: "Shadcn"
+  short_description: "shadcn/ui expert guidance — CLI, component installation, composition patterns, custom registries, theming,..."

package/docs/skill-candidates/v0.0.11/sql-postgresql-engineering/SKILL.md

@@ -1,34 +1,34 @@
----
-name: sql-postgresql-engineering
-description: "Design and review SQL and PostgreSQL schemas, queries, migrations, indexes, transactions and runtime data behavior with practical focus on correctness, explainability and production safety."
----
-
-# SQL PostgreSQL Engineering
-
-Use this skill when the task centers on relational data, SQL behavior or PostgreSQL operations.
-
-## Workflow
-
-- Start from the real schema, query path and workload shape before proposing changes.
-- Model keys, constraints, indexes and migrations as deliberate design choices.
-- Explain query behavior, data movement and lock or transaction impact.
-- Prefer reversible migrations and representative explain or smoke validation.
-- Separate application-layer assumptions from database truth.
-
-## Coverage
-
-- SQL queries, joins, aggregations, migrations, constraints, indexes and transactions.
-- PostgreSQL schemas, performance, integrity, operational review and rollout risk.
-- Debugging, refactoring, data contracts and production hardening.
-
-## Reference Anchors
-
-- PostgreSQL docs: `https://www.postgresql.org/docs/`
-- PostgreSQL tutorial: `https://www.postgresql.org/docs/current/tutorial.html`
-
-## Guardrails
-
-- Do not run destructive data changes without explicit approval.
-- Do not add indexes without reasoning about write cost and access pattern.
-- Do not hide locking or migration risk.
-- Do not claim query improvements without evidence or an explain path.
+---
+name: sql-postgresql-engineering
+description: "Design and review SQL and PostgreSQL schemas, queries, migrations, indexes, transactions and runtime data behavior with practical focus on correctness, explainability and production safety."
+---
+
+# SQL PostgreSQL Engineering
+
+Use this skill when the task centers on relational data, SQL behavior or PostgreSQL operations.
+
+## Workflow
+
+- Start from the real schema, query path and workload shape before proposing changes.
+- Model keys, constraints, indexes and migrations as deliberate design choices.
+- Explain query behavior, data movement and lock or transaction impact.
+- Prefer reversible migrations and representative explain or smoke validation.
+- Separate application-layer assumptions from database truth.
+
+## Coverage
+
+- SQL queries, joins, aggregations, migrations, constraints, indexes and transactions.
+- PostgreSQL schemas, performance, integrity, operational review and rollout risk.
+- Debugging, refactoring, data contracts and production hardening.
+
+## Reference Anchors
+
+- PostgreSQL docs: `https://www.postgresql.org/docs/`
+- PostgreSQL tutorial: `https://www.postgresql.org/docs/current/tutorial.html`
+
+## Guardrails
+
+- Do not run destructive data changes without explicit approval.
+- Do not add indexes without reasoning about write cost and access pattern.
+- Do not hide locking or migration risk.
+- Do not claim query improvements without evidence or an explain path.

package/docs/skill-candidates/v0.0.11/terminal-shell-ops/SKILL.md

@@ -1,34 +1,34 @@
----
-name: terminal-shell-ops
-description: "Design and operate terminal, shell and command workflows across Bash, PowerShell and Node-driven CLIs with focus on clarity, portability, debuggability and safe automation."
----
-
-# Terminal Shell Ops
-
-Use this skill when the task is mainly shell, terminal interaction, operator UX or CLI execution flow.
-
-## Workflow
-
-- Confirm shell, OS and TTY assumptions before scripting behavior.
-- Keep commands inspectable, composable and easy to rerun.
-- Prefer explicit flags, paths and exit-code handling over hidden magic.
-- Model input/output, prompts and failure paths as operator-facing interfaces.
-- Validate with realistic terminal usage, not only static reading.
-
-## Coverage
-
-- Bash, PowerShell, terminal UX, CLI flows, scripts, prompts and automation.
-- PATH, environment variables, exit codes, streams, TTY detection and portability.
-- Operator documentation, reliability and troubleshooting.
-
-## Reference Anchors
-
-- Bash manual: `https://www.gnu.org/software/bash/manual/bash.html`
-- PowerShell docs: `https://learn.microsoft.com/powershell/`
-
-## Guardrails
-
-- Do not rely on shell-specific behavior without stating it.
-- Do not swallow stderr or exit codes.
-- Do not make interactive commands destructive by default.
-- Do not confuse development shortcuts with operator-safe automation.
+---
+name: terminal-shell-ops
+description: "Design and operate terminal, shell and command workflows across Bash, PowerShell and Node-driven CLIs with focus on clarity, portability, debuggability and safe automation."
+---
+
+# Terminal Shell Ops
+
+Use this skill when the task is mainly shell, terminal interaction, operator UX or CLI execution flow.
+
+## Workflow
+
+- Confirm shell, OS and TTY assumptions before scripting behavior.
+- Keep commands inspectable, composable and easy to rerun.
+- Prefer explicit flags, paths and exit-code handling over hidden magic.
+- Model input/output, prompts and failure paths as operator-facing interfaces.
+- Validate with realistic terminal usage, not only static reading.
+
+## Coverage
+
+- Bash, PowerShell, terminal UX, CLI flows, scripts, prompts and automation.
+- PATH, environment variables, exit codes, streams, TTY detection and portability.
+- Operator documentation, reliability and troubleshooting.
+
+## Reference Anchors
+
+- Bash manual: `https://www.gnu.org/software/bash/manual/bash.html`
+- PowerShell docs: `https://learn.microsoft.com/powershell/`
+
+## Guardrails
+
+- Do not rely on shell-specific behavior without stating it.
+- Do not swallow stderr or exit codes.
+- Do not make interactive commands destructive by default.
+- Do not confuse development shortcuts with operator-safe automation.