Runtime Services logo

Runtime Services

Organization
VectorSpaceLab
runtime-services

Configure and troubleshoot ADK runtime services: Runner, App, sessions, memory, artifacts, plugins, telemetry, code executors, environments, event persistence, and service lifecycles.

Overview

PublisherVectorSpaceLab
RepositoryAREX-Skill
Skill nameruntime-services
Stars
341
Forks
26
Bundled files
4
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by VectorSpaceLab on GitHub. Read the source before you install it.

Installation

Install the Runtime Services AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/adk-python/sub-skills/runtime-services
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/VectorSpaceLab/AREX-Skill.git /tmp/AREX-Skill
mkdir -p .claude/skills
cp -r /tmp/AREX-Skill/skills/repositories/repo-skills/adk-python/sub-skills/runtime-services .claude/skills/runtime-services
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Runtime Services in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Runtime Services on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Runtime Services is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Runtime Services

Use this sub-skill when a task is about ADK execution services rather than agent design: Runner, InMemoryRunner, App, session persistence, memory, artifacts, plugins, telemetry, code executors, execution environments, event storage, lifecycle cleanup, or service migration cautions.

Route Here

  • Create or debug a Runner/InMemoryRunner, including run, run_async, run_live, run_debug, close, and auto_create_session behavior.
  • Choose between InMemorySessionService, SqliteSessionService, DatabaseSessionService, or cloud-backed session/memory/artifact services.
  • Explain why events, state, memory, artifacts, or live audio blobs were or were not persisted.
  • Add an app-level BasePlugin that observes model/tool/user/event callbacks while preserving runner-owned event persistence.
  • Configure OpenTelemetry/logging, TelemetryConfig, or google_adk logger behavior.
  • Attach a code executor or execution environment and assess local/container/cloud safety trade-offs.
  • Diagnose optional dependency failures such as missing SQLAlchemy for DB sessions or missing extension/cloud packages.

Route Elsewhere

Working Path

  1. Identify which service owns the symptom: runner lifecycle, session event persistence, memory ingestion/search, artifact storage, plugin callback order, telemetry export, or code execution.
  2. Confirm installation assumptions: google-adk 2.3.0, import root google.adk, Python 3.10+, and optional extras absent unless installed explicitly.
  3. Use in-memory services for focused local tests; switch to persistent services only after checking dependencies, URLs/paths, concurrency, migrations, and credential requirements.
  4. Keep event persistence runner-owned: stream events through Runner.run_async/run_live and let the configured session service append non-partial events.
  5. Close long-lived services with await runner.close() or async with Runner(...) when plugins, toolsets, or database engines need cleanup.

References And Scripts

  • API Reference: constructor signatures, core methods, imports, service contracts, optional extras, and lifecycle notes.
  • Service Patterns: safe recipes for runner setup, persistence choices, plugins, telemetry, memory/artifacts, and code execution.
  • Troubleshooting: symptom-driven fixes for DB extras, event persistence, plugin callback order, blocking tools, code executors, credentials, and migrations.
  • Runtime Services Diagnostic: safe local script that prints base runtime imports/signatures and reports optional DB-extra availability without touching databases or credentials.

Safety Defaults

  • Prefer InMemoryRunner or explicit Runner(..., session_service=InMemorySessionService()) for examples and unit tests.
  • Treat InMemorySessionService, InMemoryMemoryService, and InMemoryArtifactService as development/test services, not multi-process production stores.
  • Do not run destructive migrations or open user databases as a first diagnostic; inspect optional imports and backup plans before migration.
  • Treat UnsafeLocalCodeExecutor and LocalEnvironment as high-trust local-only surfaces because model-generated code or shell commands can affect the host.
  • Do not assume base install includes DB, extension, MCP, GCP, or cloud service dependencies.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Runtime Services AI skill do?

Configure and troubleshoot ADK runtime services: Runner, App, sessions, memory, artifacts, plugins, telemetry, code executors, environments, event persistence, and service lifecycles.

Why use Runtime Services on TypingMind?

Because you install it once and use it with any model. Runtime Services is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Runtime Services in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/VectorSpaceLab/AREX-Skill/tree/main/skills/repositories/repo-skills/adk-python/sub-skills/runtime-services. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Runtime Services?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Runtime Services?

As many as you like. As long as a model supports skills, you can use Runtime Services with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Runtime Services AI skill free?

Yes. It is published on GitHub by VectorSpaceLab under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