Skip to main content
skill CX Codex

status · orwa-mahmoud — Claude Code skill: shift reports and installation

status — a skill for Claude Code reports the current shift state in a project. It runs read-only checks and starts no work.

MIT ★ 571 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add orwa-mahmoud/nightshift --skill status -a claude-code
Open on GitHub

What status does

The skill runs ns status and ns doctor to gather project state, deadlines, open items, parked decisions, snags, and other shift details. Both commands go through runtime/ns. The skill turns their results into a brief plain-language report and relays every warning from the inspectors.

It does not edit files or begin work. It leaves counts and deadlines as computed, avoids reading the lease file directly, and omits session IDs, credentials, and transcript paths. Package inventory is a separate ns inventory command, run only when the owner asks for it by name.

What it helps with

  • summarize the current shift state in a project
  • surface open items, deadlines, and parked decisions
  • relay warnings about snags and process state

Example prompts for the agent

  • Report the current shift state for this project.
  • Summarize the open items, deadline, and snags.
  • Check the shift and include every warning.

How to install status

1Skills CLI (Vercel)

npx skills add orwa-mahmoud/nightshift --skill status -a claude-code

2Manually: put the files in place

~/.claude/skills/status/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/status/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about status

How do I install status in Claude Code?

Run npx skills add orwa-mahmoud/nightshift --skill status -a claude-code. The skill file is installed at ~/.claude/skills/status/SKILL.md.

What does status do?

It runs ns status and ns doctor, then produces a short shift report. The skill is read-only and relays warnings from the inspectors.

Does status show the project's package inventory?

Package inventory is separate: ns inventory produces it only when the owner asks for it by name.

Source text

SKILL.md · MIT
---
name: status
description: Read-only shift status covering items, parked decisions, snags, the deadline and STOP or stall state; starts no work.
license: MIT
metadata:
  internal: true
---

Report the shift status for the host-opened project **without starting or changing anything** —
this is read-only. Modify no file, begin no work.

Resolve the installed plugin root to an absolute `$NIGHTSHIFT_PLUGIN_ROOT` — `${CLAUDE_PLUGIN_ROOT}`
on Claude Code, `$PLUGIN_ROOT` on Codex when set, otherwise the absolute path this skill was
attached from (`skills/status/SKILL.md`). Run every command below through
`"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns"` — native Windows: `& "$NIGHTSHIFT_PLUGIN_ROOT\runtime\windows\ns.ps1"`
in the PowerShell tool, same verbs — which resolves the host and the workspace; `ns help` lists the
verbs, and `ns bind` prints the six resolved facts (`TASK_ROOT`, `NIGHTSHIFT_WORKSPACE`, `NS`,
`NIGHTSHIFT_PLUGIN_ROOT`, `HOST`, `SOURCE`); `$NS` below is that `NS`. Never a bare relative path: the working
directory persists between calls. Each `$NS/...` path below is where the current layout keeps that file;
`ns path <key>` prints where this workspace keeps it, and `ns path --list` names every key.

## 1. Run the two read-only inspectors

```bash
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" status
"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" doctor
```

`ns status` prints every fact: workspace, schema, armed or not, item counts and the current open
item, parked entries, staged drafts and Hunt orders, recent snag dispositions, opportunity counts
and any building entry, deadline remaining, `STOP`, stall attempts, session, lease, watch reason,
work mode and target, artifact receipts, the completion record, and recent transitions. `ns doctor` adds the checks Status
cannot make safely on its own — process liveness, the lease lines, and every Warning about a path
that is not a usable file.

## 2. Render, never re-derive

Every number and every name above is already computed. Do not count boxes, subtract a deadline from
the clock, read a marker, or work out what a state means: the fact lines carry their own meaning
where there is one to carry.

Do not reimplement liveness, do not read the runtime-owned lease file directly, and never re-derive
policy precedence. The inspectors validate through the shared library, classify the recorded pid
and the watchman pid themselves, and never print a session id, a session scope, or an ownership
capability.

Write a compact, glanceable summary in plain language. Lead with what matters tonight — that is
your judgement, and the only judgement this skill asks for. What the facts say is not.

