calendarcn: Skill for Claude Code

.claude/skills/release/SKILL.md

release is a skill for Claude Code from vmnog/calendarcn. It costs 0 tokens per session (518 once invoked), scanned A, original, MIT.

A release checklist for preparing a web application for production, the live environment users access. It covers code checks, builds, manual checks, and accessibility.

In plain words
What is it for?
Use it to verify linting, type checks, formatting, builds, key calendar interactions, keyboard use, and responsive behavior before a release.
Why use it?
It reduces the chance of deploying broken code, missing configuration, or unusable interface features.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is vmnog/calendarcn's own configuration. It tells Claude Code how to work on calendarcn itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything calendarcn configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vmnog/calendarcn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vmnog/calendarcn/main/.claude/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/vmnog/calendarcn

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/vmnog/calendarcn/release/github.svg)](https://agentmods.dev/skills/vmnog/calendarcn/release)
Your own site
<a href="https://agentmods.dev/skills/vmnog/calendarcn/release"><img src="https://agentmods.dev/badge/skills/vmnog/calendarcn/release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/vmnog/calendarcn/release"><img src="https://agentmods.dev/badge/skills/vmnog/calendarcn/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00518
Opus 5.5 $0.00000 $0.00207
Sonnet 5.5 $0.00000 $0.00104
Haiku 4.5 $0.00000 $0.00052

Measured 28d ago against content hash 4281ca7a9399, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 28d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/release/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Skill — CalendarCN

When to Use

Invoke when preparing a new release or deploying to production.

Pre-Release Checklist

1. Code Quality

pnpm lint          # Zero warnings, zero errors
pnpm typecheck     # No type errors
pnpm format:check  # All files formatted

2. Build Verification

pnpm build         # Must complete without errors

Check for:

  • No build warnings about unused imports
  • No bundle size regressions (check .next/ output)
  • No missing environment variables

3. Manual Testing

Test the following in pnpm dev:

  • Week view renders correctly with sample events
  • Event drag works (single-day and cross-day)
  • Event resize works (top and bottom handles)
  • All-day event resize works
  • Dark mode toggle functions
  • Sidebar mini calendar navigation
  • Keyboard shortcuts: T (today), J/K (navigate weeks), / (search), Cmd+/ (shortcut help)
  • Event context menu (right-click)
  • Event detail popover (click)
  • Current time indicator visible and positioned correctly
  • Responsive behavior at different viewport sizes

4. Accessibility

  • Keyboard navigation works for event selection
  • Focus indicators visible
  • Color contrast meets WCAG AA

5. Version & Changelog

  • Update version in package.json if applicable
  • Document changes since last release
  • Tag the release in git

Deployment

CalendarCN deploys to Vercel automatically on push to main.

Vercel Deployment Checks

  • Preview deployment successful (check PR preview)
  • No new Vercel build warnings
  • Production deployment healthy after merge

Rollback Procedure

If issues found post-deploy:

  1. Revert the merge commit: git revert <commit-sha>
  2. Push to main — Vercel will auto-deploy the revert
  3. Investigate the issue on a branch
  4. Fix and re-deploy via new PR

Post-Release

  • Verify production site: https://calendarcn.vercel.app
  • Check browser console for errors
  • Test core interactions on production
  • Update any related Linear issues

Read the full file on GitHub · 82 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 28d ago First seen · 82 lines · 0 tokens per session scan A 4281ca7a9399

Subscribe to this mod's changes

release is a skill published in the GitHub repository vmnog/calendarcn (139 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.