All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Devtools Sdk Error Contract Threshold Rule CheckUse when a SDK error and retry semantics decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the SDK error behavior table showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; callers can distinguish retryable from terminal errors without duplicate writes. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Approval Evidence PacketUse when a mobile push-token lifecycle result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the push-token state transition map 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; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile push-token lifecycle to produce a before/after change record and impact map for the push-token state transition map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Closeout Handoff LedgerUse when a mobile push-token lifecycle work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the push-token state transition map 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; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Completeness ReconciliationUse when the mobile push-token lifecycle workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the push-token state transition map with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Exception Triage QueueUse when the mobile push-token lifecycle workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the push-token state transition map with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Recovery Readiness DrillUse when the mobile push-token lifecycle workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the push-token state transition map with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Scenario Sensitivity MatrixUse when the mobile push-token lifecycle team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the push-token state transition map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Scope Intake GateUse when a new mobile push-token lifecycle request needs a bounded work scope to produce a scoped intake card for the push-token state transition map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three foc...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Source Provenance LedgerUse when a decision about mobile push-token lifecycle depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the push-token state transition map. Success means each material claim has a source, version/date, location, and confidence note; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- Aas Mobile Push Token Lifecycle Threshold Rule CheckUse when a mobile push-token lifecycle decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the push-token state transition map showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; stale tokens are not attributed to the wrong account and opt-out is respected. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Api Contract DesignUse when designing or changing an HTTP API contract consumed by another service, client, or team to specify resources, method semantics, schemas, errors, pagination, compatibility, and security boundaries before implementation. Trigger for new endpoints, public or partner APIs, versioning decisions, and contract reviews.Votes: 0GitHub stars: 2
- Api Example Versioned Compile SmokecheckUse when a code sample references a versioned API or constructor to create or update a version-to-example compatibility record with compiler/test output. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the example compiles or its version limitation is explicitly documented. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Api Fixture Contract Roundtrip TestUse when an API client or serializer changes request or response handling to create or update a round-trip test set with expected normalized values. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the encoded payload validates and decodes to the same documented semantics. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.Votes: 0GitHub stars: 2
- Api Onboarding Capability Surface MapUse when the actual capability boundary of API developer onboarding needs to be distinguished from assumptions. Produce a capability map for API developer onboarding 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 first-request prerequisites, credential set...Votes: 0GitHub stars: 2
- Api Onboarding Change Impact AssessmentUse when a proposed API developer onboarding version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for API developer onboarding 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 first-request prerequisites, credential s...Votes: 0GitHub stars: 2
- Api Onboarding Failure Triage RecordUse when a reproducible API developer onboarding symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for API developer onboarding 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 first-request prerequisites, credential setup boundaries, sample-data identity,...Votes: 0GitHub stars: 2
- Api Onboarding Input Output ContractUse when the accepted inputs or produced outputs for API developer onboarding need a checkable boundary. Produce an input/output contract for API developer onboarding 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 first-request prerequisites, credential setup boundaries, sample-data i...Votes: 0GitHub stars: 2
- Api Onboarding Integration Parity TraceUse when API developer onboarding exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for API developer onboarding 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 first-request prerequisites, credential setup boundaries, sample-data identity, and obse...Votes: 0GitHub stars: 2
- Api Onboarding Performance EnvelopeUse when API developer onboarding must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for API developer onboarding 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 first-request prerequisites, credential setup boundaries, sam...Votes: 0GitHub stars: 2
- Api Onboarding Permission Boundary ReviewUse when API developer onboarding may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for API developer onboarding 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 first-request prerequisites, credential setup boun...Votes: 0GitHub stars: 2
- Api Onboarding Release Handoff RecordUse when a API developer onboarding review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for API developer onboarding 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 first-request prerequisites, credential set...Votes: 0GitHub stars: 2
- Api Onboarding Reproducibility Fixture PlanUse when a API developer onboarding result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for API developer onboarding 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 first-request p...Votes: 0GitHub stars: 2
- Api Onboarding Version CompatibilityUse when a API developer onboarding integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for API developer onboarding 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 first-request prerequisites, credentia...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Capability Surface MapUse when the actual capability boundary of API rate-limit handling needs to be distinguished from assumptions. Produce a capability map for API rate-limit handling 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 quota headers, retry-after interpretation, id...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Change Impact AssessmentUse when a proposed API rate-limit handling version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for API rate-limit handling 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 quota headers, retry-after interpretation, ...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Failure Triage RecordUse when a reproducible API rate-limit handling symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for API rate-limit handling 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 quota headers, retry-after interpretation, idempotency, backoff budget, and calle...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Input Output ContractUse when the accepted inputs or produced outputs for API rate-limit handling need a checkable boundary. Produce an input/output contract for API rate-limit handling 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 quota headers, retry-after interpretation, idempotency, backoff budget, a...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Integration Parity TraceUse when API rate-limit handling exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for API rate-limit handling 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 quota headers, retry-after interpretation, idempotency, backoff budget, and caller-visible...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Performance EnvelopeUse when API rate-limit handling must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for API rate-limit handling 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 quota headers, retry-after interpretation, idempotency, backoff...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Permission Boundary ReviewUse when API rate-limit handling may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for API rate-limit handling 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 quota headers, retry-after interpretation, idempoten...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Release Handoff RecordUse when a API rate-limit handling review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for API rate-limit handling 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 quota headers, retry-after interpretation, id...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Reproducibility Fixture PlanUse when a API rate-limit handling result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for API rate-limit handling 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 quota headers, re...Votes: 0GitHub stars: 2
- Api Rate Limit Handler Version CompatibilityUse when a API rate-limit handling integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for API rate-limit handling 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 quota headers, retry-after interpretatio...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Approval Evidence PacketUse when a API contract evolution result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the API compatibility matrix 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; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect API contract evolution to produce a before/after change record and impact map for the API compatibility matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Closeout Handoff LedgerUse when a API contract evolution work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the API compatibility matrix 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; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Completeness ReconciliationUse when the API contract evolution workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the API compatibility matrix with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Exception Triage QueueUse when the API contract evolution workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the API compatibility matrix with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Recovery Readiness DrillUse when the API contract evolution workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the API compatibility matrix with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Scenario Sensitivity MatrixUse when the API contract evolution team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the API compatibility matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Scope Intake GateUse when a new API contract evolution request needs a bounded work scope to produce a scoped intake card for the API compatibility matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes,...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Source Provenance LedgerUse when a decision about API contract evolution depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the API compatibility matrix. Success means each material claim has a source, version/date, location, and confidence note; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Backend Ops Api Contract Threshold Rule CheckUse when a API contract evolution decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the API compatibility matrix showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; known consumers retain a supported path and breaking differences are explicit. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Approval Evidence PacketUse when a backend authorization boundaries result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the authorization decision table 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; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend authorization boundaries to produce a before/after change record and impact map for the authorization decision table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Closeout Handoff LedgerUse when a backend authorization boundaries work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the authorization decision table 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; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Completeness ReconciliationUse when the backend authorization boundaries workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the authorization decision table with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Exception Triage QueueUse when the backend authorization boundaries workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the authorization decision table with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Recovery Readiness DrillUse when the backend authorization boundaries workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the authorization decision table with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2