All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Remote Http Transport Reconnect Handling Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport 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, revie...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Reconnect Handling Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP transport 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 test...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 observat...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Reconnect Handling Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: remote HTTP transport 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 Remote Http Transport 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: remote HTTP transport 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, owne...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 expli...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Reconnect Handling 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: remote HTTP transport for reconnect handling. Produce a scoped risk-and-control review 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 review names relevant ...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Reconnect Handling Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: remote HTTP transport 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 limitations...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 map...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Release Readiness Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport 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, reviewable...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Release Readiness Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP transport 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 Remote Http Transport 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: remote HTTP transport 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 Remote Http Transport Release Readiness Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: remote HTTP transport 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 Remote Http Transport 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: remote HTTP transport 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, a...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 Remote Http Transport 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: remote HTTP transport 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 hazar...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Release Readiness Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: remote HTTP transport 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. Use...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 Remote Http Transport Remote Deployment Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport 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, revi...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Remote Deployment Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP transport 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 tes...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 observa...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Remote Deployment Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: remote HTTP transport 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 criteria...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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, own...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 expl...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Remote Deployment 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: remote HTTP transport for remote deployment. Produce a scoped risk-and-control review 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 review names relevant...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: remote HTTP transport 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 limitation...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 ma...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Schema Changes Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport 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 with...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Schema Changes Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP transport 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 bui...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport 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: remote HTTP transport 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 testa...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Schema Changes 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: remote HTTP transport for schema changes. Produce a versioned improvement proposal and handoff packet 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 proposed change is compared w...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 uncertaint...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 measura...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 permis...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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, permis...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Schema Changes Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: remote HTTP 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 permissio...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 reproduc...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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, revi...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Untrusted Tool Output Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP 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 tes...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 observa...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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, own...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 expl...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 limitation...Votes: 0GitHub stars: 2
- Mcplab Remote Http 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: remote HTTP 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 ma...Votes: 0GitHub stars: 2
- Mcplab Resource Discovery Client Compatibility Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: resource discovery 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 w...Votes: 0GitHub stars: 2
- Mcplab Resource Discovery Client Compatibility Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: resource discovery 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 ...Votes: 0GitHub stars: 2
- Mcplab Resource Discovery 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: resource discovery 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 te...Votes: 0GitHub stars: 2
- Mcplab Resource Discovery Client Compatibility Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: resource discovery 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 uncerta...Votes: 0GitHub stars: 2
- Mcplab Resource Discovery 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: resource discovery 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 meas...Votes: 0GitHub stars: 2