All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aws Cloudtrail Change Impact AssessmentUse when a proposed AWS CloudTrail audit evidence version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for AWS CloudTrail audit 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 trail identity, event scope, de...Votes: 0GitHub stars: 2
- Aws Cloudtrail Failure Triage RecordUse when a reproducible AWS CloudTrail audit evidence symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for AWS CloudTrail audit 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 trail identity, event scope, destination, retention, access control, ...Votes: 0GitHub stars: 2
- Aws Cloudtrail Input Output ContractUse when the accepted inputs or produced outputs for AWS CloudTrail audit evidence need a checkable boundary. Produce an input/output contract for AWS CloudTrail audit 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 trail identity, event scope, destination, retention, access c...Votes: 0GitHub stars: 2
- Aws Cloudtrail Integration Parity TraceUse when AWS CloudTrail audit evidence exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for AWS CloudTrail audit 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 trail identity, event scope, destination, retention, access control, and cover...Votes: 0GitHub stars: 2
- Aws Cloudtrail Performance EnvelopeUse when AWS CloudTrail audit evidence must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for AWS CloudTrail audit 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 trail identity, event scope, destination, retention...Votes: 0GitHub stars: 2
- Aws Cloudtrail Permission Boundary ReviewUse when AWS CloudTrail audit evidence may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for AWS CloudTrail audit 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 trail identity, event scope, destination...Votes: 0GitHub stars: 2
- Aws Cloudtrail Release Handoff RecordUse when a AWS CloudTrail audit evidence review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for AWS CloudTrail audit 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 trail identity, event scope, dest...Votes: 0GitHub stars: 2
- Aws Cloudtrail Reproducibility Fixture PlanUse when a AWS CloudTrail audit evidence result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for AWS CloudTrail audit 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 trail...Votes: 0GitHub stars: 2
- Aws Cloudtrail Version CompatibilityUse when a AWS CloudTrail audit evidence integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for AWS CloudTrail audit 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 trail identity, event scope,...Votes: 0GitHub stars: 2
- Aws Iam Capability Surface MapUse when the actual capability boundary of AWS IAM access review needs to be distinguished from assumptions. Produce a capability map for AWS IAM access 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 principal identity, action/resource scope, trust ...Votes: 0GitHub stars: 2
- Aws Iam Change Impact AssessmentUse when a proposed AWS IAM access review version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for AWS IAM access 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 principal identity, action/resource scope, trus...Votes: 0GitHub stars: 2
- Aws Iam Failure Triage RecordUse when a reproducible AWS IAM access review symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for AWS IAM access 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 principal identity, action/resource scope, trust relationship, session boundary, and ...Votes: 0GitHub stars: 2
- Aws Iam Input Output ContractUse when the accepted inputs or produced outputs for AWS IAM access review need a checkable boundary. Produce an input/output contract for AWS IAM access 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 principal identity, action/resource scope, trust relationship, session bounda...Votes: 0GitHub stars: 2
- Aws Iam Integration Parity TraceUse when AWS IAM access review exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for AWS IAM access 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 principal identity, action/resource scope, trust relationship, session boundary, and policy pr...Votes: 0GitHub stars: 2
- Aws Iam Performance EnvelopeUse when AWS IAM access review must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for AWS IAM access 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 principal identity, action/resource scope, trust relationship, sess...Votes: 0GitHub stars: 2
- Aws Iam Permission Boundary ReviewUse when AWS IAM access review may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for AWS IAM access 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 principal identity, action/resource scope, trust relatio...Votes: 0GitHub stars: 2
- Aws Iam Release Handoff RecordUse when a AWS IAM access review review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for AWS IAM access 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 principal identity, action/resource scope, trust ...Votes: 0GitHub stars: 2
- Aws Iam Reproducibility Fixture PlanUse when a AWS IAM access review result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for AWS IAM access 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 principal identity, a...Votes: 0GitHub stars: 2
- Aws Iam Version CompatibilityUse when a AWS IAM access review integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for AWS IAM access 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 principal identity, action/resource scope, t...Votes: 0GitHub stars: 2
- Aws Secrets Manager Capability Surface MapUse when the actual capability boundary of AWS Secrets Manager lifecycle review needs to be distinguished from assumptions. Produce a capability map for AWS Secrets Manager lifecycle 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 secret identity, co...Votes: 0GitHub stars: 2
- Aws Secrets Manager Change Impact AssessmentUse when a proposed AWS Secrets Manager lifecycle review version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for AWS Secrets Manager lifecycle 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 secret identity, ...Votes: 0GitHub stars: 2
- Aws Secrets Manager Failure Triage RecordUse when a reproducible AWS Secrets Manager lifecycle review symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for AWS Secrets Manager lifecycle 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 secret identity, consumer scope, version state, rotatio...Votes: 0GitHub stars: 2
- Aws Secrets Manager Input Output ContractUse when the accepted inputs or produced outputs for AWS Secrets Manager lifecycle review need a checkable boundary. Produce an input/output contract for AWS Secrets Manager lifecycle 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 secret identity, consumer scope, version state,...Votes: 0GitHub stars: 2
- Aws Secrets Manager Integration Parity TraceUse when AWS Secrets Manager lifecycle review exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for AWS Secrets Manager lifecycle 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 secret identity, consumer scope, version state, rotation evidenc...Votes: 0GitHub stars: 2
- Aws Secrets Manager Performance EnvelopeUse when AWS Secrets Manager lifecycle review must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for AWS Secrets Manager lifecycle 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 secret identity, consumer scope, vers...Votes: 0GitHub stars: 2
- Aws Secrets Manager Permission Boundary ReviewUse when AWS Secrets Manager lifecycle review may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for AWS Secrets Manager lifecycle 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 secret identity, consumer ...Votes: 0GitHub stars: 2
- Aws Secrets Manager Release Handoff RecordUse when a AWS Secrets Manager lifecycle review review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for AWS Secrets Manager lifecycle 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 secret identity, co...Votes: 0GitHub stars: 2
- Aws Secrets Manager Reproducibility Fixture PlanUse when a AWS Secrets Manager lifecycle review result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for AWS Secrets Manager lifecycle 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 bo...Votes: 0GitHub stars: 2
- Aws Secrets Manager Version CompatibilityUse when a AWS Secrets Manager lifecycle review integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for AWS Secrets Manager lifecycle 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 secret identit...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Capability Surface MapUse when the actual capability boundary of Azure Key Vault Secrets SDK for Java needs to be distinguished from assumptions. Produce a capability map for Azure Key Vault Secrets SDK for Java 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 secret identity, ve...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Change Impact AssessmentUse when a proposed Azure Key Vault Secrets SDK for Java version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Azure Key Vault Secrets SDK for Java 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 secret identity, ...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Failure Triage RecordUse when a reproducible Azure Key Vault Secrets SDK for Java symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Azure Key Vault Secrets SDK for Java 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 secret identity, version lifecycle, cache behavior, mas...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Input Output ContractUse when the accepted inputs or produced outputs for Azure Key Vault Secrets SDK for Java need a checkable boundary. Produce an input/output contract for Azure Key Vault Secrets SDK for Java 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 secret identity, version lifecycle, cache behav...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Integration Parity TraceUse when Azure Key Vault Secrets SDK for Java exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Azure Key Vault Secrets SDK for Java 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 secret identity, version lifecycle, cache behavior, masking, and...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Performance EnvelopeUse when Azure Key Vault Secrets SDK for Java must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Azure Key Vault Secrets SDK for Java 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 secret identity, version lifecycle, c...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Permission Boundary ReviewUse when Azure Key Vault Secrets SDK for Java may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Azure Key Vault Secrets SDK for Java 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 secret identity, version l...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Release Handoff RecordUse when a Azure Key Vault Secrets SDK for Java review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Azure Key Vault Secrets SDK for Java 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 secret identity, ve...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Reproducibility Fixture PlanUse when a Azure Key Vault Secrets SDK for Java result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Azure Key Vault Secrets SDK for Java 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 bo...Votes: 0GitHub stars: 2
- Azure Security Keyvault Secrets Java Version CompatibilityUse when a Azure Key Vault Secrets SDK for Java integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Azure Key Vault Secrets SDK for Java 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 secret identit...Votes: 0GitHub stars: 2
- Camera Privacy Redaction Before Cloud ReviewUse when a task involves checking image or video redaction before authorized cloud transfer to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-cont...Votes: 0GitHub stars: 2
- Ci Log Secret Redaction Summary GateUse when an agent prepares a report from workflow logs or test output to create or update a redacted summary with evidence ranges and redaction notes. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the summary retains the root-cause signal without secret-like values or excess log data. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irrev...Votes: 0GitHub stars: 2
- Cloud Identity Credential ReviewUse when a task involves reviewing cloud identity and credential configuration for least privilege, lifecycle, and exposure risks 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
- Kali LinuxUse when a task involves using Kali Linux tools for authorized learning, defensive assessment, or an isolated lab exercise 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
- Linux Seccomp Profile ReviewUse when a task involves reviewing a seccomp policy against an application's required system calls to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, devi...Votes: 0GitHub stars: 2
- Mtls Configuration Capability Surface MapUse when the actual capability boundary of Mutual TLS configuration needs to be distinguished from assumptions. Produce a capability map for Mutual TLS configuration 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 certificate identity, trust-chain boundary,...Votes: 0GitHub stars: 2
- Mtls Configuration Change Impact AssessmentUse when a proposed Mutual TLS configuration version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Mutual TLS configuration 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 certificate identity, trust-chain boundar...Votes: 0GitHub stars: 2
- Mtls Configuration Failure Triage RecordUse when a reproducible Mutual TLS configuration symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Mutual TLS configuration 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 certificate identity, trust-chain boundary, client/server role, expiry, and rot...Votes: 0GitHub stars: 2
- Mtls Configuration Input Output ContractUse when the accepted inputs or produced outputs for Mutual TLS configuration need a checkable boundary. Produce an input/output contract for Mutual TLS configuration 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 certificate identity, trust-chain boundary, client/server role, expiry,...Votes: 0GitHub stars: 2
- Mtls Configuration Integration Parity TraceUse when Mutual TLS configuration exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Mutual TLS configuration 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 certificate identity, trust-chain boundary, client/server role, expiry, and rotation evi...Votes: 0GitHub stars: 2
- Mtls Configuration Performance EnvelopeUse when Mutual TLS configuration must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Mutual TLS configuration 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 certificate identity, trust-chain boundary, client/server rol...Votes: 0GitHub stars: 2