All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Conformance Testing 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 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Least Privilege Access Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Least Privilege Access 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 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Local Development 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 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 Server Registry Metadata Local Development Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Local Development 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 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Local Development 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 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 Server Registry Metadata 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: server-registry metadata 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 Server Registry Metadata Observability 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 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 Server Registry Metadata Observability Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata 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
- Mcplab Server Registry Metadata Observability 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 observability. Produce a failure-triage record and reversible recovery plan 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 failure is bounded by observations, one te...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce an evidence-backed option-comparison matrix 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 options are compared on user-approved criteria with uncerta...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce a reviewable requirements and decision brief 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 requirements have priorities, evidence, owners, and meas...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce a scope-and-baseline record 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 owner, constraints, baseline, and acceptance signal are explicit. Use per...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce a scoped risk-and-control review 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 review names relevant hazards, per...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce a source-and-claim ledger 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 material claims are linked to current primary sources with dates and limitations. Use permis...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Observability 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 observability. Produce a risk-weighted verification plan with saved evidence 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 each critical requirement maps to a repro...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the prepared result is reproducible, re...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for reconnect handling. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means interfaces, dependencies, constraints, and review points are t...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the failure is bounded by obser...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means options are compared on user-approved criter...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means requirements have priorities, evidence, o...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means the owner, constraints, baseline, and acceptance signal are ex...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means material claims are linked to current primary sources with dates and limitati...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Reconnect Handling 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 reconnect handling. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Test disconnection, duplicate request, timeout, cancellation, and retry boundaries without repeating a consequential mutation. Success means each critical requirement ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the prepared result is reproducible, reviewa...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for release readiness. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means interfaces, dependencies, constraints, and review points are testab...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the failure is bounded by observatio...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means options are compared on user-approved criteria wi...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means requirements have priorities, evidence, owners...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means the owner, constraints, baseline, and acceptance signal are explici...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means material claims are linked to current primary sources with dates and limitations. ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Release Readiness 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 release readiness. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Gate release on versioned docs, compatibility notes, least-privilege review, regression results, and an accountable owner. Success means each critical requirement maps ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment 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 remote deployment. Produce a bounded build or configuration runbook 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 prepared result is reproducible, r...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: server-registry metadata for remote deployment. Produce a staged design blueprint 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 interfaces, dependencies, constraints, and review points are ...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment 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 remote deployment. Produce a failure-triage record and reversible recovery plan 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 failure is bounded by obse...Votes: 0GitHub stars: 2
- Mcplab Server Registry Metadata Remote Deployment 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 remote deployment. Produce an evidence-backed option-comparison matrix 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 options are compared on user-approved crite...Votes: 0GitHub stars: 2