Challenge Baseline Model
AgibotTech/genie_sim
Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…
Post project updates to team chat, gather feedback, triage responses, and plan next steps.
Install Team Update
$ npx skills add jezweb/claude-skills --skill team-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jezweb/claude-skills team-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .claude/skills/team-update && rm -rf skills-srcUse ~/.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/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .claude/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jezweb/claude-skills --skill team-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jezweb/claude-skills team-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .agents/skills/team-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .agents/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill team-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jezweb/claude-skills team-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .cursor/skills/team-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .cursor/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jezweb/claude-skills.git --path plugins/dev-tools/skills/team-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jezweb/claude-skills --skill team-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jezweb/claude-skills team-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .gemini/skills/team-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .gemini/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jezweb/claude-skills team-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jezweb/claude-skills --skill team-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .github/skills/team-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .github/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill team-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jezweb/claude-skills team-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/dev-tools/skills/team-update .opencode/skills/team-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-update" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/dev-tools/skills/team-update into .opencode/skills/team-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-update- GitHub stars
- 1.1k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,062 words
- Files
- 5 (incl. references)
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post project updates to team chat, gather feedback, triage responses, and plan next steps.
- Works in 5 steps: Playbook Check → Gather Context → Draft and Post Update → …
- With team update
- SKILL.md covers The Playbook Pattern, Phase 0: Playbook Check, Phase 0b: Discovery (First Run… and Phase 1: Gather Context, plus 7 more sections
- Calls git
What it does
Team Update is an agent skill from jezweb/claude-skills. Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/discovery-patterns.md`, `references/feedback-triage.md` and `references/message-composition.md`). Compatibility notes: claude-code-only
It sits in Productivity & Automation, covering Meeting notes and agendas. It works with Git. The repository describes itself as: Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.
When your agent uses it
- With team update
- Check team chat
- What did the team say
Example prompts
- “team update”
- “post update”
- “sync with team”
- “/team-update”
Requirements
- Compatibility (from SKILL.md): claude-code-only
- Pre-approved tools (allowed-tools): *
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 64965d9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
*
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.
Compatibility
claude-code-only
From compatibility in the SKILL.md frontmatter.
Context cost
Team Update loads about 2.3k tokens when it runs, and up to ~6.4k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 1,062 words of instructions outside code blocks.
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 jezweb/claude-skills at commit 64965d9, republished under its MIT licence (© jezweb). 1,062 words, ~2,334 tokens.
Download SKILL.mdSave it as
.claude/skills/team-update/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- team-update
- description
- Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.
- allowed-tools
- *
- compatibility
- claude-code-only
Team Update
Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available.
The Playbook Pattern
This skill uses a playbook file at .claude/team-update-playbook.md in the project root.
- First run: Discover available tools, ask the user for preferences, execute, save a playbook
- Subsequent runs: Read the playbook, skip discovery, execute directly
- User edits playbook: Changes take effect immediately (channel, style, triage rules)
The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata.
Phase 0: Playbook Check
Check if .claude/team-update-playbook.md exists in the project root.
If it exists: Read it. All tool configuration, channel info, message style, and triage rules are in there. Jump to Phase 1 with known config.
If it does not exist: Run Phase 0b (Discovery) first.
Phase 0b: Discovery (First Run Only)
Detect available capabilities by checking what MCP tools are connected and what local tools exist.
Read references/discovery-patterns.md for detection patterns.
Capability Detection
Check for each capability category:
| Capability | How to detect | Fallback if missing |
|---|---|---|
| Chat | MCP tools matching chat, slack, discord, teams | Output formatted text for manual posting |
| Git | git rev-parse --is-inside-work-tree | Skip commit summaries |
| Issues | MCP tools matching github, linear, jira | Skip or output text list |
| Tasks | MCP tools matching tasks, todos, asana | Skip or output text list |
| Knowledge | Basalt Cortex (~/Documents/basalt-cortex/) | Search for related knowledge notes |
User Preferences (Ask)
After discovery, ask the user to confirm:
- Channel: Which chat space/channel to post updates to? (List discovered options)
- Identity: Post as yourself or a bot identity? (e.g. Anthro Morphic)
- Repo scope: Which repo(s) to track? (Default: current repo)
- Message style: Brief standup, detailed changelog, or conversational update?
- Team context: Any team members to be aware of? (Names, roles)
- Triage rules: Any custom rules for handling feedback? (Or use defaults)
Save Playbook
After discovery + user preferences, save the playbook to .claude/team-update-playbook.md.
Read references/playbook-format.md for the full template. Fill in all sections with discovered tools and user preferences. If a capability was not found, note it as "Not available" in the playbook.
Ensure .claude/ is in .gitignore (the playbook contains space IDs and preferences that shouldn't be committed).
Phase 1: Gather Context
Collect information from all available sources. Use the playbook's "Data Sources" section to know which tools to call.
1a. Determine Time Window
Check the playbook's "Last Run" section for the last update timestamp. If no previous run, ask the user how far back to go (default: 24 hours).
1b. Collect Data
Gather from each available source:
| Source | What to collect | Tool |
|---|---|---|
| Git commits | git log --oneline --since=<last-update> | Bash |
| Chat messages | Messages in the configured channel since last update | Chat MCP tool from playbook |
| Open issues/PRs | Recently updated or newly created items | Issue tracker from playbook |
| Active tasks | In-progress or recently completed tasks | Task tracker from playbook |
1c. Summarise for Drafting
Group commits by theme (not individual hashes). Note any issues closed, PRs merged, or tasks completed. Flag any team messages that need response.
Phase 2: Draft and Post Update
2a. Compose Message
Read references/message-composition.md for message patterns.
Follow the playbook's "Message Style" section. General principles:
- Lead with what shipped or changed, not process
- Group related commits into themes
- Mention specific people only when relevant
- Keep it scannable (short paragraphs, bullet points)
- Write like a teammate, not an AI — no emoji spam, no hedging, no over-explaining context the team already has. See the Communication Style section in references/message-composition.md.
2b. Preview and Approval
Show the draft to the user. Include:
- The composed message
- Which channel it will be posted to
- Whether it's a new message or thread reply
APPROVAL REQUIRED: Never post to external channels without explicit user approval.
Show full SKILL.md (439 more words)Show less
2c. Post
Post the approved message using the chat tool from the playbook. If no chat tool is available, output the formatted message for the user to post manually.
2d. Update Playbook
After posting, update the "Last Run" section of the playbook with:
- Current timestamp
- Thread key (if applicable)
- Brief summary of what was posted
Phase 3: Read and Triage Feedback
3a. Read Responses
Read messages from the configured channel since the update was posted. Look for:
- Direct replies to the update
- New messages in the channel that reference the project
- Reactions or acknowledgements
3b. Classify Feedback
Read references/feedback-triage.md for classification patterns.
Use the playbook's "Triage Rules" section. Default classification:
| Type | Action |
|---|---|
| Bug report | Create issue (label: bug) |
| Feature request | Create issue (label: enhancement) |
| Question | Draft reply for user approval |
| Blocker | Flag immediately, suggest resolution |
| Acknowledgement | Note, no action needed |
| Off-topic | Ignore |
3c. Present and Act
Present a summary of feedback with proposed actions:
## Feedback Summary
- Daniel: "Can we add dark mode?" -> Create issue (enhancement)
- Rabin: "Auth is broken on staging" -> Create issue (bug, priority)
- Karen: "Looks good!" -> No action
Proceed with these actions?APPROVAL REQUIRED: Never create issues, post replies, or take external actions without explicit user approval.
Phase 4: Plan Next Steps
4a. Prioritise
From all gathered context (commits, issues, tasks, feedback), identify:
- Blockers: Things preventing progress
- High-priority: Bugs, urgent requests, deadlines
- Next up: Planned work, feature requests
- Backlog: Nice-to-haves, low-priority items
4b. Present (Not Posted)
Show the prioritised list to the user. This is for the user's planning only -- do NOT post it to any channel.
## Suggested Priorities
1. [BLOCKER] Fix auth on staging (from Rabin's feedback)
2. [HIGH] Complete API endpoint for user profiles (current sprint)
3. [NEXT] Dark mode support (from Daniel's request)
4. [BACKLOG] Refactor database queriesAutonomy Rules
| Action | Level |
|---|---|
| Read/create playbook | Just do it |
| Discover tools (first run) | Just do it, confirm preferences with user |
| Gather context (git, chat, issues) | Just do it |
| Draft update message | Just do it, show preview |
| Post to external channel | Approval required |
| Create issues/tasks | Approval required |
| Post replies to team | Approval required |
| Update playbook "Last Run" | Just do it |
| Present plan/priorities | Just do it |
Graceful Degradation
The skill works at any level of tool availability:
| Available tools | Experience |
|---|---|
| Git only | Summarise commits, output text for manual posting |
| Git + Chat | Full post/read cycle, manual issue creation |
| Git + Chat + Issues | Full cycle with automated issue creation |
| Git + Chat + Issues + Tasks + Knowledge | Full cycle with persistent tracking |
Operating Modes
The skill responds to different trigger phrases:
| Trigger | Behaviour |
|---|---|
| "team update" / "post update" | Full cycle: gather, draft, post, read feedback |
| "check team chat" / "what did the team say" | Phase 3 only: read and triage feedback |
| "standup" / "sync with team" | Phase 1 + 2: gather and post, skip feedback |
| "project update" | Phase 1 + 2 + 4: gather, post, plan (skip feedback triage) |
| "feedback loop" | Phase 3 + 4: read feedback and plan |
Reference Files
| When | Read |
|---|---|
| First run — saving playbook | references/playbook-format.md |
| First run — detecting tools | references/discovery-patterns.md |
| Composing update messages | references/message-composition.md |
| Classifying team feedback | references/feedback-triage.md |
© jezweb, 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 4 other files (references) in plugins/dev-tools/skills/team-update of jezweb/claude-skills.
- SKILL.md
- references/discovery-patterns.md
- references/feedback-triage.md
- references/message-composition.md
- references/playbook-format.md
Open the folder on GitHubat commit 64965d9
Compare with similar skills
Team Update 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Update this skilljezweb/claude-skills | 1.1k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Challenge Baseline ModelAgibotTech/genie_sim | 1.4k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| RecapSoul-Brews-Studio/arra-oracle-skills-cli | 122 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Deadline Prepdavila7/claude-code-templates | 32k | — | ~739 | Automated safety check: Pass | MIT | |
| Lark Todoautumnseasonism/lark-todo | 138 | — | ~5.5k | Automated safety check: Pass | MIT | |
| Claap Weekly RecapOthmane-Khadri/YALC-the-GTM-operating-system | 317 | — | ~5.4k | Automated safety check: Pass | MIT |
Similar skills
Recap
Soul-Brews-Studio/arra-oracle-skills-cli
Session orientation and awareness — retro summaries, handoffs, git state, focus.
Deadline Prep
davila7/claude-code-templates
Generate a structured demo outline from your session's change log and git history.
Lark Todo
autumnseasonism/lark-todo
飞书全平台待办扫描：IM 消息、会议纪要、日程、文档评论、待办审批、我发起的审批、邮件、已有任务八源并行采集，按优先级排序后支持直接处理或建任务。多企业账号自动发现并并行扫描，跨企业合并。用户说'有啥待办'、'@我的消息'、'扫一圈'、'收工检查'、'今天还差啥'、'morning standup'、'daily review' 时触发，连随口'忙不忙'、'有人找我吗'也应触发。同时覆盖多企业…
Claap Weekly Recap
Othmane-Khadri/YALC-the-GTM-operating-system
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.
Ingest
coreyhaines31/makerskills
When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into…
More from jezweb/claude-skills
All 52 skills in this repoElevenlabs Agents
jezweb/claude-skills
Build conversational AI voice agents on the ElevenLabs platform.
Favicon Gen
jezweb/claude-skills
Generate custom favicons from logos, text, or brand colours.
Tailwind Theme Builder
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
Project Health
jezweb/claude-skills
All-in-one project configuration and health management. An agent skill from jezweb/claude-skills.
Responsiveness Check
jezweb/claude-skills
Test website responsiveness across viewport widths using browser automation.
MCP Builder
jezweb/claude-skills
Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.
Related
Works with
Categories
Questions about Team Update
What does Team Update do?
Post project updates to team chat, gather feedback, triage responses, and plan next steps. Team Update is an agent skill from jezweb/claude-skills. Post project updates to team chat, gather feedback, triage responses, and plan next steps.
When should I use Team Update?
Team Update fits situations like: with team update; check team chat; what did the team say.
How do I install Team Update in Claude Code?
Run `npx skills add jezweb/claude-skills --skill team-update -a claude-code`. Or copy the skill folder (plugins/dev-tools/skills/team-update in jezweb/claude-skills) into .claude/skills/team-update in your project. Claude Code loads it when a task matches its description.
How do I install Team Update in Codex?
Run `npx skills add jezweb/claude-skills --skill team-update -a codex`. Or copy the skill folder (plugins/dev-tools/skills/team-update in jezweb/claude-skills) into .agents/skills/team-update in your project. Codex loads it when a task matches its description.
Can I use Team Update 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 jezweb/claude-skills --skill team-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-update, .gemini/skills/team-update, .github/skills/team-update and .opencode/skills/team-update in your project.
What does Team Update need to run?
Going by SKILL.md and its folder, Team Update needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: *. Compatibility (from SKILL.md): claude-code-only.
Does Team Update 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 Team Update 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 Team Update use?
Team Update 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 Team Update use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.
What are the alternatives to Team Update?
Skills that share tags, products or a category with Team Update: Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars), Recap (Soul-Brews-Studio/arra-oracle-skills-cli, 122 stars), Deadline Prep (davila7/claude-code-templates, 32k stars) and Lark Todo (autumnseasonism/lark-todo, 138 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Update?
jezweb (a GitHub user) maintains it in jezweb/claude-skills, which has 1,051 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 5, 2026.
Source: jezweb/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.