dennisonbertram/agent-university-skill · Archived

agent-university

Connect to and use the Agent University hosted MCP server — evidence-backed knowledge (build guides, gotchas, recipes, code samples) for building with LLM-tooling targets.

First seen Jul 18, 2026

Installation

$ npx skills add dennisonbertram/agent-university-skill --skill agent-university

Summary

  • Connect to and use the Agent University hosted MCP server — evidence-backed knowledge (build guides, gotchas, recipes, code samples) for building with LLM-tooling targets.
  • Use when building with a tool, SDK, or API covered by an Agent University degree, when you need a step-by-step build guide grounded in live-verified evidence, or when debugging a platform-specific error.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,246 B
  • docs SUMMARY.md 401 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Agent University MCP Server

Agent University is a knowledge corpus built from real, live-verified builds ("degrees") of LLM-tooling targets — SDKs, APIs, CLIs, and cloud services. Every artifact carries an evidence tier and a source citation back to the build that produced it. The corpus is served by a hosted MCP server.

Requirements

  • An Agent University API key in the AGENTUNIVERSITYAPI_KEY environment

variable. The server rejects unauthenticated requests. Keys are issued by the maintainer — request one via an issue on this repo.

Register the server

Claude Code:

claude mcp add --transport http agent-university \
  https://agent-university-api-production.up.railway.app/v1/mcp \
  --header "Authorization: Bearer ${AGENT_UNIVERSITY_API_KEY}"

Any other MCP client (streamable HTTP):

{
  "url": "https://agent-university-api-production.up.railway.app/v1/mcp",
  "headers": { "Authorization": "Bearer <AGENT_UNIVERSITY_API_KEY>" }
}

How to use the tools

Building with a covered target? Call agentuniversityhowtobuild FIRST. It returns the complete, ordered build guide assembled from how the target was actually built and verified — verbatim source content with citations, not search snippets.

Knowledge tools:

Tool When to use
agentuniversityhowtobuild First call for any "how do I build X" task — full ordered guide.
agentuniversitysearch General queries; supports target/degree/artifact/evidence filters.
agentuniversityplan_build Planning context: recipes, gotchas, instructions for a target.
agentuniversityget_gotchas Before writing code against a target — known traps, live-verified.
agentuniversityget_recipe Working recipes for a target or degree.
agentuniversitydebug_error Hit a platform-specific error or symptom — search known fixes.
agentuniversityget_artifact Fetch a full artifact by ID (from search results).
agentuniversitygetcodesample Fetch a code sample by ID with source citation.
agentuniversitygetdegreestatus Degree metadata for a target.

Ops tools (agentuniversityops*: deployment, checks, freshness, probe, metrics, events, runbooks, runbook, errorcatalog) report on the hosted API itself — corpus version, health checks, retrieval mode, error-code handling. Use them to verify the server is current before trusting results, or when a call fails: opsfreshness answers "is the corpus live and current?" in one call; opserror_catalog says whether an error is retryable.

Recommended flow: howtobuild (or search) → getgotchas before coding → debugerror when something breaks. Prefer artifacts marked with higher evidence tiers (e.g. live_verified) when results conflict.