All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Agent Quality Route Cost Source Provenance LedgerUse when a decision about model route and cost attribution depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the route-cost reconciliation. Success means each material claim has a source, version/date, location, and confidence note; cost is attributed to the observed route and unknown usage remains explicit. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limi...Votes: 0GitHub stars: 2
- Aas Agent Quality Route Cost Threshold Rule CheckUse when a model route and cost attribution decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the route-cost reconciliation 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; cost is attributed to the observed route and unknown usage remains explicit. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Approval Evidence PacketUse when a agent session replay determinism result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent session replay determinism to produce a before/after change record and impact map for the minimized replay record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Closeout Handoff LedgerUse when a agent session replay determinism work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Completeness ReconciliationUse when the agent session replay determinism workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Exception Triage QueueUse when the agent session replay determinism workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Recovery Readiness DrillUse when the agent session replay determinism workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Scenario Sensitivity MatrixUse when the agent session replay determinism team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the minimized replay record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Scope Intake GateUse when a new agent session replay determinism request needs a bounded work scope to produce a scoped intake card for the minimized replay record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focu...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Source Provenance LedgerUse when a decision about agent session replay determinism depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the minimized replay record. Success means each material claim has a source, version/date, location, and confidence note; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Aas Agent Quality Session Replay Threshold Rule CheckUse when a agent session replay determinism decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the minimized replay 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; the declared behavior can be reproduced without replaying external side effects. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Approval Evidence PacketUse when a competing skill trigger resolution result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the trigger-collision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Change Impact TraceUse when a version, rule, source, or stakeholder change may affect competing skill trigger resolution to produce a before/after change record and impact map for the trigger-collision decision table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Closeout Handoff LedgerUse when a competing skill trigger resolution work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the trigger-collision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Completeness ReconciliationUse when the competing skill trigger resolution workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the trigger-collision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Exception Triage QueueUse when the competing skill trigger resolution workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the trigger-collision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Recovery Readiness DrillUse when the competing skill trigger resolution workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the trigger-collision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Scenario Sensitivity MatrixUse when the competing skill trigger resolution team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the trigger-collision decision table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Scope Intake GateUse when a new competing skill trigger resolution request needs a bounded work scope to produce a scoped intake card for the trigger-collision decision table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focu...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Source Provenance LedgerUse when a decision about competing skill trigger resolution depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the trigger-collision decision table. Success means each material claim has a source, version/date, location, and confidence note; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Aas Agent Quality Trigger Collision Threshold Rule CheckUse when a competing skill trigger resolution decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the trigger-collision decision 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; each conflict has a declared resolution or a user clarification path. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Agent Commit Message To Diff Consistency CheckUse when a tool-using agent prepares a commit message from a diff to create or update a message-to-file mapping with any unsupported claims removed. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every message claim has a corresponding changed path or verified behavior. 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
- Agent Loop Budgeting And ObservabilityUse when an agent loop can consume variable time, tool calls, money, tokens, or external quota to set explicit limits and progress signals, monitor them per iteration, detect churn or plateau, and stop or ask before crossing budgets. Trigger for unattended, recurring, multi-agent, or open-ended tasks where cost or runaway behavior matters.Votes: 0GitHub stars: 2
- Agent Runtime DebuggingUse when an agent run stalls, repeats tool calls, misroutes work, loses task context, or produces behavior inconsistent with its intended workflow to reconstruct the run from observable traces, test a specific failure hypothesis, and recommend a bounded recovery. Trigger for agent-runtime incidents and repeated orchestration failures, not ordinary application-code defects.Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Approval Evidence PacketUse when a agent message-to-tool correlation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent message-to-tool correlation to produce a before/after change record and impact map for the correlation map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Closeout Handoff LedgerUse when a agent message-to-tool correlation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Completeness ReconciliationUse when the agent message-to-tool correlation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Exception Triage QueueUse when the agent message-to-tool correlation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Recovery Readiness DrillUse when the agent message-to-tool correlation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Scenario Sensitivity MatrixUse when the agent message-to-tool correlation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the correlation map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Scope Intake GateUse when a new agent message-to-tool correlation request needs a bounded work scope to produce a scoped intake card for the correlation map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thre...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Source Provenance LedgerUse when a decision about agent message-to-tool correlation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the correlation map. Success means each material claim has a source, version/date, location, and confidence note; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Agent Telemetry Message Correlation Threshold Rule CheckUse when a agent message-to-tool correlation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Approval Evidence PacketUse when a agent run outcome classification result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search,...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent run outcome classification to produce a before/after change record and impact map for the outcome taxonomy and sample audit. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Closeout Handoff LedgerUse when a agent run outcome classification work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Completeness ReconciliationUse when the agent run outcome classification workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Exception Triage QueueUse when the agent run outcome classification workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Recovery Readiness DrillUse when the agent run outcome classification workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Scenario Sensitivity MatrixUse when the agent run outcome classification team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the outcome taxonomy and sample audit with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Scope Intake GateUse when a new agent run outcome classification request needs a bounded work scope to produce a scoped intake card for the outcome taxonomy and sample audit. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Source Provenance LedgerUse when a decision about agent run outcome classification depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the outcome taxonomy and sample audit. Success means each material claim has a source, version/date, location, and confidence note; classes are mutually understandable and separate model output from verified task completion. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Agent Telemetry Outcome Taxonomy Threshold Rule CheckUse when a agent run outcome classification decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. Use configured search, fe...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Approval Evidence PacketUse when a agent trace replay fixtures result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fe...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Change Impact TraceUse when a version, rule, source, or stakeholder change may affect agent trace replay fixtures to produce a before/after change record and impact map for the minimized replay fixture. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Closeout Handoff LedgerUse when a agent trace replay fixtures work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Agent Telemetry Replay Fixture Completeness ReconciliationUse when the agent trace replay fixtures workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the minimized replay fixture 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 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 Exception Triage QueueUse when the agent trace replay fixtures workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2