@fprad0/skill-master-mcp 0.0.11 → 1.0.0

package/docs/skill-candidates/v0.0.11/git-version-control-ops/SKILL.md

@@ -1,34 +1,34 @@
----
-name: git-version-control-ops
-description: "Operate Git histories, branches, diffs, merges, rebases and release flows with practical attention to safety, reviewability, recovery paths and team collaboration."
----
-
-# Git Version Control Ops
-
-Use this skill when the task is mainly about Git rather than application code itself.
-
-## Workflow
-
-- Identify branch state, remote state and uncommitted work before acting.
-- Prefer reviewable, reversible moves over clever history surgery.
-- Keep commit intent explicit and scoped.
-- Explain impact before risky history operations.
-- Validate branch state after push, merge or release moves.
-
-## Coverage
-
-- Diffs, commits, branches, tags, merges, rebases, cherry-picks and release prep.
-- Recovery paths, conflict handling, remote sync and safe operator workflows.
-- Collaboration hygiene for Git-based delivery.
-
-## Reference Anchors
-
-- Git docs: `https://git-scm.com/docs`
-- Git book: `https://git-scm.com/book/en/v2`
-
-## Guardrails
-
-- Do not rewrite shared history casually.
-- Do not hide destructive commands behind vague wording.
-- Do not mix unrelated changes in one release commit.
-- Do not claim sync safety without checking remote state.
+---
+name: git-version-control-ops
+description: "Operate Git histories, branches, diffs, merges, rebases and release flows with practical attention to safety, reviewability, recovery paths and team collaboration."
+---
+
+# Git Version Control Ops
+
+Use this skill when the task is mainly about Git rather than application code itself.
+
+## Workflow
+
+- Identify branch state, remote state and uncommitted work before acting.
+- Prefer reviewable, reversible moves over clever history surgery.
+- Keep commit intent explicit and scoped.
+- Explain impact before risky history operations.
+- Validate branch state after push, merge or release moves.
+
+## Coverage
+
+- Diffs, commits, branches, tags, merges, rebases, cherry-picks and release prep.
+- Recovery paths, conflict handling, remote sync and safe operator workflows.
+- Collaboration hygiene for Git-based delivery.
+
+## Reference Anchors
+
+- Git docs: `https://git-scm.com/docs`
+- Git book: `https://git-scm.com/book/en/v2`
+
+## Guardrails
+
+- Do not rewrite shared history casually.
+- Do not hide destructive commands behind vague wording.
+- Do not mix unrelated changes in one release commit.
+- Do not claim sync safety without checking remote state.

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

@@ -1,34 +1,34 @@
----
-name: go-engineering
-description: "Build and review Go services, CLIs and concurrent systems with focus on package design, interfaces, context handling, observability, testing and operational robustness."
----
-
-# Go Engineering
-
-Use this skill when the task is primarily Go code, tooling or service design.
-
-## Workflow
-
-- Inspect module structure, package boundaries and entrypoints before editing.
-- Treat `context`, errors, interfaces and goroutine lifecycle as explicit design concerns.
-- Keep packages small, concrete and easy to test.
-- Favor predictable composition over deep abstraction trees.
-- Validate with build, tests and representative runtime paths.
-
-## Coverage
-
-- Go APIs, CLIs, workers, packages, modules and concurrency patterns.
-- Context propagation, cancellation, channels, HTTP, configuration and logging.
-- Refactors, debugging, code review and deployment-grade hardening.
-
-## Reference Anchors
-
-- Go docs: `https://go.dev/doc/`
-- Go language spec: `https://go.dev/ref/spec`
-
-## Guardrails
-
-- Do not leak goroutines or ignore cancellation.
-- Do not use interfaces prematurely.
-- Do not bury errors without context.
-- Do not overcomplicate package layout for small services.
+---
+name: go-engineering
+description: "Build and review Go services, CLIs and concurrent systems with focus on package design, interfaces, context handling, observability, testing and operational robustness."
+---
+
+# Go Engineering
+
+Use this skill when the task is primarily Go code, tooling or service design.
+
+## Workflow
+
+- Inspect module structure, package boundaries and entrypoints before editing.
+- Treat `context`, errors, interfaces and goroutine lifecycle as explicit design concerns.
+- Keep packages small, concrete and easy to test.
+- Favor predictable composition over deep abstraction trees.
+- Validate with build, tests and representative runtime paths.
+
+## Coverage
+
+- Go APIs, CLIs, workers, packages, modules and concurrency patterns.
+- Context propagation, cancellation, channels, HTTP, configuration and logging.
+- Refactors, debugging, code review and deployment-grade hardening.
+
+## Reference Anchors
+
+- Go docs: `https://go.dev/doc/`
+- Go language spec: `https://go.dev/ref/spec`
+
+## Guardrails
+
+- Do not leak goroutines or ignore cancellation.
+- Do not use interfaces prematurely.
+- Do not bury errors without context.
+- Do not overcomplicate package layout for small services.

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

