iainmcl/setup-project-update
claude/skills/setup-project-update/SKILL.md
Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
tools
Updated May 19, 2026
$ install --global
skillsauthnpx skillsauth add iainmcl/dotfiles setup-project-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 7:53 AM187.8s1 file scanned
SKILL.md
- name:
- setup-project-update
- description:
- Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
Setup Project Update
Create a .claude/project-update.json config file in the current repo so that the project-update skill can run without asking setup questions each time.
Step 1 — Ask for project config
Ask all of these in a single message:
- Project name — what's this project called?
- Audience & Slack channel — who receives the update and where does it get posted? (e.g. "PM lead Sarah, #product-updates")
- Sources — which of these apply? For each relevant one, ask for the detail needed:
- Git — just confirm yes/no (uses the current repo automatically)
- Jira — what's the project key? (e.g.
PAY,AUTH,TK-APP) - Slack — which channel to read? (e.g.
#payments-eng) - Notion — page URL or search term?
- docs/ — any specific path, or just
docs/?
- Standing highlights — anything to always mention or emphasise? (optional)
- Standing exclusions — anything to always leave out? (optional)
Step 2 — Write the config file
Create .claude/project-update.json at the root of the current working directory.
{
"project": "<project name>",
"audience": "<audience description>",
"channel": "<slack channel>",
"sources": {
"git": true,
"jira": "<project key or null>",
"slack": "<channel name or null>",
"notion": "<url or search term or null>",
"docs": "<path or null>"
},
"highlights": "<standing things to emphasise, or null>",
"exclusions": "<standing things to omit, or null>"
}
Omit any source key where the value would be null — keep the file clean.
Step 3 — Confirm
Tell the user:
- The config has been written to
.claude/project-update.json - They can now run
project-update(or say "write a project update") and it will skip the setup questions — only asking for the time period - They can edit the file directly anytime to change config
- Commit the file to the repo so the whole team benefits
Related Skills
iainmcl/weekly-review
development
VerifiedTrustedCommunity
Run a weekly achievement review - pulls from Jira, GitHub, and Slack to capture what you shipped in the last week, maps achievements to your 2026 goals, and appends impact-focused entries to your brag doc. Use when asked to "do a weekly review", "capture this week's wins", "update my brag doc", "what did I ship this week", "record my achievements", "what have I done this week", "add to my performance doc", or anything about tracking weekly progress, brag doc entries, or performance evidence. Trigger even if the user just says "weekly review" or "document what I did".
SKILL.mdUpdated May 19, 2026
iainmcl/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated May 19, 2026
iainmcl/sentry-fix
testing
VerifiedTrustedCommunity
Find the highest-frequency unresolved Sentry error for the VAT & Invoicing or Billing team, understand its root cause, create a Jira ticket in the APP project, implement a fix, and open a draft PR. Use when asked to "fix sentry issues", "triage sentry errors", "look at sentry", "what's broken in sentry", "create a fix for a sentry issue", or "sentry triage". Runs the full flow autonomously in the background.
SKILL.mdUpdated May 19, 2026
iainmcl/project-update
development
VerifiedTrustedCommunity
Generate a concise project status update for product managers, formatted for Slack. Use this skill when asked to write a project update, status report, sprint summary, progress briefing, or team update for PMs or stakeholders. Trigger on phrases like "write a project update", "create a status update for slack", "summarise what happened this week", "what should I tell the PM", "prepare an update for the team", "weekly update", "project status", even if the user doesn't explicitly mention Slack or PMs.
SKILL.mdUpdated May 19, 2026