Menu
SkillsMP has collected 8 skills from AgentEra/Agently-Skills. Open a skill to review its source and details.
Showing 8 of 8 collected skills.
Use for Agently request-side setup and contracts: model settings, Prompt/input/output design, effect tuning, missing or redundant context, structured output, response reuse, streaming, session memory, embeddings, and retrieval within one request family.…
Use to design, understand, tune, or audit a non-trivial Agently model workflow: model-node responsibilities, input/output completeness, data-flow correctness or redundancy, model-versus-Host/workflow ownership, topology, evidence, lifecycle, concurrency, or…
Use when a model-powered product, assistant, automation, evaluator, or workflow request still needs the right Agently owner, execution shape, or project boundary chosen. Also use for explicit low-frequency TaskDAG or DynamicTask requests.
Use when a business metric comparison must be written from structured evidence with explicit evidence references and limitations.
Use when migrating an existing LangChain, LangGraph, LlamaIndex, or CrewAI system into Agently and mapping each source behavior to its actual request, runtime, context/storage, or TriggerFlow owner.
Use for Agently runtime extension surfaces: Actions and MCP, ExecutionResource lifecycle, TaskWorkspace file capabilities, RecordStore durability, auto_func and KeyWaiter helpers, FastAPIHelper transport, or optional agently-devtools observation and…
Use for Agently-Stage process-local task lifetime and sync/async interop: Stage scopes and handles, settlement/cancellation, StageCallBridge and StageStream, Tunnel replay channels, or local EventEmitter listeners. Choose this even inside TriggerFlow when a…
Use when developer-owned execution needs inspectable branching, concurrency, joins, waits, approval, retry, runtime streams, pause/resume, recovery, or mixed sync/async orchestration. Use agently-stage instead when a provider-owned sync wrapper only bridges…