Agentseek Lifecycle logo

Agentseek Lifecycle

Organization
ob-labs
agentseek-lifecycle

Use when helping with AgentSeek-managed projects or AgentSeek-compatible templates: create projects, diagnose lifecycle issues, run doctor/dev/info/task commands, edit lifecycle specs, or maintain Cookiecutter template inputs. Prefer public AgentSeek CLI and template contracts.

Overview

Publisherob-labs
Repositoryagentseek
Skill nameagentseek-lifecycle
Stars
202
Forks
30
Bundled files
3
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.

  • 3 bundled files

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

  • Open source

    Published by ob-labs on GitHub. Read the source before you install it.

Installation

Install the Agentseek Lifecycle 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/ob-labs/agentseek/tree/main/src/skills/agentseek-lifecycle
  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/ob-labs/agentseek.git /tmp/agentseek
mkdir -p .claude/skills
cp -r /tmp/agentseek/src/skills/agentseek-lifecycle .claude/skills/agentseek-lifecycle
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agentseek Lifecycle 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 Agentseek Lifecycle 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 Agentseek Lifecycle 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.

AgentSeek Lifecycle

Core Workflow

  1. Identify the workspace shape:
    • Generated project: look for .agentseek/lifecycle.toml, .env.example, pyproject.toml, frontend files, and project README.
    • Template project: look for cookiecutter.json, rendered {{ cookiecutter... }} paths, generated lifecycle specs, and template README.
  2. Work through the public lifecycle surface:
    • agentseek create
    • agentseek doctor
    • agentseek dev
    • agentseek info
    • agentseek task
  3. Treat .agentseek/lifecycle.toml as the compatibility contract between a generated project and AgentSeek.
  4. Keep changes narrow:
    • Update generated instructions when lifecycle behavior changes.
    • Preserve non-interactive template rendering.
    • Use AgentSeek commands and project files as the validation surface.
  5. Validate with public commands whenever possible.

Load References

  • For lifecycle specs, task expectations, and public validation commands, read references/agentseek-lifecycle.md.
  • For template variables, rendering, --no-input, private variables, hooks, and template maintenance, read references/cookiecutter.md.

Default Validation

For a generated project:

bash
agentseek info
agentseek doctor
agentseek dev --dry-run
agentseek task --list

For a template project, render with defaults into a temporary directory, then run the generated project's lifecycle checks:

bash
tmpdir="$(mktemp -d)"
cd "$tmpdir"
agentseek create <type>/<name> --no-input
cd <generated-project>
agentseek info
agentseek doctor
agentseek dev --dry-run

If the template lives on a branch that is not the template repository's default branch, pass the branch explicitly:

bash
agentseek create <type>/<name> --checkout <branch> --no-input

If the repository provides its own test or lint commands, run the smallest relevant set after the public lifecycle check.

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 Agentseek Lifecycle AI skill do?

Use when helping with AgentSeek-managed projects or AgentSeek-compatible templates: create projects, diagnose lifecycle issues, run doctor/dev/info/task commands, edit lifecycle specs, or maintain Cookiecutter template inputs. Prefer public AgentSeek CLI and template contracts.

Why use Agentseek Lifecycle on TypingMind?

Because you install it once and use it with any model. Agentseek Lifecycle 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 Agentseek Lifecycle in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ob-labs/agentseek/tree/main/src/skills/agentseek-lifecycle. 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 Agentseek Lifecycle?

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 Agentseek Lifecycle?

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

Is the Agentseek Lifecycle AI skill free?

Yes. It is published on GitHub by ob-labs 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 👇