All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Backend Ops Observability Redaction Scenario Sensitivity MatrixUse when the backend observability and log redaction team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the log-field review matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Scope Intake GateUse when a new backend observability and log redaction request needs a bounded work scope to produce a scoped intake card for the log-field review matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Source Provenance LedgerUse when a decision about backend observability and log redaction depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the log-field review matrix. Success means each material claim has a source, version/date, location, and confidence note; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Threshold Rule CheckUse when a backend observability and log redaction decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Approval Evidence PacketUse when a API pagination and filtering semantics result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search,...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Change Impact TraceUse when a version, rule, source, or stakeholder change may affect API pagination and filtering semantics to produce a before/after change record and impact map for the pagination contract worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Closeout Handoff LedgerUse when a API pagination and filtering semantics work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Completeness ReconciliationUse when the API pagination and filtering semantics workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Exception Triage QueueUse when the API pagination and filtering semantics workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Recovery Readiness DrillUse when the API pagination and filtering semantics workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Scenario Sensitivity MatrixUse when the API pagination and filtering semantics team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the pagination contract worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Scope Intake GateUse when a new API pagination and filtering semantics request needs a bounded work scope to produce a scoped intake card for the pagination contract worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Source Provenance LedgerUse when a decision about API pagination and filtering semantics depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the pagination contract worksheet. Success means each material claim has a source, version/date, location, and confidence note; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Backend Ops Pagination Semantics Threshold Rule CheckUse when a API pagination and filtering semantics decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the pagination contract worksheet 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; page boundaries neither skip nor duplicate stable test records under declared assumptions. Use configured search, fe...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Approval Evidence PacketUse when a backend connection pool saturation behavior result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend connection pool saturation behavior to produce a before/after change record and impact map for the connection-pool saturation profile. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Closeout Handoff LedgerUse when a backend connection pool saturation behavior work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Completeness ReconciliationUse when the backend connection pool saturation behavior workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured search, ...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Exception Triage QueueUse when the backend connection pool saturation behavior workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Recovery Readiness DrillUse when the backend connection pool saturation behavior workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fe...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Scenario Sensitivity MatrixUse when the backend connection pool saturation behavior team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the connection-pool saturation profile with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Scope Intake GateUse when a new backend connection pool saturation behavior request needs a bounded work scope to produce a scoped intake card for the connection-pool saturation profile. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Source Provenance LedgerUse when a decision about backend connection pool saturation behavior depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the connection-pool saturation profile. Success means each material claim has a source, version/date, location, and confidence note; queue growth is visible before saturation and the test remains isolated from production. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Backend Ops Pool Saturation Threshold Rule CheckUse when a backend connection pool saturation behavior decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the connection-pool saturation profile 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; queue growth is visible before saturation and the test remains isolated from production. Use configured se...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Approval Evidence PacketUse when a backend release compatibility result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, f...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend release compatibility to produce a before/after change record and impact map for the staged-release evidence packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Closeout Handoff LedgerUse when a backend release compatibility work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Completeness ReconciliationUse when the backend release compatibility workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Exception Triage QueueUse when the backend release compatibility workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Recovery Readiness DrillUse when the backend release compatibility workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Scenario Sensitivity MatrixUse when the backend release compatibility team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the staged-release evidence packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Scope Intake GateUse when a new backend release compatibility request needs a bounded work scope to produce a scoped intake card for the staged-release evidence packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Source Provenance LedgerUse when a decision about backend release compatibility depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the staged-release evidence packet. Success means each material claim has a source, version/date, location, and confidence note; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Backend Ops Release Compatibility Threshold Rule CheckUse when a backend release compatibility decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the staged-release evidence packet 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; the release candidate meets predeclared gates and no live rollout is triggered by this workflow. Use configured search, fetc...Votes: 0GitHub stars: 2
- Bittorrent Client DevelopmentUse when implementing or reviewing a BitTorrent client, parser, peer protocol, or piece-transfer workflow to start with a bounded, lawful test torrent and validate metainfo, peer messages, piece hashes, file paths, and resource limits before enabling broader networking. Trigger for BitTorrent-compatible download or seeding behavior.Votes: 0GitHub stars: 2
- Blockchain Cryptocurrency DevelopmentUse when designing or implementing a blockchain, cryptocurrency ledger, wallet prototype, transaction format, or consensus experiment to separate educational simulation from production financial systems, define state-transition invariants, and use vetted cryptographic libraries rather than inventing primitives. Trigger for ledger, token, block, transaction, wallet, or chain-reorganization work.Votes: 0GitHub stars: 2
- Browser Api Replay Write Safety ReviewUse when a task involves reviewing whether a browser-captured API request can be replayed without unintended side effects to record the target site and origin, browser and driver version, active account, test or production context, user authorization, data sensitivity, and intended side effects. Use a bounded, reproducible interaction, verify both browser-visible and relevant underlying state, preserve evidence safely, and report uncertainty. Do not reuse profiles, disclose authentication sta...Votes: 0GitHub stars: 2
- Fastapi Router PatternsUse when a task involves organizing FastAPI routes around validated request models, dependency boundaries, and testable service logic 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 ...Votes: 0GitHub stars: 2
- Search Engine DevelopmentUse when building a search system over an application, document collection, or structured dataset without a public-web crawler as its main purpose to define corpus scope, tokenization, ranking goals, freshness, and access rules before indexing. Trigger for analyzers, inverted indexes, query execution, ranking, or search relevance work.Votes: 0GitHub stars: 2
- Swift Global Actor Api Boundary CheckUse when a task involves reviewing global-actor annotations on public types, protocols, and callbacks 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
- Web Server DevelopmentUse when implementing an HTTP server, routing layer, reverse proxy, or web-serving runtime to define supported protocol behavior, concurrency and resource limits, and trust boundaries before exposing a listener; test malformed requests and filesystem access in a local harness. Trigger for request parsing, routing, middleware, static files, or server lifecycle work.Votes: 0GitHub stars: 2
- Write Read Consistency Staleness Window ProbeUse when a system uses caches, replicas, or asynchronous indexing after a write to create or update a bounded consistency trace with write acknowledgement and read timestamps. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the observed propagation window fits the documented contract or is escalated. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally vi...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Approval Evidence PacketUse when a mobile deep-link routing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the deep-link route test 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Change Impact TraceUse when a version, rule, source, or stakeholder change may affect mobile deep-link routing to produce a before/after change record and impact map for the deep-link route test matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Closeout Handoff LedgerUse when a mobile deep-link routing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the deep-link route test 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Completeness ReconciliationUse when the mobile deep-link routing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the deep-link route test 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Exception Triage QueueUse when the mobile deep-link routing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the deep-link route test 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Recovery Readiness DrillUse when the mobile deep-link routing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the deep-link route test 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; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Scenario Sensitivity MatrixUse when the mobile deep-link routing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the deep-link route test matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Mobile Deep Link Routing Scope Intake GateUse when a new mobile deep-link routing request needs a bounded work scope to produce a scoped intake card for the deep-link route test matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; valid links reach the intended screen and malformed or unauthorized links fail closed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2