All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Agent Telemetry Replay Fixture Recovery Readiness DrillUse when the agent trace replay fixtures workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Scenario Sensitivity MatrixUse when the agent trace replay fixtures team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the minimized replay fixture with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Scope Intake GateUse when a new agent trace replay fixtures request needs a bounded work scope to produce a scoped intake card for the minimized replay fixture. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Source Provenance LedgerUse when a decision about agent trace replay fixtures depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the minimized replay fixture. Success means each material claim has a source, version/date, location, and confidence note; the fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Threshold Rule CheckUse when a agent trace replay fixtures decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Approval Evidence PacketUse when a agent retry and timeout timelines result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent retry and timeout timelines to produce a before/after change record and impact map for the retry timeline. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Closeout Handoff LedgerUse when a agent retry and timeout timelines work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Completeness ReconciliationUse when the agent retry and timeout timelines workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Exception Triage QueueUse when the agent retry and timeout timelines workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Recovery Readiness DrillUse when the agent retry and timeout timelines workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Scenario Sensitivity MatrixUse when the agent retry and timeout timelines team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the retry timeline with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Scope Intake GateUse when a new agent retry and timeout timelines request needs a bounded work scope to produce a scoped intake card for the retry timeline. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Source Provenance LedgerUse when a decision about agent retry and timeout timelines depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the retry timeline. Success means each material claim has a source, version/date, location, and confidence note; the timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Agent Telemetry Retry Timeline Threshold Rule CheckUse when a agent retry and timeout timelines decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the retry timeline 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 timeline matches the configured budget and repeated calls are not mistaken for independent success. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Approval Evidence PacketUse when a agent model and route tracing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent model and route tracing to produce a before/after change record and impact map for the route-selection evidence note. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Closeout Handoff LedgerUse when a agent model and route tracing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Completeness ReconciliationUse when the agent model and route tracing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Exception Triage QueueUse when the agent model and route tracing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Recovery Readiness DrillUse when the agent model and route tracing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Scenario Sensitivity MatrixUse when the agent model and route tracing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the route-selection evidence note with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Scope Intake GateUse when a new agent model and route tracing request needs a bounded work scope to produce a scoped intake card for the route-selection evidence note. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Source Provenance LedgerUse when a decision about agent model and route tracing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the route-selection evidence note. Success means each material claim has a source, version/date, location, and confidence note; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Agent Telemetry Routing Trace Threshold Rule CheckUse when a agent model and route tracing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the route-selection evidence note 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; route changes are attributable to a versioned event without inferring hidden reasoning. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Approval Evidence PacketUse when a agent session lineage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent session lineage to produce a before/after change record and impact map for the run-lineage record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Closeout Handoff LedgerUse when a agent session lineage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Completeness ReconciliationUse when the agent session lineage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Exception Triage QueueUse when the agent session lineage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Recovery Readiness DrillUse when the agent session lineage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Scenario Sensitivity MatrixUse when the agent session lineage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the run-lineage record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Scope Intake GateUse when a new agent session lineage request needs a bounded work scope to produce a scoped intake card for the run-lineage record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, a...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Source Provenance LedgerUse when a decision about agent session lineage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the run-lineage record. Success means each material claim has a source, version/date, location, and confidence note; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Agent Telemetry Session Lineage Threshold Rule CheckUse when a agent session lineage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the run-lineage record 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; each run can be linked to its task and configuration without exposing user secrets. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Approval Evidence PacketUse when a streamed-response termination evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fe...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Change Impact TraceUse when a version, rule, source, or stakeholder change may affect streamed-response termination evidence to produce a before/after change record and impact map for the partial-output state ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Closeout Handoff LedgerUse when a streamed-response termination evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Completeness ReconciliationUse when the streamed-response termination evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Exception Triage QueueUse when the streamed-response termination evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Recovery Readiness DrillUse when the streamed-response termination evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Scenario Sensitivity MatrixUse when the streamed-response termination evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the partial-output state ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Scope Intake GateUse when a new streamed-response termination evidence request needs a bounded work scope to produce a scoped intake card for the partial-output state ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Source Provenance LedgerUse when a decision about streamed-response termination evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the partial-output state ledger. Success means each material claim has a source, version/date, location, and confidence note; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Agent Telemetry Stream Termination Threshold Rule CheckUse when a streamed-response termination evidence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the partial-output state ledger 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; partial output is explicitly distinguished from a complete response or successful action. Use configured search, fetch...Votes: 0GitHub stars: 2
- Agent Telemetry Tool Event Schema Approval Evidence PacketUse when a agent tool-event schemas result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the tool-event contract 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; events distinguish requested, attempted, completed, failed, and unverified actions. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Agent Telemetry Tool Event Schema Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent tool-event schemas to produce a before/after change record and impact map for the tool-event contract. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; events distinguish requested, attempted, completed, failed, and unverified actions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Agent Telemetry Tool Event Schema Closeout Handoff LedgerUse when a agent tool-event schemas work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the tool-event contract 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; events distinguish requested, attempted, completed, failed, and unverified actions. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Agent Telemetry Tool Event Schema Completeness ReconciliationUse when the agent tool-event schemas workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the tool-event contract 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; events distinguish requested, attempted, completed, failed, and unverified actions. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Agent Telemetry Tool Event Schema Exception Triage QueueUse when the agent tool-event schemas workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the tool-event contract 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; events distinguish requested, attempted, completed, failed, and unverified actions. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2