All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Capability Negotiation Least Privilege Access Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 be...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, o...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 un...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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. Us...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Least Privilege Access Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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 p...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 ...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Local Development Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation 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...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Local Development Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 befor...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, one ...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Local Development Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation 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 uncer...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 me...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 p...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, p...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Local Development Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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 perm...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 rep...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation 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 wit...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 bu...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: capability negotiation 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 test...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability 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: capability negotiation for observability. Produce a versioned improvement proposal and handoff packet 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 proposed change is compared ...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation 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 uncertain...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 measur...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: capability negotiation 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 permi...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, permi...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Observability Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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 permissi...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 reprodu...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Reconnect Handling Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation 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, revi...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Reconnect Handling Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 tes...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 observa...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Reconnect Handling Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation 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 criteria...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, own...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 expl...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Reconnect Handling Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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 limitation...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 ma...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Release Readiness Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation 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, reviewabl...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Release Readiness Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 testable...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 observations...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Release Readiness Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation 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 with...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 Capability Negotiation 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: capability negotiation 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 explicit....Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Release Readiness 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: capability negotiation for release readiness. Produce a scoped risk-and-control review 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 review names relevant haza...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Release Readiness Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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. Us...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 to...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Remote Deployment Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: capability negotiation 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, rev...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Remote Deployment Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: capability negotiation 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 te...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 observ...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Remote Deployment Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: capability negotiation 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 criteri...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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, ow...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation 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: capability negotiation 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 exp...Votes: 0GitHub stars: 2
- Mcplab Capability Negotiation Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: capability negotiation 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 limitatio...Votes: 0GitHub stars: 2