AI Agent Library
Platform Packs

Platform Hub

Choose the best target platform for each agent, skill, prompt system, workflow, or deployable AI asset.

Platform strategy:

Build once, package many ways. A strong agent spec can become a Custom GPT, Gemini Gem, Claude Project, static Vercel page, Notion operating doc, n8n workflow, or GitHub-managed prompt chain.

Primary Conversational Agent

ChatGPT / Custom GPTs

Best for packaged assistants with instructions, knowledge files, conversation starters, and optional actions.

  • Use for productized assistants.
  • Attach curated knowledge files.
  • Convert agent specs into instructions.
  • Add safe starter prompts and output rules.
Open Custom GPT portfolio →
Static Deployable Web Asset

Vercel

Best for static directories, calculators, landing pages, resource hubs, documentation sites, lead magnets, and product microsites.

  • Use dependency-free HTML/CSS/JS when possible.
  • Keep public resources searchable.
  • Deploy agent catalogs and knowledge directories.
  • Use vercel.json to control deployment behavior.
Open Vercel portfolio →
Workspace Knowledge System

Notion

Best for operating docs, internal databases, task queues, content calendars, partner trackers, and source-of-truth knowledge pages.

  • Use for planning and documentation.
  • Track assets, issues, partners, and campaigns.
  • Store page briefs and status tables.
  • Keep public repo content separate from private workspace notes.
Open knowledge layer →
Lightweight Assistant Packaging

Gemini Gems

Best for lightweight reusable assistant concepts that do not require a full custom app or deep repo structure.

  • Use for fast assistant packaging.
  • Keep instructions short and durable.
  • Convert top-performing GPT patterns.
  • Track inventory in the portfolio folder.
Open Gemini Gems portfolio →
Automation Workflow Engine

n8n / Workflow Automation

Best for no-code and low-code automations using triggers, webhooks, CRM updates, approval steps, and data-routing workflows.

  • Use for workflow specs and automation playbooks.
  • Define triggers and webhook payloads first.
  • Include human approval gates.
  • Separate public examples from production credentials.
Open automation KB →
Code Execution Layer

GitHub / Codex

Best for repo-managed execution: issues, branches, PRs, prompts, schemas, generated pages, reviews, and release discipline.

  • Use issue-scoped branches.
  • Keep unrelated changes out of each PR.
  • Store command/control prompts in the repo.
  • Review before merge when changing core site files.
Open contribution rules →

Platform selection matrix

Asset type Best platform Reason Repo output
Public agent directory Vercel Static, searchable, shareable, and easy to deploy. agent-catalog.html
Packaged assistant Custom GPT Best for instructions, knowledge files, and guided outputs. agents/[agent].md
Internal operating doc Notion Best for private planning, task tracking, and documentation. knowledge-base/
Automation workflow n8n Best for webhook-triggered processes and connector actions. schemas/webhook-event.schema.json
Lightweight reusable assistant Gemini Gems Best for quick assistant patterns and simple instructions. portfolio/gemini-gems/
Repo execution workflow GitHub / Codex Best for branch-scoped implementation and PR review. roadmap/, schemas/, examples/