Agent Skills for OSU

Includes OSU API skill for fetching public data from The Ohio State University Content APIs (content.osu.edu) and (optionally) running an MCP server that exposes the same data as tools.

What’s included

• OSU API Skill: ohio-state-api/
  • Instructions: ohio-state-api/SKILL.md
  • Direct HTTP helper: ohio-state-api/scripts/osu-fetch.mjs
  • Endpoint reference: ohio-state-api/references/endpoints.md
  • Bundled MCP server source: ohio-state-api/mcp-server/

Quick start (direct HTTP)

Fetch OSU dining locations:

node ohio-state-api/scripts/osu-fetch.mjs --service dining --path /locations

Fetch by full URL:

node ohio-state-api/scripts/osu-fetch.mjs https://content.osu.edu/v2/api/v1/dining/locations

Add query params (repeatable):

node ohio-state-api/scripts/osu-fetch.mjs --service buildings --path /buildings --param q=union

MCP server (optional)

Build the bundled MCP server:

cd ohio-state-api/mcp-server
npm install
npm run build

Then configure your MCP client to run:

• command: node
• args: ["/ABSOLUTE/PATH/TO/ohio-state-api/mcp-server/build/index.js"]

Tool definitions live under ohio-state-api/mcp-server/src/.

Installing as a skill

How you “install” depends on your agent:

• If your agent scans a skills directory, copy or symlink ohio-state-api/ into that directory.
• If your agent supports adding skills by path, point it at ohio-state-api/SKILL.md.

Troubleshooting

• Could not resolve host / fetch failed: your environment likely has no outbound DNS/internet access.
• Unexpected 404s: ensure you’re using the correct base URL; osu-fetch.mjs treats --path as relative to the service base (leading / is fine).