All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mcplab Tool Interface Contracts Observability Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts Observability Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Observability Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Observability Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Reconnect Handling Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts Reconnect Handling Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Reconnect Handling Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Reconnect Handling Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Release Readiness Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts Release Readiness Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Release Readiness Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Release Readiness Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Remote Deployment Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts Remote Deployment Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Remote Deployment Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for 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
- Mcplab Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Schema Changes Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts Schema Changes Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Schema Changes Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Schema Changes Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Untrusted Tool Output Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts 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: tool-interface contracts 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 Tool Interface Contracts Untrusted Tool Output Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: tool-interface contracts for 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
- Aas Agent Quality Retrieval Evidence Approval Evidence PacketUse when a retrieval evidence grounding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the retrieval-to-claim trace containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; every material claim maps to the retrieved evidence or is labeled unsupported. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Agent Quality Retrieval Evidence Change Impact TraceUse when a version, rule, source, or stakeholder change may affect retrieval evidence grounding to produce a before/after change record and impact map for the retrieval-to-claim trace. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every material claim maps to the retrieved evidence or is labeled unsupported. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Aas Agent Quality Retrieval Evidence Closeout Handoff LedgerUse when a retrieval evidence grounding work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the retrieval-to-claim trace with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; every material claim maps to the retrieved evidence or is labeled unsupported. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2