@@ -1,34 +1,34 @@
----
-name: java-engineering
-description: "Design, implement and review Java applications, services and CLIs with attention to build tooling, JVM behavior, package boundaries, testing, dependency hygiene and production-grade maintainability."
----
-
-# Java Engineering
-
-Use this skill when the task is centered on Java application code or JVM service design.
-
-## Workflow
-
-- Identify the build system first: Maven, Gradle or plain Java tooling.
-- Read package layout, dependency graph and runtime assumptions before changing code.
-- Keep domain logic separated from framework glue and infrastructure code.
-- Treat configuration, threading, serialization and resource lifecycle as first-class concerns.
-- Validate with compile, test and representative runtime entrypoints.
-
-## Coverage
-
-- Java services, libraries, CLIs, packaging, dependency management and test structure.
-- JVM runtime behavior, configuration, exceptions, concurrency and integration boundaries.
-- Refactors, code review, API design and deployment readiness.
-
-## Reference Anchors
-
-- Java learning docs: `https://dev.java/learn/`
-- OpenJDK docs: `https://openjdk.org/`
-
-## Guardrails
-
-- Do not hide checked/unchecked error boundaries.
-- Do not couple business logic tightly to framework annotations or containers.
-- Do not introduce build-tool drift without updating the whole workflow.
-- Do not claim thread safety without concrete reasoning.
+---
+name: java-engineering
+description: "Design, implement and review Java applications, services and CLIs with attention to build tooling, JVM behavior, package boundaries, testing, dependency hygiene and production-grade maintainability."
+---
+
+# Java Engineering
+
+Use this skill when the task is centered on Java application code or JVM service design.
+
+## Workflow
+
+- Identify the build system first: Maven, Gradle or plain Java tooling.
+- Read package layout, dependency graph and runtime assumptions before changing code.
+- Keep domain logic separated from framework glue and infrastructure code.
+- Treat configuration, threading, serialization and resource lifecycle as first-class concerns.
+- Validate with compile, test and representative runtime entrypoints.
+
+## Coverage
+
+- Java services, libraries, CLIs, packaging, dependency management and test structure.
+- JVM runtime behavior, configuration, exceptions, concurrency and integration boundaries.
+- Refactors, code review, API design and deployment readiness.
+
+## Reference Anchors
+
+- Java learning docs: `https://dev.java/learn/`
+- OpenJDK docs: `https://openjdk.org/`
+
+## Guardrails
+
+- Do not hide checked/unchecked error boundaries.
+- Do not couple business logic tightly to framework annotations or containers.
+- Do not introduce build-tool drift without updating the whole workflow.
+- Do not claim thread safety without concrete reasoning.

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

