AgentEra

Minimal guidance-only Skill used by release-pinned compatibility examples.

Use for portfolio-facing stock risk briefs that separate market facts, interpretation, and non-investment-advice boundaries.

Use for market-entry or go-to-market memos that combine CRM evidence, competitive signals, and executive decision needs.

Use for concise business travel plans that combine policy constraints, local route facts, and traveler priorities.

Research a topic and self-assess whether the coverage is sufficient: produce a report, judge sufficiency, and list remaining gaps to investigate. Use for adaptive/agentic research and iterative investigation.

Produce a deep, structured research report on a topic: decompose into key dimensions, analyze each with evidence and reasoning, synthesize cross-cutting insights, and surface open questions. Use for deep research, analysis, and literature/landscape reviews.

Audit a vendor agreement or contract: extract key clauses, check that required clause categories are present, flag compliance gaps and risks, and emit a structured audit summary. Use for compliance, contract review, audit, and vendor agreement requests.

Analyze an infrastructure incident alert and produce a structured response plan plus an executable on-call runbook. Use for incident, alert, on-call, and runbook requests.

Build complex agent and intelligent system services with Agently (Model control + TriggerFlow).

Agent setup, prompt layering, routing, and info injection patterns.

FastAPI service wrappers for Agently Agent + TriggerFlow (POST, SSE, WebSocket).

Translate LangChain/LangGraph patterns into Agently code (model control + TriggerFlow).

Structured output patterns with ensure_keys, ordering, and instant streaming.

Streaming outputs, runtime streams, and ReAct-style tool loops.

Event-driven TriggerFlow orchestration patterns and branching.

Use when the user wants to build, initialize, validate, optimize, or refactor a model-powered assistant, internal tool, automation, evaluator, or workflow from a business scenario or common problem statement, including project-structure refactors or starter skeletons that may separate model setup, prompt config, and orchestration, even if the request also mentions a UI, app shell, or local model service such as Ollama, and it is still unclear whether the solution should stay a single request, add supporting capabilities, or become orchestration. The user does not need to mention Agently explicitly.

Use when the user is shaping Agently request-side behavior: model setup, settings files, prompt management, structured output, response reuse, streaming consumption, session memory, embeddings, knowledge-base indexing, retrieval, or retrieval-backed answers within one request family.

Use when the user needs Agently TaskDAG / Dynamic Task, model-generated or app-submitted DAG planning, TaskDAG validation, TaskDAGResolver handlers, TaskDAGExecutor execution, or the Agently.create_dynamic_task compatibility facade. TaskDAG is the DAG foundation capability; Dynamic Task is the convenience facade over it and uses TriggerFlow as the execution substrate.

Use when the user needs workflow orchestration such as branching, concurrency, approvals, waiting and resume, runtime stream, restart-safe execution, mixed sync/async function or module orchestration, event-driven fan-out, process-clarity refactors that make stages explicit, performance-oriented refactors that collapse split requests, or workflow definitions and chunk-level runtime metadata that must stay visible for debugging and visualization. The user does not need to say TriggerFlow explicitly.

Use when the user wants Agently runtime extension capabilities: Action Runtime, built-in action packages, legacy tool compatibility, MCP access, ExecutionResource lifecycle, FastAPIHelper or streaming API exposure, auto-function helpers, KeyWaiter, or optional agently-devtools observation, evaluation, and playground integration.

Use when the user wants to migrate an existing LangChain, LangGraph, LlamaIndex, CrewAI, or similar system into Agently, including choosing whether the source belongs to request/agent-side Agently behavior or TriggerFlow orchestration.