Run any Skill in Manus with one click

status

Stars0

Forks0

UpdatedJune 10, 2026 at 21:09

Produce a tight 4-section status update (What happened / What's next / What I recommend / What I need from you), 1-3 sentences each. Use when the user says "give me an update", "status", "where are we", "sitrep", "recap", "summarize the situation", or invokes `/status`. Skip any section that's genuinely empty rather than padding it.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

itsHabib

itsHabib/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	status
description	Produce a tight 4-section status update (What happened / What's next / What I recommend / What I need from you), 1-3 sentences each. Use when the user says "give me an update", "status", "where are we", "sitrep", "recap", "summarize the situation", or invokes `/status`. Skip any section that's genuinely empty rather than padding it.
user_invocable	true

Status update

Output four sections, in this order, with these exact headers. Hard cap: 1-3 sentences per section.

What happened

Concrete outcomes since the last update or session start — shipped / merged / blocked. PR numbers, SHAs, file paths welcome. No process narration ("I tried X then Y") — just results.

What's next

The 1-2 immediate moves in priority order. Not a backlog dump.

What I recommend

One specific recommendation + the reason in one phrase. No hedging. If genuinely no preference, say "no strong rec" and move on.

What I need from you

Concrete asks only ("dashboard error", "yes/no on X"). If nothing's blocking: write "nothing — keep moving" and stop.

Rules

1-3 sentences per section is a hard cap. If it won't fit, the framing is wrong, not the cap.
Skip empty sections (no "N/A" padding).
Write to the operator, not about the work. No "we" / "us".
File paths / PR numbers / SHAs welcome. Adjectives and adverbs aren't.
No emoji unless the operator's explicit style demands it.

More from this repository

same repository

floor

itsHabib/skills

Render the EFFECTIVE Claude Code harness rulebook for this machine/project — what the current session may actually do — by merging every settings layer (global ~/.claude/settings.json, project .claude/settings.json, project settings.local.json) plus PreToolUse/PostToolUse hooks into one tiered view (free / consequential / guarded), flagging cross-shell asymmetries (a Bash rule with no PowerShell twin), wildcards that undo curated per-verb rules, and denies shadowed by allows. Use when you ask "what am I allowed to do", "what's my floor", "show the effective permissions", "render my rulebook", "why did that prompt", "audit my settings", "what's changed in my permissions", or invoke /floor. Read-only — it never edits settings.

2026-07-200

health

itsHabib/skills

Sign-on tool-health board — reads the workbench friction log and rolls it up per tool into a "how's each tool doing" view (recent friction, worst severity, one-line pain), using a LOCAL model (free, offline). Use when the operator asks "how are my tools doing", "tool health", "what's the friction", "how's everything doing", "anything need attention", "are my tools ok", or invokes /health, especially at sign-on. Distinct from /wip (in-flight work right now) and /status (session recap) — this is standing tool *health* from accumulated friction.

2026-07-090

offload

itsHabib/skills

Offload a cheap, verifiable sub-task to the LOCAL model (Ollama, $0, offline) via the `local` CLI — narrow a big file list, extract structure from noisy tool output, classify log lines or command success/failure. Use PROACTIVELY mid-task when a sub-step is mechanical narrowing/extraction/shallow-classification AND you can verify the result at a glance; also when the operator says "offload that", "run that locally", "use the local model", or invokes /offload. NEVER for deep judgment (code review, risk calls, dense-diff reasoning) — that stays with you.

2026-07-090

voice-learn

itsHabib/skills

Build and mine a corpus of AI-draft → operator-final pairs so the agent's writing converges on the operator's real voice. Two verbs — capture (freeze the AI version of a draft BEFORE the operator edits it) and learn (diff the operator's final against the frozen AI version, classify every edit as voice vs content, and fold recurring voice edits into voice-profile.md and tellscan.mjs as dated, evidence-backed rules). Use when the operator says "voice learn", "capture this draft", "here's my final version, learn from it", "diff my edits", "store this pair", "learn my voice", or invokes /voice-learn. Corpus lives under a writing dir you configure (e.g. ~/writing/corpus/); the voice profile stays the single contract.

2026-07-090

transfer-context

itsHabib/skills

Fork a thread that came up mid-task into its own briefed Claude Code session — without derailing the agent that's currently working. The source agent pauses just long enough to emit a thread-scoped context packet, spins a chip seeded with it, and resumes its main task untouched. The chip becomes a fresh session you can question about that one thread. Use when the user says "transfer context", "pull on that thread", "fork this thread off", "spin that tangent into its own session", "hand this thread to another agent", "don't derail — chip that thread with context", or invokes `/transfer-context`. Distinct from /chip (fires off a TASK, and explicitly avoids conversation-dependent context) and /continue (hands off the WHOLE session). This is thread-scoped, conversation-dependent, and non-disruptive to the source.

2026-07-090

skills

itsHabib/skills

Skill librarian - catalog every skill available in this session and recommend the best fit for a task. Discovers all skills on disk (personal ~/.claude/skills, project .claude/skills, and skills stranded in .claude/worktrees) by reading their frontmatter, so the catalog is always current. Run alone (/skills) for a grouped tabular overview of everything you have; run with a prompt (/skills open a pull request for my changes) to rank the catalog against that task and recommend the top matches with the exact command to type. Use when the operator asks "what skills do I have", "which skills are available", "what can I run", "is there a skill for X", "which skill should I use for Y", "recommend a skill", "I forget what skills I built", "what's available to me", or invokes /skills.

2026-07-090

name	status
description	Produce a tight 4-section status update (What happened / What's next / What I recommend / What I need from you), 1-3 sentences each. Use when the user says "give me an update", "status", "where are we", "sitrep", "recap", "summarize the situation", or invokes `/status`. Skip any section that's genuinely empty rather than padding it.
user_invocable	true

Status update

Output four sections, in this order, with these exact headers. Hard cap: 1-3 sentences per section.

What happened

Concrete outcomes since the last update or session start — shipped / merged / blocked. PR numbers, SHAs, file paths welcome. No process narration ("I tried X then Y") — just results.

What's next

The 1-2 immediate moves in priority order. Not a backlog dump.

What I recommend

One specific recommendation + the reason in one phrase. No hedging. If genuinely no preference, say "no strong rec" and move on.

What I need from you

Concrete asks only ("dashboard error", "yes/no on X"). If nothing's blocking: write "nothing — keep moving" and stop.

Rules

1-3 sentences per section is a hard cap. If it won't fit, the framing is wrong, not the cap.
Skip empty sections (no "N/A" padding).
Write to the operator, not about the work. No "we" / "us".
File paths / PR numbers / SHAs welcome. Adjectives and adverbs aren't.
No emoji unless the operator's explicit style demands it.