@@ -1,34 +1,34 @@
----
-name: javascript-engineering
-description: "Implement and review JavaScript and Node.js applications with focus on modules, async flows, runtime behavior, APIs, tooling, compatibility and operational reliability across browser and server contexts."
----
-
-# JavaScript Engineering
-
-Use this skill when the task is mainly JavaScript or Node.js rather than type-heavy TypeScript.
-
-## Workflow
-
-- Determine the runtime first: browser, Node.js, worker, edge or test harness.
-- Verify module mode, package boundaries and build assumptions before changing imports.
-- Keep async behavior explicit: promises, retries, streams, events and shutdown paths.
-- Separate transport, domain logic and persistence so the runtime stays testable.
-- Validate with direct execution paths and representative failure cases.
-
-## Coverage
-
-- JavaScript, Node.js, modules, packages, scripts, APIs, jobs and automation.
-- Async control flow, JSON payloads, process lifecycle, file system and child processes.
-- Runtime debugging, compatibility issues, migration and production hardening.
-
-## Reference Anchors
-
-- MDN JavaScript docs: `https://developer.mozilla.org/en-US/docs/Web/JavaScript`
-- Node.js docs: `https://nodejs.org/en/docs`
-
-## Guardrails
-
-- Do not confuse browser and server APIs.
-- Do not introduce silent promise failures or ignored rejections.
-- Do not change module systems casually in mixed ESM/CJS projects.
-- Do not hide runtime assumptions from the user.
+---
+name: javascript-engineering
+description: "Implement and review JavaScript and Node.js applications with focus on modules, async flows, runtime behavior, APIs, tooling, compatibility and operational reliability across browser and server contexts."
+---
+
+# JavaScript Engineering
+
+Use this skill when the task is mainly JavaScript or Node.js rather than type-heavy TypeScript.
+
+## Workflow
+
+- Determine the runtime first: browser, Node.js, worker, edge or test harness.
+- Verify module mode, package boundaries and build assumptions before changing imports.
+- Keep async behavior explicit: promises, retries, streams, events and shutdown paths.
+- Separate transport, domain logic and persistence so the runtime stays testable.
+- Validate with direct execution paths and representative failure cases.
+
+## Coverage
+
+- JavaScript, Node.js, modules, packages, scripts, APIs, jobs and automation.
+- Async control flow, JSON payloads, process lifecycle, file system and child processes.
+- Runtime debugging, compatibility issues, migration and production hardening.
+
+## Reference Anchors
+
+- MDN JavaScript docs: `https://developer.mozilla.org/en-US/docs/Web/JavaScript`
+- Node.js docs: `https://nodejs.org/en/docs`
+
+## Guardrails
+
+- Do not confuse browser and server APIs.
+- Do not introduce silent promise failures or ignored rejections.
+- Do not change module systems casually in mixed ESM/CJS projects.
+- Do not hide runtime assumptions from the user.

package/docs/skill-candidates/v0.0.11/json-contract-design/SKILL.md

@@ -1,34 +1,34 @@
----
-name: json-contract-design
-description: "Define and review JSON payloads, schemas and machine-readable contracts with emphasis on compatibility, validation, naming consistency and integration safety across APIs and automation."
----
-
-# JSON Contract Design
-
-Use this skill when the task is about JSON structures, schemas or exchange contracts between systems.
-
-## Workflow
-
-- Identify producers, consumers and compatibility expectations first.
-- Define required versus optional fields explicitly.
-- Keep naming, nullability, enums and nested structures consistent.
-- Add validation boundaries close to ingress and egress points.
-- Validate with realistic examples and edge cases.
-
-## Coverage
-
-- JSON payloads, schemas, API contracts, config files and event/message bodies.
-- Compatibility review, migration planning, serialization and validation strategy.
-- Human-readable examples for integration and debugging.
-
-## Reference Anchors
-
-- JSON RFC 8259: `https://www.rfc-editor.org/rfc/rfc8259`
-- JSON Schema: `https://json-schema.org/`
-
-## Guardrails
-
-- Do not introduce ambiguous null versus missing semantics.
-- Do not rename contract fields casually across active integrations.
-- Do not rely on informal examples when a schema is needed.
-- Do not hide breaking changes.
+---
+name: json-contract-design
+description: "Define and review JSON payloads, schemas and machine-readable contracts with emphasis on compatibility, validation, naming consistency and integration safety across APIs and automation."
+---
+
+# JSON Contract Design
+
+Use this skill when the task is about JSON structures, schemas or exchange contracts between systems.
+
+## Workflow
+
+- Identify producers, consumers and compatibility expectations first.
+- Define required versus optional fields explicitly.
+- Keep naming, nullability, enums and nested structures consistent.
+- Add validation boundaries close to ingress and egress points.
+- Validate with realistic examples and edge cases.
+
+## Coverage
+
+- JSON payloads, schemas, API contracts, config files and event/message bodies.
+- Compatibility review, migration planning, serialization and validation strategy.
+- Human-readable examples for integration and debugging.
+
+## Reference Anchors
+
+- JSON RFC 8259: `https://www.rfc-editor.org/rfc/rfc8259`
+- JSON Schema: `https://json-schema.org/`
+
+## Guardrails
+
+- Do not introduce ambiguous null versus missing semantics.
+- Do not rename contract fields casually across active integrations.
+- Do not rely on informal examples when a schema is needed.
+- Do not hide breaking changes.

