Borrowing it
Nothing to install: this file belongs to WaniWani-AI/sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WaniWani-AI/sdk/main/.agents/skills/project-update/SKILL.mdgit clone --depth 1 https://github.com/WaniWani-AI/sdkWrote 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.
[](https://agentmods.dev/skills/waniwani-ai/sdk/project-update)<a href="https://agentmods.dev/skills/waniwani-ai/sdk/project-update"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/project-update/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.
<a href="https://agentmods.dev/skills/waniwani-ai/sdk/project-update"><img src="https://agentmods.dev/badge/skills/waniwani-ai/sdk/project-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.02299 |
| Opus 5 | $0.00039 | $0.01149 |
| Sonnet 5 | $0.00015 | $0.00460 |
| Haiku 4.5 | $0.00008 | $0.00230 |
Grade A, and why
project-update 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Update
Post concise, non-technical status updates on Linear projects and keep ticket/project statuses in sync. The audience is non-technical teams (business, customer success, leadership) who need to understand where things stand without engineering jargon.
What This Skill Does
- Gathers recent activity from multiple sources (git, Linear, Granola meetings, user context)
- For each active project, drafts a short product-oriented status update (1-3 sentences)
- Detects stale ticket/project statuses and proposes corrections
- After user validation, posts updates to Linear and applies status changes
Nothing is posted or changed without explicit user approval.
Output Style
The team uses plain, conversational status updates. Match this tone — no bullet points, no markdown headers, no emojis. Just a few sentences that answer: what happened, where is it heading, any blockers.
Examples that match the team's tone:
Still in progress, working on last UX quirks. Targeting May 15th for pushing this to prod on the client side
The client has submitted the app for review on ChatGPT on May 8th Waiting on the review to be approved or rejected
We are super blocked on this one because the client says the technical API documentation isn't ready, and the person responsible on their side is short on capacity.
Key principles:
- Product language, not engineering language ("user flow is ready for testing" not "refactored the handler and merged the PR")
- Short — 1 to 3 sentences max per project
- Mention concrete next steps or blockers when relevant
- Use real dates, client names, and feature names — be specific
- Health status:
onTrack,atRisk, oroffTrack
WaniWani Product Repos
When matching project work to git, activity is read entirely through gh against these repos on GitHub (github.com/WaniWani-AI) — never from local clones:
| GitHub repo | What it is |
|---|---|
| WaniWani-AI/app | Main application |
| WaniWani-AI/sdk | @waniwani/sdk |
| WaniWani-AI/website | Marketing site |
| WaniWani-AI/cli | @waniwani/cli |
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.
- 9d ago First seen · 164 lines · 77 tokens per session scan A 265741ebf44e
project-update is a skill published in the GitHub repository WaniWani-AI/sdk (17 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 2,299 once invoked, about $0.0004 per session on Opus 5. 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-08-30.
Other skills, from other repositories
onplana-project-planner
Turn a goal or a brief into an executable Onplana plan over its MCP server: write a plan.md and attach it to the project, decompose it into tasks and subtasks, set start/due dates and dependencies, assign owners, add test cases as you go, and create tasks for the downstream surfaces a change ripples to. Use this…
onplana-autonomous-agent
Work autonomously on projects in Onplana over its MCP server: pick up the open tasks in a project, do the work, keep each task's status current, report progress as comments, file an Issue when something is wrong, and poll for human replies. Use this whenever an agent (Claude Code, ChatGPT / Codex, or claude.ai) is…
development-orchestration
Compose Herdr tools and domain Skills into dependency-aware development lanes with explicit ownership, validation, and safe worktree/workspace reclamation.
sdlc-review
Review Kanban handoffs and route verified outcomes.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…