Explore skills
Showing 50701–50730 of 77079 skills
Use 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 install or run third-party commands without authorization.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, and completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 scope, and completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, and completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, task transitions, tool scope, and completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 scope, and completion evidence. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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; do not install or run third-party commands without authorization.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 identity, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 identity, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 identity, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 bounded to model weight identity, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 identity, precision, sequence and batch settings, accelerator memory, and runtime overhead. Use only authorized local evidence, version-matched authoritative references, and synthetic or approved fixtures. Do not install tools, expose credentials, change live systems, publish, contact people, or make irreversible decisions without explicit approval; stop when authority or recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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 irreversible writes.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse 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.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when implementing a neural-network model, training loop, inference component, or learning algorithm to define tensor shapes, data provenance, objective, and evaluation before training; verify numerical behavior on small reproducible cases before using larger or sensitive datasets. Trigger for architecture, gradient, optimizer, or model-serving work.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when multiple bounded workers produce overlapping files or findings to create or update a merged manifest of artifact, owner, source, changed paths, and checks. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: every accepted artifact has one accountable owner and a verified merge result. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a multi-part task cannot finish every component in one run to create or update a status matrix with dependencies and evidence per subgoal. Use the configured search, fetch, read, browser, and test capabilities only when available and authorized. Success criterion: the final status names completed, blocked, and unverified parts without contradiction. Preserve evidence and a run record, limit rework to three meaningful passes, and obtain approval before externally visible or irreversible writes.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodex