agentera/agently-session-memory
skills/agently-session-memory/SKILL.md
Use when the user needs conversation continuity, memo, or restore-after-restart behavior for a request family, including session ids, chat history, request-side memory boundaries, and session-backed continuity.
$ install --global
skillsauthnpx skillsauth add agentera/agently-skills agently-session-memoryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
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
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 27, 2026, 3:24 AM135.2s4 files scanned
SKILL.md
- name:
- agently-session-memory
- description:
- Use when the user needs conversation continuity, memo, or restore-after-restart behavior for a request family, including session ids, chat history, request-side memory boundaries, and session-backed continuity.
Agently Session Memory
Use this skill when the request path already exists but continuity or restore behavior is the main design problem.
Native-First Rules
- prefer Session-backed continuity before inventing a custom memory layer
- keep request-side chat history and memo boundaries explicit
- separate request memory from workflow runtime state
Anti-Patterns
- do not use session as a substitute for workflow orchestration state
- do not keep restart-sensitive memory only in transient globals
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