All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Stdio Transport Schema Changes Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means options are compared on user-approved criteria with uncertainty and ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means requirements have priorities, evidence, owners, and measurable ac...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means the review names relevant hazards, permissions,...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned in...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Schema Changes Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: stdio transport for schema changes. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Diff the old and new schema and check required fields, optionality, error behavior, and compatibility at both ends. Success means each critical requirement maps to a reproducible c...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the prepared result is reproducible, reviewable...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means interfaces, dependencies, constraints, and review points are testable ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the failure is bounded by observations,...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means options are compared on user-approved criteria with ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means requirements have priorities, evidence, owners, a...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the owner, constraints, baseline, and acceptance signal are explicit. ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means the review names relevant hazar...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means material claims are linked to current primary sources with dates and limitations. Use...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Untrusted Tool Output Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: stdio transport for untrusted tool output. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Validate tool results as untrusted data, constrain output size/type, and do not execute returned instructions automatically. Success means each critical requirement maps to ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the prepared result is reproducible, reviewable,...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means interfaces, dependencies, constraints, and review points are testable b...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the failure is bounded by observations, ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means options are compared on user-approved criteria with u...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means requirements have priorities, evidence, owners, an...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the owner, constraints, baseline, and acceptance signal are explicit. U...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means material claims are linked to current primary sources with dates and limitations. Use ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Client Compatibility Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: tool-interface contracts for client compatibility. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means each critical requirement maps to a...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the prepared result is reproducible, rev...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means interfaces, dependencies, constraints, and review points are te...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the failure is bounded by observ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means options are compared on user-approved criteri...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means requirements have priorities, evidence, ow...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the owner, constraints, baseline, and acceptance signal are exp...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means material claims are linked to current primary sources with dates and limitatio...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Conformance Testing Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: tool-interface contracts for conformance testing. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means each critical requirement m...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the prepared result is reproducible, reviewable...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means interfaces, dependencies, constraints, and review points are testable ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the failure is bounded by observations,...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means options are compared on user-approved criteria with ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means requirements have priorities, evidence, owners, a...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means the owner, constraints, baseline, and acceptance signal are explicit. ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means material claims are linked to current primary sources with dates and limitations. Use...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Least Privilege Access Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: tool-interface contracts for least-privilege access. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: List the minimum resources, tools, roots, and scopes required; reject wildcard access when a narrower grant works. Success means each critical requirement maps to ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the prepared result is reproducible, reviewable, a...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means interfaces, dependencies, constraints, and review points are testable bef...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the failure is bounded by observations, on...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means options are compared on user-approved criteria with unc...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means requirements have priorities, evidence, owners, and ...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means the review names relevant hazards,...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means material claims are linked to current primary sources with dates and limitations. Use pe...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Local Development Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Model Context Protocol servers and integrations: tool-interface contracts for local development. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Test with synthetic data and local fixtures; inspect filesystem, environment, and network permissions before launch. Success means each critical requirement maps to a r...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Observability Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for observability. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means the prepared result is reproducible, reviewable, and w...Votes: 0GitHub stars: 2
- Mcplab Tool Interface Contracts Observability Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts for observability. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Emit correlation and outcome metadata while redacting secrets, prompts, personal data, and sensitive tool arguments. Success means interfaces, dependencies, constraints, and review points are testable before ...Votes: 0GitHub stars: 2