**Relay every Warning either inspector prints.** Each one is a real finding: a planted symlink
where a marker should be is not an empty night, a malformed work mode is not a working site, and a
failed clock-out is not a finished shift. Say what it means for the owner and name the confirm
action the inspector offers. Never soften a warning into silence.

Do not print a project tool's raw output, credentials, raw evidence, a session id, or a transcript
path. The inspectors do not emit them; do not go looking.

The project inventory is a separate optional report the owner asks for by name:
`"$NIGHTSHIFT_PLUGIN_ROOT/runtime/ns" inventory`. Status never prints it unasked — a table of
packages is not a glance.

© orwa-mahmoud · MIT · orwa-mahmoud/nightshift

Similar skills

All skills for Agent setup: memory, context, orchestration →

status by other authors comes first.

status official anthropics Creates case status summaries for clients, supervisors, or courts. Use it when the same case notes need a different format and level of detail. CX Codex +1 624installs status NeoLabHQ status is a Claude Code skill that reports the current state of the FPF knowledge base, including hypotheses by layer, evidence freshness, and decisions. CX Codex +1 1,200installs status backnotprop status displays work in progress as an ASCII board printed to the terminal, not a paragraph of text. Useful when you need to see multiple work streams, dependencies, and blockers at a glance. CX Codex +1 526installs status nowledge-co status — a skill for Claude Code and other agents that checks Nowledge Mem connectivity: server reachability, versions, mode. Runs after setup or when memory operations return errors. CX Codex +1 312installs status hashgraph-online status is a Claude Code skill that checks whether HOL Guard is installed and reports local protection state without changing configuration. CX Codex +1 ★ 1,118repo stars sprint-status Donchitos sprint-status reads the sprint plan and story files, then reports what is done and what is left. Useful when you need a fast read on how the sprint is going. CX Codex +1 634installs spark-recipe-shared-inbox-status readdle spark-recipe-shared-inbox-status is a Claude Code skill that reports open and completed emails, unassigned work, and assignment counts for shared inboxes. Run it to review a team’s inbox workload. CX Codex +1 356installs bm-status basicmachines-co bm-status is a Claude Code skill that checks Basic Memory's current health and configuration, including CLI access, hook queues, and recent session checkpoints. CX Codex +1 154installs conductor-status sickn33 conductor-status prints where a Conductor project stands: track progress, the phase in flight and the next task. Reads the Conductor files in your repo and builds the report in chat. CX Codex +1 ★ 50,109repo stars status-report official anthropics Generates a structured status report for leadership: KPI metrics with green/yellow/red flags, risks, and decisions needed. Turns project tracker activity into a readable narrative. CX Codex +1 3,300installs oc-status official anthropics oc-status drafts weekly status-request emails to outside counsel for active matters and saves one Markdown file per matter. It can also create Gmail drafts through an available MCP. CX Codex +1 627installs

From the same set17

The whole set →
stop A Claude Code skill pauses a Nightshift session while keeping unfinished items open. It runs when the session needs to stop immediately. CX Codex +1 ★ 571repo stars start This Claude Code skill starts a Nightshift run from the project's punch list. When the list is empty, it presents staged work for selection. CX Codex +1 ★ 571repo stars setup The setup Claude Code skill prepares Nightshift in a project and proposes quality checks through at most four questions. It creates .nightshift/ without enabling checks on its own. CX Codex +1 ★ 571repo stars schedule Prints scheduler configuration for starting a shift at a set time. It checks the Nightshift workspace and queued work before generating it. CX Codex +1 ★ 571repo stars reset The reset Claude Code skill clears damaged or confusing runtime state in an open project. It removes temporary markers and the deadline while preserving work and evidence. CX Codex +1 ★ 571repo stars quality This Claude Code skill groups project quality work into a single shift. It starts on requests about tests, accessibility, documentation, contracts, or security. CX Codex +1 ★ 571repo stars purge The purge Claude Code skill deletes Nightshift state from a project. It prints the .nightshift/ path and waits for the owner to confirm before deletion. CX Codex +1 ★ 571repo stars plan This Claude Code skill opens a planning room to explore a project and shape the work with its owner. Implementation waits until the owner deliberately leaves the room. CX Codex +1 ★ 571repo stars

Project sponsors

Companies that keep this analytics open