All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Server Registry Metadata Remote Deployment Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: server-registry metadata for remote deployment. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means requirements have priorities, evidence, ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: server-registry metadata for remote deployment. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means the owner, constraints, baseline, and acceptance signal are e...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: server-registry metadata for remote deployment. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means material claims are linked to current primary sources with dates and limitat...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment 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: server-registry metadata for remote deployment. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Review authentication, transport security, tenant isolation, consent, data retention, and deployment exposure before remote use. Success means each critical requirement...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Schema Changes Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: server-registry metadata for schema changes. Produce a bounded build or configuration runbook 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 prepared result is reproducible, reviewable, and w...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Schema Changes Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for schema changes. Produce a staged design blueprint 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 interfaces, dependencies, constraints, and review points are testable before ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Schema Changes Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: server-registry metadata for schema changes. Produce a failure-triage record and reversible recovery plan 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 failure is bounded by observations, one te...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Schema Changes Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: server-registry metadata 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 uncerta...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 meas...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 per...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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, per...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Schema Changes Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: server-registry metadata 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 permis...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 repro...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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, r...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Untrusted Tool Output Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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 ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 obse...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 crite...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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, ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata 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: server-registry metadata 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 e...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Untrusted Tool Output Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: server-registry metadata 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 limitat...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility 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 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, and with...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport 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 before bui...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, one testa...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility Measured Improvement And HandoffUse when a measured result or recurring failure suggests a change worth testing and handing to an owner for Model Context Protocol servers and integrations: stdio transport for client compatibility. Produce a versioned improvement proposal and handoff packet 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 proposed change is compared w...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility 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 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 uncertaint...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, and measura...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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. Use permis...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility 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 client compatibility. Produce a scoped risk-and-control review 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 review names relevant hazards, permis...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Client Compatibility Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport 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 permissio...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 reproduc...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Conformance Testing 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 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, reviewable, ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Conformance Testing Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport 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 testable be...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 observations, o...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Conformance Testing 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 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 criteria with un...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, owners, and...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 explicit. Us...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Conformance Testing 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 conformance testing. Produce a scoped risk-and-control review 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 review names relevant hazards...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Conformance Testing Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport 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 limitations. Use p...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 maps to a ...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, and wit...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Least Privilege Access Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport 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 before bu...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, one test...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 uncertain...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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, and measur...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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. Use permi...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Least Privilege Access 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 least-privilege access. Produce a scoped risk-and-control review 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 review names relevant hazards, permi...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Least Privilege Access Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: stdio transport 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 permissi...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport 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: stdio transport 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 a reprodu...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Local Development 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 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, and within...Votes: 0GitHub stars: 2
- Mcplab Stdio Transport Local Development Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: stdio transport 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 before build...Votes: 0GitHub stars: 2