Skip to content
Back to skills

Agent Core

ASecurity

"Routes local OpenHands SDK agent construction, LLM configuration,

  • 247 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
toolsgoshellapi

Works with

  • api
  • mcp

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill agent-core --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agent Core?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agent Core
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-agent-core-488dfa2c/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-agent-core-488dfa2c)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: agent-core
description: "Routes local OpenHands SDK agent construction, LLM configuration,
  conversation lifecycle, callbacks, persistence, interruption, condensation,
  and title-generation workflows."
disable-model-invocation: true
metadata:
  disco-role: operating
license: MIT
---

# Agent Core

Use this sub-skill for the local SDK path: creating `LLM`, `Agent`, `Conversation`, `LocalConversation`, `RemoteConversation`, and `AgentContext` objects; configuring callbacks, tokens, tags, persistence, interrupts, condensation, and model/provider behavior; and understanding how conversations move through the SDK.

## What this route owns

- `LLM` construction, provider selection, and model settings.
- `Agent` creation and tool lists, including `mcp_config`, `system_prompt`, `condenser`, and `critic`.
- `Conversation` factory routing to `LocalConversation` or `RemoteConversation`.
- Conversation callbacks, token callbacks, `ConversationState`, persistence, tags, and observability metadata.
- Interrupt and pause behavior, condensation recovery, title generation, and async/sync parity.

## Start here

Read [`references/api-reference.md`](references/api-reference.md) for the concrete constructor signatures and major attributes. Read [`references/workflows.md`](references/workflows.md) for common local and remote conversation flows. Read [`references/troubleshooting.md`](references/troubleshooting.md) when a conversation fails, pauses unexpectedly, or runs with the wrong model/provider.

## Typical triggers

- "Create an agent that edits files and runs shell commands."
- "Use a local conversation with custom callbacks."
- "Why did the run pause or get interrupted?"
- "How do I attach persistence, tags, or a custom condenser?"
- "How do I generate or rename a conversation title?"

## Cross-links

- For skill loading, plugins, hooks, MCP, and secrets, go to [`../extensions/SKILL.md`](../extensions/SKILL.md).
- For built-in tool names, registration, and presets, go to [`../built-in-tools/SKILL.md`](../built-in-tools/SKILL.md).
- For remote workspace and agent-server transport details, go to [`../remote-runtime/SKILL.md`](../remote-runtime/SKILL.md).

## Minimum workflow

1. Choose a model and build `LLM`.
2. Build an `Agent` with the desired tools, skills, and optional MCP or condenser settings.
3. Create a `Conversation` with a local path or `Workspace`.
4. Add callbacks or tags if the use case needs observability.
5. Call `send_message()` and `run()` or use the async methods in a matching async flow.
6. Use `interrupt()`/`close()`/persistence APIs when the conversation must stop or resume later.

## Do not bury these details here

- Full API tables belong in `references/api-reference.md`.
- End-to-end examples belong in `references/workflows.md`.
- Error handling and recovery belong in `references/troubleshooting.md`.

Files in this skill

  • SKILL.md2.8 KB
  • references/api-reference.md2.2 KB
  • references/troubleshooting.md1.1 KB
  • references/workflows.md1.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.