All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 29,024
- 1,210
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse security skills
Showing 1,945–1,968 of 29,024 skills
- Mcplab Remote Http Transport Conformance Testing Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport for conformance testing. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Exercise required protocol conformance cases against the pinned spec; report unimplemented optional capabilities separately. Success means the prepared result is reproducible, review...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Security Rights And Safety ReviewUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the review names relevant hazards, ...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Scope And Baseline RecordUse when the work needs a verified goal, authorized boundary, and starting state for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use ...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Requirements And Decision BriefUse when a request must be converted into testable constraints and an owned decision for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means requirements have priorities, evidence, owners, and m...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means options are compared on user-approved criteria with unce...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Failure Triage And RecoveryUse when an unexpected result needs diagnosis without widening risk or losing evidence for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the failure is bounded by observations, one...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means interfaces, dependencies, constraints, and review points are testable befo...Votes: 0GitHub stars: 2
- Mcplab Remote Http Transport Client Compatibility Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: remote HTTP transport for client compatibility. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Verify the target host/client protocol version and negotiated capabilities with the actual supported client matrix. Success means the prepared result is reproducible, reviewable, an...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 exp...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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, ow...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 criteri...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 observ...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design Untrusted Tool Output Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: prompt-template design 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 te...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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, rev...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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, permi...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 permi...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 measur...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design Schema Changes Option Comparison MatrixUse when several tools, designs, methods, or workflows could satisfy the same need for Model Context Protocol servers and integrations: prompt-template design 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 uncertain...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 test...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design Schema Changes Design BlueprintUse when a solution needs a coherent structure before implementation or production for Model Context Protocol servers and integrations: prompt-template design 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 bu...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design Schema Changes Build Configuration RunbookUse when an authorized implementation needs repeatable steps and a visible change boundary for Model Context Protocol servers and integrations: prompt-template design 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 wit...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design 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: prompt-template design 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 m...Votes: 0GitHub stars: 2
- Mcplab Prompt Template Design Remote Deployment Source Research And Provenance LedgerUse when a decision depends on current, source-grounded information for Model Context Protocol servers and integrations: prompt-template design 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
- Mcplab Prompt Template Design 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: prompt-template design 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