package/docs/skill-candidates/v0.0.11/multi-client-mcp-ops/SKILL.md

@@ -1,36 +1,36 @@
----
-name: multi-client-mcp-ops
-description: "Configure and validate MCP readiness across Codex, Claude, Gemini and Antigravity with practical focus on client config, transport, global registration and operator troubleshooting."
----
-
-# Multi Client MCP Ops
-
-Use this skill when the task is about making MCP servers work consistently across multiple AI clients.
-
-## Workflow
-
-- Start from the target client and its real config file path.
-- Verify transport, command, args, working directory and environment requirements.
-- Keep registration reproducible and explain how the user can verify it.
-- Separate local clone execution from global npm-installed execution.
-- Validate readiness client by client instead of assuming parity.
-
-## Coverage
-
-- Codex, Claude, Gemini and Antigravity MCP registration and troubleshooting.
-- Global versus project-local config, stdio commands, PATH and restart requirements.
-- Operator-facing readiness checks and rollout hygiene.
-
-## Reference Anchors
-
-- OpenAI Codex MCP docs: `https://developers.openai.com/codex/mcp/`
-- Model Context Protocol docs: `https://modelcontextprotocol.io/docs/develop/connect-local-servers`
-- Gemini CLI MCP docs: `https://google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html`
-- Antigravity MCP docs: `https://cloud.google.com/gemini/enterprise/docs/antigravity/mcp-servers`
-
-## Guardrails
-
-- Do not assume one client config format works unchanged in another.
-- Do not claim readiness without checking the effective config path and command.
-- Do not hide restart requirements after config changes.
-- Do not mix package-global and repo-local command assumptions.
+---
+name: multi-client-mcp-ops
+description: "Configure and validate MCP readiness across Codex, Claude, Gemini and Antigravity with practical focus on client config, transport, global registration and operator troubleshooting."
+---
+
+# Multi Client MCP Ops
+
+Use this skill when the task is about making MCP servers work consistently across multiple AI clients.
+
+## Workflow
+
+- Start from the target client and its real config file path.
+- Verify transport, command, args, working directory and environment requirements.
+- Keep registration reproducible and explain how the user can verify it.
+- Separate local clone execution from global npm-installed execution.
+- Validate readiness client by client instead of assuming parity.
+
+## Coverage
+
+- Codex, Claude, Gemini and Antigravity MCP registration and troubleshooting.
+- Global versus project-local config, stdio commands, PATH and restart requirements.
+- Operator-facing readiness checks and rollout hygiene.
+
+## Reference Anchors
+
+- OpenAI Codex MCP docs: `https://developers.openai.com/codex/mcp/`
+- Model Context Protocol docs: `https://modelcontextprotocol.io/docs/develop/connect-local-servers`
+- Gemini CLI MCP docs: `https://google-gemini.github.io/gemini-cli/docs/tools/mcp-server.html`
+- Antigravity MCP docs: `https://cloud.google.com/gemini/enterprise/docs/antigravity/mcp-servers`
+
+## Guardrails
+
+- Do not assume one client config format works unchanged in another.
+- Do not claim readiness without checking the effective config path and command.
+- Do not hide restart requirements after config changes.
+- Do not mix package-global and repo-local command assumptions.