TritonAI Skills Library

A skill gives your AI assistant instructions for a particular task, such as checking a document for accessibility or finding a saved project decision. This library explains what each skill can help you do and gives you a request to try.

How skills help with your request

Check that the skill is available. Open your AI workspace and ask, “Which skills can I use here?” Some skills need a particular app, connected service, or local setup.
Describe what you want to do. Try an example below and provide the file or context the agent needs. The Harness can select an installed, enabled skill when your request and conversation context match what it does. You can also name a skill to direct the agent, but that is usually optional.
Review the result. Ask which checks it completed and what still needs your attention. A skill can guide the work; it does not grant access to accounts or services.

Looking for Outlook or Google Drive connections? Explore TritonAI Harness plugins, then try the guided Harness exercises.

9skills to explore
TritonAImaintained
Automatedsource refresh

Live from UCSD/UCSD-Skills-Library. Synced at commit 43bc2695a2bf, committed 2026-08-10.

Available now

Find a skill for the work in front of you

Choose a task below, then try the example request in an AI workspace where the skill is available.

TritonAI maintained

Review code changes

Check changes to a software project for bugs and test failures before sharing them with others.

Try asking

Review the changes in this project, run the relevant tests, and explain any problems you find.

What you’ll get: A summary of the checks, confirmed problems, and fixes made or still needed. You decide when the changes are ready to release.

Before you start: Open the software project you want reviewed. The skill uses the project's review tools when available, or performs a structured review.

Code review

Technical details

Skill name: tritonai-autoreview

Use for TritonAI Harness or UCSD AI Tools code-review closeout before commit, pull request update, merge, release, or ship. Trigger when the user says use tritonai-autoreview, run TritonAI autoreview, autoreview this, auto review, Codex review, second-model review, review this branch, review this PR, review this commit, before merge, before ship, closeout review, run tests plus review, or fix accepted review findings.

Supporting files: Self-contained

tritonai/tritonai-autoreview

Browse source files

Read instructions

TritonAI maintained

Report a problem or suggest an improvement

Turn a problem or idea into a clear message for the TritonAI team.

Try asking

Draft feedback about this issue: my task stopped before creating the file I requested. Help me explain what happened and what I expected.

What you’ll get: A short email draft with a subject, the problem, and useful context. You review it before anything is sent.

Before you start: Describe what happened. If an email-sending tool is unavailable, you receive a draft you can send yourself.

Feedback

Technical details

Skill name: tritonai-feedback

Use when a user wants to send feedback, bug reports, support requests, improvement ideas, or agent-experience notes to the TritonAI team. Trigger on explicit requests such as /tritonai, /feedback, /feed-back, /feed back, TritonAI feedback, email TritonAI, report this to TritonAI, or send this to tritonai@ucsd.edu.

Supporting files: Self-contained

tritonai/tritonai-feedback

Browse source files

Read instructions

TritonAI maintained

Understand your Harness setup

Get help understanding your current Harness settings and investigating setup problems.

Try asking

Check which model my Harness session is using and which skills are available. Explain what you can confirm and what you cannot check.

What you’ll get: An explanation based on the setup it can inspect, with any missing information identified. Settings stay unchanged unless you request a change.

Before you start: Use this with the Harness environment you want checked. A project folder alone may not reveal the running app's settings.

Harness help

Technical details

Skill name: tritonai-harness-config

Investigate and explain the live TritonAI Harness environment using sanitized runtime and source evidence. Use for Harness config files, CODEX_HOME or TRITONAI_HOME, permissions or sandbox modes, models and providers, skills, logs, installation paths, or comparisons with personal Codex or Codex Desktop. Also use for explicit T3 Code or t3code configuration/runtime questions, Harness-versus-T3 Code comparisons, or questions about a t3code identifier in a Harness diagnostic; not unrelated source-code mentions.

Supporting files: Self-contained

tritonai/tritonai-harness-config

Browse source files

Read instructions

TritonAI maintained

Check content for accessibility

Find accessibility issues in documents, presentations, and webpages, and get help fixing them.

Try asking

Review this workshop handout for accessibility. Check its headings, links, and image descriptions, then explain what needs fixing.

What you’ll get: Specific issues and suggested fixes, plus checks that still need a person. The review helps improve the content; it does not certify compliance.

Before you start: Provide the file or page you want reviewed and tell the agent who will use it.

Accessibility

Technical details

Skill name: ucsd-accessibility-compliance

Use for UC San Diego digital accessibility work across websites, web apps, Campus CMS or Simple Sites pages, LMS content, forms, documents, PDFs, presentations, email campaigns, social posts, images, graphics, audio, and video. Helps implement, audit, or remediate content against official UCSD accessibility guidance, UCSD Digital Accessibility Standards, WCAG 2.1 AA expectations, ADA Title II and UC policy context, keyboard and screen-reader usability, semantic HTML, forms, contrast, alt text, captions, transcripts, accessible documents, and practical manual review steps. Trigger on /ucsd-accessibility, accessibility review, a11y, WCAG, ADA Title II, Siteimprove, screen reader, keyboard access, alt text, captions, transcripts, PDF remediation, or "is this accessible at UCSD".

Supporting files: 1 reference

tritonai/ucsd-accessibility-compliance

Browse source files

Read instructions

TritonAI maintained

Get help with the campus website editor

Get guidance for editing a UC San Diego website in Cascade, the campus content management system.

Try asking

Walk me through updating an existing department page in Cascade. Explain how to preview it and check headings and links before publication.

What you’ll get: Steps grounded in UC San Diego's CMS training, with guidance on what to review before publishing.

Before you start: You need the appropriate CMS access to make changes. The skill provides guidance; installing it does not connect your agent to Cascade.

Website editing

Technical details

Skill name: ucsd-cms

Use when authoring, editing, publishing, or reviewing content on a UC San Diego website running on Hannon Hill Cascade CMS (Blink, department sites, *.ucsd.edu sites managed in the campus CMS) — to follow the correct workflow, pick the right template/module, write valid metadata, meet accessibility and SEO requirements, and publish safely. Trigger when the user mentions Cascade, Blink, "the CMS", a `.ucsd.edu` page, templates, modules, drawers, tabs, metadata, display names, system names, SiteImprove, publish/unpublish, or asks "how do I add/edit/publish a page", "what template should I use", "why is my page not showing", "how do I get CMS access". Also /ucsd-cms.

Supporting files: Self-contained

tritonai/ucsd-cms

Browse source files

Read instructions

TritonAI maintained

Understand how to handle your data

Identify how sensitive the information in a planned project may be and which handling requirements to check.

Try asking

Review this proposed workshop signup form using only its field names. Explain the likely UC Protection Levels and which handling questions need a campus decision.

What you’ll get: An initial classification with reasons, relevant handling requirements, and questions for the responsible campus owner. This does not approve a storage service or use of the data.

Before you start: Start with a description or sample field names. You do not need to provide real personal records for this example.

Data handling

Technical details

Skill name: ucsd-data-classification

Use when building or reviewing a UC San Diego application, automation, script, database, API, or data pipeline that stores, transmits, logs, or displays data — to classify that data under UC's IS-3 Protection Levels (P1–P4) and apply the handling controls each level requires. Trigger when defining data models or database schemas, choosing where to store data, writing logging, building forms or endpoints that collect personal/financial/health/student data, or whenever fields like SSN, credit card, PHI, FERPA student records, passwords, API keys, or other PII appear. Also /ucsd-data-classification, "classify this data", "what protection level", "can I store this", "is this allowed at UCSD".

Supporting files: 3 references

tritonai/ucsd-data-classification

Browse source files

Read instructions

TritonAI maintained

Follow UC San Diego webpage standards

Help a website developer keep a page consistent with UC San Diego's standard layout and navigation.

Try asking

Review the department webpage source in this project. Check that it follows the UC San Diego template and identify any changes needed.

What you’ll get: A review of the page source against the campus template, with specific corrections and checks for the developer to follow.

Before you start: This is for work on website source files. Provide the project and its UC San Diego template files; CMS editors can use the campus website editor skill.

Website development

Technical details

Skill name: ucsd-decorator

Build and edit UC San Diego web pages on the Decorator 5 design system without damaging the page chrome. Use when working on any ucsd.edu site, campus page shell, Decorator template, or kitchen-sink component — and specifically when a task touches the header, navbar, mobile offcanvas drawer, search forms, footer, or an embedded UCSD widget. Enforces one writable canvas, a pinned source of truth for markup, and a CI-checkable chrome contract.

Supporting files: 8 references

tritonai/ucsd-decorator

Browse source files

Read instructions

TritonAI maintained

Find and reuse saved project notes

Look up earlier decisions and keep useful notes for future work with your AI assistant.

Try asking

Find our saved decisions about the workshop agenda. Summarize what we agreed, cite the notes, and flag anything that may be out of date.

What you’ll get: A summary tied to the notes it found, with gaps and uncertainty identified. You can also ask it to save or correct a specific note.

Before you start: Requires an existing local memory folder. It searches saved material; email and calendar access require their own connections and permission.

Project memory

Technical details

Skill name: ucsd-memory

Use and maintain an existing local TritonAI memory vault. Trigger on $memory, remember this, forget this, search memory, what do we know about, summarize this into memory, memory status, or requests to add, update, remove, query, or cite Obsidian-style TritonAI memory notes.

Supporting files: Self-contained

tritonai/ucsd-memory

Browse source files

Read instructions

TritonAI maintained

Set up project memory

Create a place on your computer to keep project notes and decisions for later conversations.

Try asking

Set up a local memory folder for my workshop planning. Show me where the notes will live and ask before enabling background updates or importing connected sources.

What you’ll get: An organized memory folder with starter files and instructions for using it. Background updates and connected sources need your approval.

Before you start: Choose a local folder. If you already have project memory, ask the agent to inspect it before creating another setup.

Project memory

Technical details

Skill name: ucsd-memory-create

Create and maintain a local TritonAI memory vault. Use when a user asks for $memory-create, memory setup, an Obsidian-style memory graph, daily conversation sync, weekly memory cleanup, or cross-platform background memory jobs for TritonAI Harness.

Supporting files: 1 reference · 2 assets

tritonai/ucsd-memory-create

Browse source files

Read instructions

Make a skill available

First ask your agent whether the named skill is available in your current workspace. If it is missing, follow the setup instructions for your agent. TritonAI Harness users can start with access and setup.

Manual installation for other compatible agents

Clone the source repository, then copy an individual skill directory from tritonai/ into the skills directory used by your agent.

git clone https://github.com/UCSD/UCSD-Skills-Library.git
mkdir -p ~/.agents/skills
cp -R UCSD-Skills-Library/tritonai/skill-name ~/.agents/skills/

Review the skill and its supporting files before installation. The public library excludes restricted operational procedures and credentials.

Read the repository instructions