agent-registry

Dynamic agent registry via js-doc-store-server. Store, version, and discover subagent definitions in a database instead of static markdown files.

Ir para a instalação

Repositório: MauricioPerera/pi-extension-data-architect
Última atividade na origem: 12 de maio de 2026 às 22:53
Idioma detectado do SKILL.md: inglês
Estrelas: 0
Forks: 0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/MauricioPerera/pi-extension-data-architect --skill agent-registry

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

flow-engine

Pi extension for workflow automation enabling resilient server startup procedures and agent-based workflow orchestration.

2026-05-13

skill-registry

Meta-skill pattern for dynamic skill discovery. Keep only ONE SKILL.md on filesystem; query all specialized skills on-demand from js-doc-store-server by tags.

2026-05-13

task-manager

Persistent task management with subagent orchestration. Create tasks, assign to agents, track execution, and build workflows via js-doc-store-server.

2026-05-12

Ver todas deste repositório

Filesystem (~/.pi/agent/agents/)
├── scout.md
├── planner.md
├── reviewer.md
└── worker.md

js-doc-store-server (localhost:3000)
└── table: agents
    ├── scout     → content: full markdown
    ├── planner   → content: full markdown
    ├── reviewer  → content: full markdown
    ├── worker    → content: full markdown
    └── custom    → user-defined agents

{
  "tableName": "agents",
  "columns": [
    { "name": "name",        "type": "text", "required": true },
    { "name": "description", "type": "text" },
    { "name": "version",     "type": "text" },
    { "name": "tags",        "type": "text" },
    { "name": "model",       "type": "text" },
    { "name": "tools",       "type": "text" },
    { "name": "content",     "type": "text", "required": true },
    { "name": "source",      "type": "text" }
  ]
}

---
name: scout
description: Fast codebase reconnaissance
tools: read, grep, find, ls, bash
model: qwen3.6:latest
---

You are a scout. Quickly investigate a codebase and return structured findings...

// 1. Discover by topic (optional)
const results = await arch_query({
  tableName: "agents",
  filter: { tags: { $regex: "review" } }
});

// 2. Register new agent from conversation
await arch_insert({
  tableName: "agents",
  data: {
    name: "security-auditor",
    description: "Audits code for security vulnerabilities",
    version: "1.0.0",
    tags: "security,audit,subagent",
    model: "qwen3.6:latest",
    tools: "read, grep, find, ls, bash",
    content: `---\nname: security-auditor\n...\n---\n\nYou are a security auditor...`,
    source: "registry"
  }
});

// 3. Verify
const all = await arch_query({ tableName: "agents", filter: {} });

Task	Tool Sequence
Discover by topic	`arch_query` → filter `tags: { $regex: "topic" }`
Load full agent	`arch_query` → filter `name: "exact-name"` → read `.content`
Register new agent	`arch_insert` into `agents` table
Update agent version	`arch_update` with `$set: { version, content }`
List all agents	`arch_query` with empty filter
Delete obsolete agent	`arch_remove` with filter `{ name: "agent-name" }`

Benefit	Explanation
Cross-machine portability	Agents follow your `js-doc-store-server`
Versioning	Field `version` tracks agent evolution
Tag Search	Find agents by topic, not just filename
Cross-session persistence	Agents survive pi restarts
Easy Registration	New agent = 1 `arch_insert` call
Centralized Source	Single `agents` table
Hybrid Fallback	Works with or without server

Issue	Consequence
Agents scattered across machines	No portability between workspaces
No versioning	Agent definitions evolve but files don't track it
No dynamic updates	Must restart pi to see new agents
No sharing	Can't reuse agent definitions across projects

Issue	Consequence
Agents scattered across machines	No portability between workspaces
No versioning	Agent definitions evolve but files don't track it
No dynamic updates	Must restart pi to see new agents
No sharing	Can't reuse agent definitions across projects

agent-registry

Opções de instalação

Revise os arquivos de origem

Agent Registry — Dynamic Agent Discovery

Problem with Static Filesystem Agents

Agent Registry — Dynamic Agent Discovery

Problem with Static Filesystem Agents

The Registry Pattern

Schema

Agent Markdown Format

How Discovery Works

Workflow: Register a New Agent

Tool Combinations for Agent Management

Server-Side Fallback

Benefits

Migration from Filesystem to Registry

See Also

name	agent-registry
version	1.0.0
tags	agents,subagent,registry,discovery,dynamic,persistence,architecture
author	MauricioPerera
description	Dynamic agent registry via js-doc-store-server. Store, version, and discover subagent definitions in a database instead of static markdown files.

agent-registry

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Agent Registry — Dynamic Agent Discovery

Problem with Static Filesystem Agents

Agent Registry — Dynamic Agent Discovery

Problem with Static Filesystem Agents

The Registry Pattern

Schema

Agent Markdown Format

How Discovery Works

Workflow: Register a New Agent

Tool Combinations for Agent Management

Server-Side Fallback

Benefits

Migration from Filesystem to Registry

See Also