agentera/agently-langchain-to-agently
skills/agently-langchain-to-agently/SKILL.md
Use when a migration is already known to stay on the LangChain agent side, including agent setup, tools, structured output, retrieval, and short-term memory.
$ install --global
skillsauthnpx skillsauth add agentera/agently-skills agently-langchain-to-agentlyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
70%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 27, 2026, 3:06 AM182.6s4 files scanned
SKILL.md
- name:
- agently-langchain-to-agently
- description:
- Use when a migration is already known to stay on the LangChain agent side, including agent setup, tools, structured output, retrieval, and short-term memory.
LangChain To Agently
Use this skill after migration ownership is already confirmed to be LangChain agent-side work.
Native-First Rules
- map source LangChain behavior to existing Agently capability surfaces
- keep migration focused on request-side and agent-side behavior
- escalate to TriggerFlow only when the source design truly depends on orchestration semantics
Anti-Patterns
- do not treat every LangChain migration as a workflow migration
- do not preserve old abstractions when Agently already has a direct native surface
Read Next
references/overview.md
Related Skills
agentera/agently-dynamic-task
development
VerifiedTrustedCommunity
Use when the user needs Agently Dynamic Task, model-generated or app-submitted DAG planning, TaskDAG validation, DynamicTaskResolver handlers, or TaskDAGExecutor execution through Agently.create_dynamic_task. Dynamic Task is a first-class Agently API that uses TriggerFlow as an execution substrate.
9SKILL.mdUpdated May 21, 2026
agentera/agently-runtime
tools
VerifiedTrustedCommunity
Use when the user wants Agently runtime extension capabilities: Action Runtime, built-in action packages, legacy tool compatibility, MCP access, Execution Environment lifecycle, FastAPIHelper or streaming API exposure, auto-function helpers, KeyWaiter, or optional agently-devtools observation, evaluation, and playground integration.
9SKILL.mdUpdated May 17, 2026
agentera/agently-request
development
VerifiedTrustedCommunity
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.
9SKILL.mdUpdated May 17, 2026
agentera/agently-triggerflow
development
VerifiedTrustedCommunity
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.
9SKILL.mdUpdated Mar 26, 2026