Showing 61561–61590 of 77104 skills
Use when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when several tools, designs, methods, or workflows could satisfy the same need for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a request must be converted into testable constraints and an owned decision for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when the work needs a verified goal, authorized boundary, and starting state for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a decision depends on current, source-grounded information for Human-governed agent improvement: regression-preserving upgrades for conflicting evidence. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an authorized implementation needs repeatable steps and a visible change boundary for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when several tools, designs, methods, or workflows could satisfy the same need for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a request must be converted into testable constraints and an owned decision for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when the work needs a verified goal, authorized boundary, and starting state for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a decision depends on current, source-grounded information for Human-governed agent improvement: regression-preserving upgrades for long-horizon tasks. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Persist a baseline checkpoint and a bounded change proposal; do not convert project duration into permission to alter the agent. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an authorized implementation needs repeatable steps and a visible change boundary for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when several tools, designs, methods, or workflows could satisfy the same need for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a request must be converted into testable constraints and an owned decision for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when the work needs a verified goal, authorized boundary, and starting state for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a decision depends on current, source-grounded information for Human-governed agent improvement: regression-preserving upgrades for missing acceptance criteria. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Add an explicit testable acceptance criterion and evaluator version before proposing a skill update. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an authorized implementation needs repeatable steps and a visible change boundary for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when several tools, designs, methods, or workflows could satisfy the same need for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a request must be converted into testable constraints and an owned decision for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when the work needs a verified goal, authorized boundary, and starting state for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a decision depends on current, source-grounded information for Human-governed agent improvement: regression-preserving upgrades for multi-session projects. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Store proposed lessons with source, time, confidence, and review status; never merge unreviewed session notes into active instructions. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an authorized implementation needs repeatable steps and a visible change boundary for Human-governed agent improvement: regression-preserving upgrades for parallel-work handoffs. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Provide the reviewer with the exact proposal, rationale, baseline, tests, risk, and rollback instead of delegating silent changes. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: regression-preserving upgrades for parallel-work handoffs. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Provide the reviewer with the exact proposal, rationale, baseline, tests, risk, and rollback instead of delegating silent changes. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Use when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: regression-preserving upgrades for parallel-work handoffs. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Provide the reviewer with the exact proposal, rationale, baseline, tests, risk, and rollback instead of delegating silent changes. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills