# 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",…

- **Type:** Skill
- **Install:** `agentstack add skill-dbalders-ucsd-skills-library-ucsd-cms`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [dbalders](https://agentstack.voostack.com/s/dbalders)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [dbalders](https://github.com/dbalders)
- **Source:** https://github.com/dbalders/UCSD-Skills-Library/tree/main/tritonai/ucsd-cms

## Install

```sh
agentstack add skill-dbalders-ucsd-skills-library-ucsd-cms
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# UCSD CMS (Hannon Hill Cascade) Authoring

Help users create, edit, publish, and maintain pages on UC San Diego websites managed
in **Hannon Hill Cascade CMS** (Blink and many `*.ucsd.edu` department sites), following
the campus authoring workflow and quality requirements.

This skill is a **navigator over the official Blink CMS training**. For step-level UI
detail, fetch the linked Blink page rather than relying on memory — Blink is the source
of truth and is updated by the campus web team.

- Training hub: 

## When to use

- Adding, editing, moving, or deleting a page or folder on a UCSD Cascade site.
- Choosing a template or module for new content.
- Writing or fixing page metadata (title, summary, display name, system name).
- Reviewing a page before publish (accessibility, SEO, links, headings).
- Publishing to stage or live, unpublishing, or rolling back a version.
- Managing site users, navigation, or QA via SiteImprove.
- Onboarding: requesting CMS training and access.

## Core terminology (quick reference)

| Term | What it is |
|---|---|
| **Site** | A collection of pages under one domain (e.g. `sitename.ucsd.edu`). |
| **Page** | One webpage within a site. |
| **System name** | Lowercase, hyphenated; determines the page's URL slug. |
| **Display name** | Metadata; determines how the page appears in navigation menus. |
| **Metadata** | Title, summary, author, display name attached to a page. |
| **Template** | Pre-built page layout selected at creation time. |
| **Module** | Reusable content block placed on a page. |
| **Drawer / Tab** | Interactive sections that reveal additional content in place. |
| **Shortlink** | Same-subdomain redirect using `go` in the URL. |
| **Vanity URL** | Separate-subdomain redirect; needs coordination. |

Full list: [Basic Terminology](https://blink.ucsd.edu/technology/websites/training/start/terminology.html).

## How to use this skill

Identify which workflow the user is in, then walk through the matching steps below. When
a step requires UI specifics, **fetch the linked Blink page** for current instructions.

### 1. Get access (first time)

1. [Training and access](https://blink.ucsd.edu/technology/websites/training/start/access/index.html) — complete required training before access is granted.
2. [Logging in](https://blink.ucsd.edu/technology/websites/training/start/login.html), [Dashboard](https://blink.ucsd.edu/technology/websites/training/start/dashboard.html), [Navigation screen](https://blink.ucsd.edu/technology/websites/training/start/navigation.html), [User settings](https://blink.ucsd.edu/technology/websites/training/start/settings.html).
3. [Roles and responsibilities](https://blink.ucsd.edu/technology/websites/training/start/roles/index.html) — confirm the user has the right role for what they're trying to do.

### 2. Create new content

1. [Plan the page](https://blink.ucsd.edu/technology/websites/training/new-page/index.html) — purpose, audience, where it lives in the site hierarchy.
2. [Add a new page or folder](https://blink.ucsd.edu/technology/websites/training/new-page/add.html), or [copy an existing one](https://blink.ucsd.edu/technology/websites/training/new-page/copy.html).
3. [Choose a template](https://blink.ucsd.edu/technology/websites/training/new-page/templates/index.html) — match the template to the page type; don't fight the template with manual formatting.
4. Set [metadata](https://blink.ucsd.edu/technology/websites/training/new-page/metadata.html): title, summary, **display name** (nav label), and a lowercase-hyphenated **system name** (URL slug).

### 3. Edit a page

1. [Editing workflow](https://blink.ucsd.edu/technology/websites/training/edit/index.html) → [edit the page](https://blink.ucsd.edu/technology/websites/training/edit/page.html).
2. Use the right primitives:
   - [Headings](https://blink.ucsd.edu/technology/websites/training/edit/headings.html) — exactly one H1, no skipped levels.
   - [Formatting](https://blink.ucsd.edu/technology/websites/training/edit/formatting.html), [Links](https://blink.ucsd.edu/technology/websites/training/edit/links.html), [Tables](https://blink.ucsd.edu/technology/websites/training/edit/tables.html).
   - [Modules](https://blink.ucsd.edu/technology/websites/training/edit/modules.html) for reusable blocks.
   - [Images](https://blink.ucsd.edu/technology/websites/training/edit/images/upload.html) and [files](https://blink.ucsd.edu/technology/websites/training/edit/files/index.html) via the [file chooser](https://blink.ucsd.edu/technology/websites/training/edit/file-chooser.html).
3. [Preview](https://blink.ucsd.edu/technology/websites/training/edit/preview.html) every change.
4. [Submit (save)](https://blink.ucsd.edu/technology/websites/training/edit/submit.html) the draft.
5. For Blink editors: review the [common revisions list](https://blink.ucsd.edu/technology/websites/training/edit/common-revisions.html) before submitting.

### 4. Publish

1. [Publish to stage or live](https://blink.ucsd.edu/technology/websites/training/publishing/index.html). **Always preview before publishing live.**
2. Mind [publishing relationships](https://blink.ucsd.edu/technology/websites/training/publishing/relationships.html) — changing a shared asset republishes everything that uses it.
3. To retire content: [unpublish](https://blink.ucsd.edu/technology/websites/training/publishing/unpublish.html) (keeps the asset) or [disable publishing](https://blink.ucsd.edu/technology/websites/training/publishing/disable.html).
4. [Publish the entire site](https://blink.ucsd.edu/technology/websites/training/publishing/site.html) only when a site-wide change requires it.

### 5. Advanced operations

[Version rollback](https://blink.ucsd.edu/technology/websites/training/advanced/versions.html) ·
[Asset audit](https://blink.ucsd.edu/technology/websites/training/advanced/audit.html) ·
[Site navigation menus](https://blink.ucsd.edu/technology/websites/training/advanced/navigation-menus.html) ·
[Reorder pages](https://blink.ucsd.edu/technology/websites/training/advanced/reorder.html) ·
[Embed video](https://blink.ucsd.edu/technology/websites/training/advanced/video.html) ·
[Move asset](https://blink.ucsd.edu/technology/websites/training/advanced/move.html) ·
[Delete asset](https://blink.ucsd.edu/technology/websites/training/advanced/delete.html) ·
[Recover deleted asset](https://blink.ucsd.edu/technology/websites/training/advanced/recover.html) ·
[Analytics](https://blink.ucsd.edu/technology/websites/training/advanced/analytics.html) ·
[Embed code](https://blink.ucsd.edu/technology/websites/training/advanced/embed.html) ·
[Kitchen Sink](https://blink.ucsd.edu/technology/websites/training/advanced/kitchen-sink.html) (all components, one page).

### 6. Manage the site

- [Add-ons & tools](https://blink.ucsd.edu/technology/websites/training/managing/index.html)
- [SiteImprove](https://blink.ucsd.edu/technology/websites/training/managing/siteimprove/index.html) — broken links, accessibility, QA monitoring.
- [Accessibility](https://blink.ucsd.edu/technology/websites/training/managing/accessibility/index.html) — site-level improvements.
- [SEO](https://blink.ucsd.edu/technology/websites/training/managing/seo/index.html)
- [Site organization](https://blink.ucsd.edu/technology/websites/training/managing/organization/index.html)
- [User management](https://blink.ucsd.edu/technology/websites/training/managing/users/index.html)
- [QA review](https://blink.ucsd.edu/technology/websites/training/managing/review/index.html)
- [AI tools](https://blink.ucsd.edu/technology/websites/training/managing/ai-tools/index.html)

### 7. Writing for the web

- [Philosophy & writing style](https://blink.ucsd.edu/technology/websites/training/writing/index.html)
- [Editorial style guide](https://blink.ucsd.edu/technology/websites/training/writing/styleguide/index.html)

## Pre-publish checklist

Before publishing live, confirm:

- [ ] **Template** matches the page type; no custom CSS hacks to fake another template.
- [ ] **System name** is lowercase, hyphenated, stable (changing it breaks the URL).
- [ ] **Display name** is short, scannable, matches site nav style.
- [ ] **Metadata** title and summary are filled in (SEO + previews depend on these).
- [ ] **Headings** start at H1, no skipped levels, structure reflects content hierarchy.
- [ ] **Links** are descriptive (no "click here"); internal links use the file chooser, not pasted URLs.
- [ ] **Images** have meaningful `alt` text; decorative images marked accordingly.
- [ ] **Tables** are used for tabular data only (not layout); have headers.
- [ ] **Files** uploaded via the file chooser; PDFs are accessible (tagged, not scanned images).
- [ ] **Previewed** in the CMS preview before submit.
- [ ] **Accessibility** — run SiteImprove or the current UCSD accessibility guidance before publishing high-traffic pages.
- [ ] **Data classification** — no P3/P4 data on a public page; use the `ucsd-data-classification` skill if installed, otherwise UC IS-3 guidance.
- [ ] **Brand & voice** — for visual/voice review, use the `ucsd-branding` skill if installed.

## Guardrails

- **Never publish without previewing first.** The CMS preview is the only reliable check.
- **Never change a system name on a live page** without a redirect plan — it breaks every link to that URL.
- **Never paste raw HTML into the editor** to bypass the template unless explicitly required and reviewed; templates encode accessibility and brand defaults.
- **Never upload images or files outside the CMS file chooser** — broken links and missing asset audit otherwise.
- **Never put P3/P4 data** (FERPA student records, PII, secrets, etc.) on a public CMS page. Use the `ucsd-data-classification` skill to assess, if installed.
- **Never disable accessibility features** (alt text, headings, tab order) to make a page look a certain way.
- **Never bulk-delete assets** without checking [publishing relationships](https://blink.ucsd.edu/technology/websites/training/publishing/relationships.html) — deletes can cascade.
- **Don't guess UI steps** — when the user needs the exact click path, fetch the matching Blink page.

## When to escalate

Route to the **campus web team / your site's CMS administrator** rather than guess when:

- The user needs a **new template, module, or site** (not authorable by editors).
- A **vanity URL** or new subdomain is needed (cross-team coordination).
- A page **won't publish** after troubleshooting, or publishing relationships are unclear.
- The user lacks the **role** required for an action.
- Content involves **regulated data** — assess with the `ucsd-data-classification` skill first, then escalate to the security office.

## Sources & currency

Current as of **2026-06-26**.

All content is mirrored from the UCSD Blink CMS training hub. Prefer fetching the
linked Blink page over relying on this skill's summaries when UI specifics matter —
Blink reflects the current Cascade version and campus policy.

- Training hub: 
- [Release notes / upgrade guide](https://blink.ucsd.edu/technology/websites/training/release-notes.html)
- [FAQ](https://blink.ucsd.edu/technology/websites/training/faq.html)
- Platform: Hannon Hill Cascade CMS (per [Basic Terminology](https://blink.ucsd.edu/technology/websites/training/start/terminology.html)).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [dbalders](https://github.com/dbalders)
- **Source:** [dbalders/UCSD-Skills-Library](https://github.com/dbalders/UCSD-Skills-Library)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-dbalders-ucsd-skills-library-ucsd-cms
- Seller: https://agentstack.voostack.com/s/dbalders
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.