Agent skill

Sc Summary

by remix-run in remix-run/react-router

Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md.

MITAuto-check passedProductivity & Automation

Install Sc Summary

skills CLI
$ npx skills add remix-run/react-router --skill sc-summary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install remix-run/react-router sc-summary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/remix-run/react-router.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sc-summary .claude/skills/sc-summary && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sc-summary
GitHub stars
57k
Token cost
~405 tokens
SKILL.md length
218 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md.

  • Works in 4 steps: Read the existing Meeting Notes entries… → Read each entire source note, especially… → Write a public-facing, high-level… → …
  • Revise Steering Committee meeting summaries
  • Calls git
  • Tasks that involve Internal communications

What it does

Sc Summary is an agent skill from remix-run/react-router. Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md. Use when asked to add or revise Steering Committee meeting summaries.

Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Productivity & Automation, covering Internal communications and Meeting notes and agendas. It works with React Router. The repository describes itself as: Declarative routing for React. The licence is MIT.

When your agent uses it

  • Revise Steering Committee meeting summaries
  • Tasks that involve Internal communications
  • Tasks that involve Meeting notes and agendas

Example prompts

  • “/sc-summary”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the existing Meeting Notes entries and list the files at the supplied location. Summarize the requested dates or files. If the user…
  2. Read each entire source note, especially the details. Resolve repeated or inconsistent points before writing. Treat proposed ideas…
  3. Write a public-facing, high-level summary of React Router discussion only. Omit unrelated conversation and banter. Refer to participants…
  4. Insert each entry near the other meeting dates, preserve unrelated content, then review the diff against the source and run git diff…

What it can do on your machine

Read from SKILL.md and the folder at commit dee9ad2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sc Summary loads about 405 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 218 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~405

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from remix-run/react-router at commit dee9ad2, republished under its MIT licence (© remix-run). 218 words, ~405 tokens.

Download SKILL.mdSave it as .claude/skills/sc-summary/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sc-summary
description
Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md. Use when asked to add or revise Steering Committee meeting summaries.

Steering Committee Meeting Summaries

Use the notes folder or files the user supplies in the request or current conversation. If no source location is available, ask for it. Write to the repository's GOVERNANCE.md, under Meeting Notes.

  1. Read the existing Meeting Notes entries and list the files at the supplied location. Summarize the requested dates or files. If the user gives no date or quantity, choose the earliest meeting without an entry and do one meeting for review. Do not duplicate an existing entry unless asked to revise it.
  2. Read each entire source note, especially the details. Resolve repeated or inconsistent points before writing. Treat proposed ideas, decisions, and suggested next steps distinctly; do not present an unconfirmed proposal as an agreed decision.
  3. Write a public-facing, high-level summary of React Router discussion only. Omit unrelated conversation and banter. Refer to participants by first name. Follow the existing <details> format and prose in GOVERNANCE.md; use short topical headings when useful. Match the depth of existing entries, adjusted to how much substantive discussion occurred.
  4. Insert each entry near the other meeting dates, preserve unrelated content, then review the diff against the source and run git diff --check. Show the new or revised entries to the user. Do not post them to GitHub, commit, or publish unless requested.

© remix-run, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/sc-summary of remix-run/react-router.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit dee9ad2

Compare with similar skills

Sc Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sc Summary compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sc Summary this skillremix-run/react-router57k—~405Automated safety check: PassMIT
Program Managerborghei/Claude-Skills891—~1.3kAutomated safety check: PassMIT
Stakeholder Commsandreaskelm/pm-brain234—~2.8kAutomated safety check: PassCustom licence
Foundation Meeting Agendaproduct-on-purpose/pm-skills716—~2.6kAutomated safety check: PassApache-2.0
Meeting Notessanqiufong/slides-from-anything1321 repos~321Automated safety check: PassApache-2.0
Pmstudio Commscoco-research/coco513—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Program Manager

    borghei/Claude-Skills

    Program management for multi-project coordination, portfolio governance, dependency tracking, benefits realization, charters, and steering-committee reporting.

    891 GitHub stars~1.3k tokensUpdated 3 days ago
    Writing & ContentAuto-check passed
  • Stakeholder Comms

    andreaskelm/pm-brain

    Write, tighten, or review written stakeholder communication: one-pagers, exec summaries, decision docs, status updates, newsletters, sprint summaries and sprint review updates, meeting agendas…

    234 GitHub stars~2.8k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Foundation Meeting Agenda

    product-on-purpose/pm-skills

    Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent.

    716 GitHub stars~2.6k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Meeting Notes

    sanqiufong/slides-from-anything

    Meeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer.

    132 GitHub starsUsed in 1 repo~321 tokens
    Productivity & AutomationAuto-check passed
  • Pmstudio Comms

    coco-research/coco

    Generate templated stakeholder communications from project context.

    513 GitHub stars~1.2k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Summarize Doc

    kbanc85/claudia

    Create an executive summary of any document at the appropriate level of detail.

    296 GitHub stars~785 tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from remix-run/react-router

  • React Router Development

    remix-run/react-router

    Guides work on React Router apps by first identifying whether the app uses Framework, Data or Declarative mode, then loading the matching reference and the installed package docs.

    57k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    Auto-check passed
  • React Router PR Finish Line

    remix-run/react-router

    Takes a blocked community pull request in React Router and adds the missing tests, change file or docs so it can merge, working on the contributor's branch.

    57k GitHub stars~1.4k tokensUpdated today
    Auto-check passed
  • React Router Bug Fix Workflow

    remix-run/react-router

    Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.

    57k GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • React Router RFC Implementer

    remix-run/react-router

    Turns a React Router RFC discussion on GitHub into an implementation, weighing community feedback and settling open questions with you before coding.

    57k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Questions about Sc Summary

What does Sc Summary do?

Summarize React Router Steering Committee meeting notes from a user-provided location in GOVERNANCE.md. Sc Summary is an agent skill from remix-run/react-router.md.

When should I use Sc Summary?

Sc Summary fits situations like: revise Steering Committee meeting summaries; tasks that involve Internal communications; tasks that involve Meeting notes and agendas.

How do I install Sc Summary in Claude Code?

Run `npx skills add remix-run/react-router --skill sc-summary -a claude-code`. Or copy the skill folder (.agents/skills/sc-summary in remix-run/react-router) into .claude/skills/sc-summary in your project. Claude Code loads it when a task matches its description.

How do I install Sc Summary in Codex?

Run `npx skills add remix-run/react-router --skill sc-summary -a codex`. Or copy the skill folder (.agents/skills/sc-summary in remix-run/react-router) into .agents/skills/sc-summary in your project. Codex loads it when a task matches its description.

Can I use Sc Summary in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add remix-run/react-router --skill sc-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sc-summary, .gemini/skills/sc-summary, .github/skills/sc-summary and .opencode/skills/sc-summary in your project.

What does Sc Summary need to run?

Going by SKILL.md and its folder, Sc Summary needs the command-line tools its instructions call (git).

Does Sc Summary access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sc Summary safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sc Summary use?

Sc Summary is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sc Summary use?

About 405 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sc Summary?

Skills that share tags, products or a category with Sc Summary: Program Manager (borghei/Claude-Skills, 891 stars), Stakeholder Comms (andreaskelm/pm-brain, 234 stars), Foundation Meeting Agenda (product-on-purpose/pm-skills, 716 stars) and Meeting Notes (sanqiufong/slides-from-anything, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sc Summary?

remix-run (a GitHub organization) maintains it in remix-run/react-router, which has 56,594 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.

Source: remix-run/react-router on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.