All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Mtls Configuration Permission Boundary ReviewUse when Mutual TLS configuration may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Mutual TLS configuration showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to certificate identity, trust-chain boundary, client...Votes: 0GitHub stars: 2
- Mtls Configuration Release Handoff RecordUse when a Mutual TLS configuration review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Mutual TLS configuration with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to certificate identity, trust-chain boundary,...Votes: 0GitHub stars: 2
- Mtls Configuration Reproducibility Fixture PlanUse when a Mutual TLS configuration result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Mutual TLS configuration defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to certificate ide...Votes: 0GitHub stars: 2
- Mtls Configuration Version CompatibilityUse when a Mutual TLS configuration integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Mutual TLS configuration with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to certificate identity, trust-chain boun...Votes: 0GitHub stars: 2
- Pci Compliance Capability Surface MapUse when the actual capability boundary of Payment-card control evidence needs to be distinguished from assumptions. Produce a capability map for Payment-card control evidence covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to in-scope data flow, system bounda...Votes: 0GitHub stars: 2
- Pci Compliance Change Impact AssessmentUse when a proposed Payment-card control evidence version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Payment-card control evidence with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to in-scope data flow, system boun...Votes: 0GitHub stars: 2
- Pci Compliance Failure Triage RecordUse when a reproducible Payment-card control evidence symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Payment-card control evidence with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to in-scope data flow, system boundary, control evidence, retention, and...Votes: 0GitHub stars: 2
- Pci Compliance Input Output ContractUse when the accepted inputs or produced outputs for Payment-card control evidence need a checkable boundary. Produce an input/output contract for Payment-card control evidence with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to in-scope data flow, system boundary, control evidence, retent...Votes: 0GitHub stars: 2
- Pci Compliance Integration Parity TraceUse when Payment-card control evidence exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Payment-card control evidence showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to in-scope data flow, system boundary, control evidence, retention, and assessor...Votes: 0GitHub stars: 2
- Pci Compliance Performance EnvelopeUse when Payment-card control evidence must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Payment-card control evidence with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to in-scope data flow, system boundary, control eviden...Votes: 0GitHub stars: 2
- Pci Compliance Permission Boundary ReviewUse when Payment-card control evidence may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Payment-card control evidence showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to in-scope data flow, system boundary, con...Votes: 0GitHub stars: 2
- Pci Compliance Release Handoff RecordUse when a Payment-card control evidence review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Payment-card control evidence with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to in-scope data flow, system bounda...Votes: 0GitHub stars: 2
- Pci Compliance Reproducibility Fixture PlanUse when a Payment-card control evidence result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Payment-card control evidence defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to in-sc...Votes: 0GitHub stars: 2
- Pci Compliance Version CompatibilityUse when a Payment-card control evidence integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Payment-card control evidence with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to in-scope data flow, system b...Votes: 0GitHub stars: 2
- Pentest KaliUse when a task involves conducting a bounded penetration test with Kali tools against a system explicitly authorized for testing to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not inst...Votes: 0GitHub stars: 2
- Pentest ToolsUse when a task involves selecting and operating security-testing tools for a permitted assessment with an auditable scope to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or ...Votes: 0GitHub stars: 2
- Policy As Code Capability Surface MapUse when the actual capability boundary of Policy-as-code systems needs to be distinguished from assumptions. Produce a capability map for Policy-as-code systems covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to policy source and version, evaluation inputs, e...Votes: 0GitHub stars: 2
- Policy As Code Change Impact AssessmentUse when a proposed Policy-as-code systems version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Policy-as-code systems with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to policy source and version, evaluation inputs,...Votes: 0GitHub stars: 2
- Policy As Code Failure Triage RecordUse when a reproducible Policy-as-code systems symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Policy-as-code systems with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to policy source and version, evaluation inputs, enforcement stage, exceptions, and ro...Votes: 0GitHub stars: 2
- Policy As Code Input Output ContractUse when the accepted inputs or produced outputs for Policy-as-code systems need a checkable boundary. Produce an input/output contract for Policy-as-code systems with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to policy source and version, evaluation inputs, enforcement stage, exceptions...Votes: 0GitHub stars: 2
- Policy As Code Integration Parity TraceUse when Policy-as-code systems exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Policy-as-code systems showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to policy source and version, evaluation inputs, enforcement stage, exceptions, and rollback bo...Votes: 0GitHub stars: 2
- Policy As Code Performance EnvelopeUse when Policy-as-code systems must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Policy-as-code systems with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to policy source and version, evaluation inputs, enforcement stage, ...Votes: 0GitHub stars: 2
- Policy As Code Permission Boundary ReviewUse when Policy-as-code systems may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Policy-as-code systems showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to policy source and version, evaluation inputs, enforcem...Votes: 0GitHub stars: 2
- Policy As Code Release Handoff RecordUse when a Policy-as-code systems review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Policy-as-code systems with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to policy source and version, evaluation inputs, e...Votes: 0GitHub stars: 2
- Policy As Code Reproducibility Fixture PlanUse when a Policy-as-code systems result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Policy-as-code systems defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to policy source and v...Votes: 0GitHub stars: 2
- Policy As Code Version CompatibilityUse when a Policy-as-code systems integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Policy-as-code systems with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to policy source and version, evaluation inpu...Votes: 0GitHub stars: 2
- Privacy By Design Capability Surface MapUse when the actual capability boundary of Privacy-by-design review needs to be distinguished from assumptions. Produce a capability map for Privacy-by-design review covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to data purpose, field necessity, consent boun...Votes: 0GitHub stars: 2
- Privacy By Design Change Impact AssessmentUse when a proposed Privacy-by-design review version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Privacy-by-design review with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to data purpose, field necessity, consent bo...Votes: 0GitHub stars: 2
- Privacy By Design Failure Triage RecordUse when a reproducible Privacy-by-design review symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Privacy-by-design review with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to data purpose, field necessity, consent boundary, retention, access, and deletio...Votes: 0GitHub stars: 2
- Privacy By Design Input Output ContractUse when the accepted inputs or produced outputs for Privacy-by-design review need a checkable boundary. Produce an input/output contract for Privacy-by-design review with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to data purpose, field necessity, consent boundary, retention, access, and...Votes: 0GitHub stars: 2
- Privacy By Design Integration Parity TraceUse when Privacy-by-design review exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Privacy-by-design review showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to data purpose, field necessity, consent boundary, retention, access, and deletion path. U...Votes: 0GitHub stars: 2
- Privacy By Design Performance EnvelopeUse when Privacy-by-design review must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Privacy-by-design review with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to data purpose, field necessity, consent boundary, retention, a...Votes: 0GitHub stars: 2
- Privacy By Design Permission Boundary ReviewUse when Privacy-by-design review may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Privacy-by-design review showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to data purpose, field necessity, consent boundary, r...Votes: 0GitHub stars: 2
- Privacy By Design Release Handoff RecordUse when a Privacy-by-design review review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Privacy-by-design review with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to data purpose, field necessity, consent boun...Votes: 0GitHub stars: 2
- Privacy By Design Reproducibility Fixture PlanUse when a Privacy-by-design review result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Privacy-by-design review defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to data purpose, f...Votes: 0GitHub stars: 2
- Privacy By Design Version CompatibilityUse when a Privacy-by-design review integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Privacy-by-design review with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to data purpose, field necessity, consent...Votes: 0GitHub stars: 2
- Privacy Mask Capability Surface MapUse when the actual capability boundary of Sensitive image and screenshot masking needs to be distinguished from assumptions. Produce a capability map for Sensitive image and screenshot masking covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to source-image id...Votes: 0GitHub stars: 2
- Privacy Mask Change Impact AssessmentUse when a proposed Sensitive image and screenshot masking version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Sensitive image and screenshot masking with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to source-image ...Votes: 0GitHub stars: 2
- Privacy Mask Failure Triage RecordUse when a reproducible Sensitive image and screenshot masking symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Sensitive image and screenshot masking with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to source-image identity, target regions, transformed-...Votes: 0GitHub stars: 2
- Privacy Mask Input Output ContractUse when the accepted inputs or produced outputs for Sensitive image and screenshot masking need a checkable boundary. Produce an input/output contract for Sensitive image and screenshot masking with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to source-image identity, target regions, tran...Votes: 0GitHub stars: 2
- Privacy Mask Integration Parity TraceUse when Sensitive image and screenshot masking exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Sensitive image and screenshot masking showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to source-image identity, target regions, transformed-copy stat...Votes: 0GitHub stars: 2
- Privacy Mask Performance EnvelopeUse when Sensitive image and screenshot masking must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Sensitive image and screenshot masking with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to source-image identity, target reg...Votes: 0GitHub stars: 2
- Privacy Mask Permission Boundary ReviewUse when Sensitive image and screenshot masking may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Sensitive image and screenshot masking showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to source-image identity,...Votes: 0GitHub stars: 2
- Privacy Mask Release Handoff RecordUse when a Sensitive image and screenshot masking review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Sensitive image and screenshot masking with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to source-image id...Votes: 0GitHub stars: 2
- Privacy Mask Reproducibility Fixture PlanUse when a Sensitive image and screenshot masking result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Sensitive image and screenshot masking defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review i...Votes: 0GitHub stars: 2
- Privacy Mask Version CompatibilityUse when a Sensitive image and screenshot masking integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Sensitive image and screenshot masking with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to source-ima...Votes: 0GitHub stars: 2
- Remote Mac Build Agent Isolation ReviewUse when a task involves reviewing isolation and credential exposure on a remote macOS build worker to record Swift, Xcode, operating-system, build, and target versions; reproduction steps; data sensitivity; and the permission boundary before acting. Check current Apple or Swift documentation, preserve source and trace provenance, and verify on an owned test target. Do not change signing credentials, publish, notarize, or operate production systems without explicit approval.Votes: 0GitHub stars: 2
- Security Account Takeover Containment ReviewUse when a task involves coordinating response when evidence suggests an identity may be controlled by an unauthorized actor to record the asset owner, authorized environment, exact scope, applicable policy or assessment approval, evidence source, data sensitivity, and potential service impact. Prefer current primary references, bounded non-destructive checks, synthetic data, and independently verifiable evidence. Separate observed facts from assumptions, preserve uncertainty, and obtain expl...Votes: 0GitHub stars: 2
- Security Active Passive Assessment BoundaryUse when a task involves classifying proposed security assessment actions by their potential to affect a target to record the asset owner, authorized environment, exact scope, applicable policy or assessment approval, evidence source, data sensitivity, and potential service impact. Prefer current primary references, bounded non-destructive checks, synthetic data, and independently verifiable evidence. Separate observed facts from assumptions, preserve uncertainty, and obtain explicit approval...Votes: 0GitHub stars: 2
- Security Assessment Privacy Impact ScreenUse when a task involves screening a security test for exposure of personal or sensitive information to record the asset owner, authorized environment, exact scope, applicable policy or assessment approval, evidence source, data sensitivity, and potential service impact. Prefer current primary references, bounded non-destructive checks, synthetic data, and independently verifiable evidence. Separate observed facts from assumptions, preserve uncertainty, and obtain explicit approval before act...Votes: 0GitHub stars: 2