All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Agent Coordination Review Adjudication Approval Evidence PacketUse when a multi-reviewer disagreement adjudication result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fet...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Change Impact TraceUse when a version, rule, source, or stakeholder change may affect multi-reviewer disagreement adjudication to produce a before/after change record and impact map for the reviewer disagreement ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Closeout Handoff LedgerUse when a multi-reviewer disagreement adjudication work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Completeness ReconciliationUse when the multi-reviewer disagreement adjudication workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Exception Triage QueueUse when the multi-reviewer disagreement adjudication workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Recovery Readiness DrillUse when the multi-reviewer disagreement adjudication workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Scenario Sensitivity MatrixUse when the multi-reviewer disagreement adjudication team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the reviewer disagreement ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Scope Intake GateUse when a new multi-reviewer disagreement adjudication request needs a bounded work scope to produce a scoped intake card for the reviewer disagreement ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refine...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Source Provenance LedgerUse when a decision about multi-reviewer disagreement adjudication depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the reviewer disagreement ledger. Success means each material claim has a source, version/date, location, and confidence note; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. R...Votes: 0GitHub stars: 2
- Aas Agent Coordination Review Adjudication Threshold Rule CheckUse when a multi-reviewer disagreement adjudication decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Approval Evidence PacketUse when a parallel worker file leases result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Change Impact TraceUse when a version, rule, source, or stakeholder change may affect parallel worker file leases to produce a before/after change record and impact map for the file-ownership lease map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Closeout Handoff LedgerUse when a parallel worker file leases work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Completeness ReconciliationUse when the parallel worker file leases workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Exception Triage QueueUse when the parallel worker file leases workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Recovery Readiness DrillUse when the parallel worker file leases workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Scenario Sensitivity MatrixUse when the parallel worker file leases team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the file-ownership lease map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Scope Intake GateUse when a new parallel worker file leases request needs a bounded work scope to produce a scoped intake card for the file-ownership lease map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three f...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Source Provenance LedgerUse when a decision about parallel worker file leases depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the file-ownership lease map. Success means each material claim has a source, version/date, location, and confidence note; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Aas Agent Coordination Work Lease Threshold Rule CheckUse when a parallel worker file leases decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Agent Architecture AuditUse when an agent or LLM application behaves inconsistently, misses tool calls, regresses after wrapper changes, contaminates memory, or fails between model output and UI/API delivery to trace inputs through context, planning, tools, state, recovery, and rendering; isolate the failing stage with evidence. Trigger before broad prompt rewrites or blind retries.Votes: 0GitHub stars: 2
- Agentic Code Change WorkflowUse when an agent is asked to modify code, add a feature, fix a bug, or change configuration in a repository to establish scope, inspect project conventions, plan a small change, implement with relevant tests, review the diff, and verify before reporting. Trigger for multi-file edits, behavior changes, or production-impacting fixes; gate commits and deployments separately.Votes: 0GitHub stars: 2
- Agentic Loop DesignUse when a request spans multiple actions or tool calls and needs a reliable completion condition to design a bounded agent loop connecting a clear objective to an artifact, feedback signal, allowed actions, durable progress, and stopping rules. Trigger for autonomous, recurring, or multi-turn work; use a simpler single pass for small, reversible tasks.Votes: 0GitHub stars: 2
- Agentic WorkflowsUse when a task involves authoring an agent-enabled CI or repository workflow with explicit triggers, safe outputs, and review gates 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 i...Votes: 0GitHub stars: 2
- Crewai Capability Surface MapUse when the actual capability boundary of CrewAI orchestration needs to be distinguished from assumptions. Produce a capability map for CrewAI orchestration covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to agent role boundaries, task transitions, tool scope...Votes: 0GitHub stars: 2
- Crewai Change Impact AssessmentUse when a proposed CrewAI orchestration version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for CrewAI orchestration with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to agent role boundaries, task transitions, tool sco...Votes: 0GitHub stars: 2
- Crewai Failure Triage RecordUse when a reproducible CrewAI orchestration symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for CrewAI orchestration with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to agent role boundaries, task transitions, tool scope, and completion evidence. Use only ...Votes: 0GitHub stars: 2
- Crewai Input Output ContractUse when the accepted inputs or produced outputs for CrewAI orchestration need a checkable boundary. Produce an input/output contract for CrewAI orchestration with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to agent role boundaries, task transitions, tool scope, and completion evidence. U...Votes: 0GitHub stars: 2
- Crewai Integration Parity TraceUse when CrewAI orchestration exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for CrewAI orchestration showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to agent role boundaries, task transitions, tool scope, and completion evidence. Use only authorize...Votes: 0GitHub stars: 2
- Crewai Performance EnvelopeUse when CrewAI orchestration must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for CrewAI orchestration with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to agent role boundaries, task transitions, tool scope, and completion e...Votes: 0GitHub stars: 2
- Crewai Permission Boundary ReviewUse when CrewAI orchestration may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for CrewAI orchestration showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to agent role boundaries, task transitions, tool scope, and c...Votes: 0GitHub stars: 2
- Crewai Release Handoff RecordUse when a CrewAI orchestration review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for CrewAI orchestration with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to agent role boundaries, task transitions, tool scope...Votes: 0GitHub stars: 2
- Crewai Reproducibility Fixture PlanUse when a CrewAI orchestration result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for CrewAI orchestration defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to agent role boundaries, ...Votes: 0GitHub stars: 2
- Crewai Version CompatibilityUse when a CrewAI orchestration integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for CrewAI orchestration with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to agent role boundaries, task transitions, tool ...Votes: 0GitHub stars: 2
- Custom AgentsUse when a task involves defining a specialized repository agent with a bounded role, allowed tools, context sources, and measurable output 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; d...Votes: 0GitHub stars: 2
- Failure Recovery And ReplanningUse when a tool call, test, or action fails, returns ambiguous output, or does not improve the artifact to diagnose the failure, preserve known-good state, change the next attempt, bound retries, and escalate when evidence remains insufficient. Trigger for recovery, replanning, partial completion, and repeated errors in autonomous or multi-turn workflows.Votes: 0GitHub stars: 2
- Hf Mem Capability Surface MapUse when the actual capability boundary of Hugging Face model memory estimation needs to be distinguished from assumptions. Produce a capability map for Hugging Face model memory estimation covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to model weight identi...Votes: 0GitHub stars: 2
- Hf Mem Change Impact AssessmentUse when a proposed Hugging Face model memory estimation version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Hugging Face model memory estimation with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to model weight iden...Votes: 0GitHub stars: 2
- Hf Mem Failure Triage RecordUse when a reproducible Hugging Face model memory estimation symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Hugging Face model memory estimation with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to model weight identity, precision, sequence and batch se...Votes: 0GitHub stars: 2
- Hf Mem Input Output ContractUse when the accepted inputs or produced outputs for Hugging Face model memory estimation need a checkable boundary. Produce an input/output contract for Hugging Face model memory estimation with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to model weight identity, precision, sequence and ...Votes: 0GitHub stars: 2
- Hf Mem Integration Parity TraceUse when Hugging Face model memory estimation exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Hugging Face model memory estimation showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to model weight identity, precision, sequence and batch settings, a...Votes: 0GitHub stars: 2
- Hf Mem Performance EnvelopeUse when Hugging Face model memory estimation must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Hugging Face model memory estimation with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to model weight identity, precision, seq...Votes: 0GitHub stars: 2
- Hf Mem Permission Boundary ReviewUse when Hugging Face model memory estimation may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Hugging Face model memory estimation showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to model weight identity, pre...Votes: 0GitHub stars: 2
- Hf Mem Release Handoff RecordUse when a Hugging Face model memory estimation review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Hugging Face model memory estimation with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to model weight identi...Votes: 0GitHub stars: 2
- Hf Mem Reproducibility Fixture PlanUse when a Hugging Face model memory estimation result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Hugging Face model memory estimation defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bo...Votes: 0GitHub stars: 2
- Hf Mem Version CompatibilityUse when a Hugging Face model memory estimation integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Hugging Face model memory estimation with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to model weight i...Votes: 0GitHub stars: 2
- Long Running Agent OperationsUse when operating a cloud-hosted, scheduled, or continuously running agent service beyond a single interactive session to define lifecycle controls, least-privilege scopes, budgets, observability, incident actions, and rollout gates before enabling persistent autonomy. Trigger for always-on agents, background workers, or production agent fleets.Votes: 0GitHub stars: 2
- Loop Finalization Side Effect InventoryUse when a multi-tool workflow is nearing completion to create or update a final side-effect inventory with target, status, and verification result. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: each effect is either verified, explicitly pending approval, or reported as not performed. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irrev...Votes: 0GitHub stars: 2
- Multi Agent CoordinationUse when two or more agents, subagents, or workers must contribute to a shared objective to define bounded roles, artifact ownership, interfaces, isolated work areas, message cadence, integration checks, and a responsible coordinator. Trigger for parallel research or implementation; do not parallelize tightly coupled edits without explicit ownership and merge rules.Votes: 0GitHub stars: 2
- Multi Session Project BlueprintingUse when a project is too large for one focused implementation pass and must span multiple pull requests, sessions, or collaborating agents to create a dependency-aware plan with self-contained work packets, acceptance evidence, ownership boundaries, and change-control rules. Trigger for migrations, broad refactors, multi-stage features, or context-loss-sensitive work; skip for small tasks.Votes: 0GitHub stars: 2