Skip to main content
skill CX Codex

status · emotixco — Claude Code skill: what it does and how to install

The status Claude Code skill summarizes company progress from files in founder/. It runs when someone asks what has been decided, what remains open, or what skill to run next.

MIT ★ 900 updated 2026-11-03

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

What status does

The skill reads files in founder/ and presents the company’s state in a compact report. It brings together decisions from saved skill outputs, dates and their age, recorded facts, open questions, and next steps based on gaps in the folder.

It flags competitor prices, funding figures, and market numbers older than 30 days, expired metric or target dates, older files, and conflicting figures. If founder/ is missing or empty, it says so and names two skills to start with. Nothing is saved; the report reflects the files read at that moment. It also reads ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md.

What it helps with

  • summarize decisions saved across company files
  • find unanswered questions and placeholders
  • flag stale figures and expired targets
  • compare conflicting numbers across files
  • choose the next skill based on missing work

Example prompts for the agent

  • Summarize the company’s current position and what has been decided.
  • What questions are still open in the saved work?
  • Which skill should run next?

How to install status

1Skills CLI (Vercel)

npx skills add emotixco/claude-skills-founder --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 emotixco/claude-skills-founder --skill status -a claude-code. The skill file is at ~/.claude/skills/status/SKILL.md.

What does status do?

It reads founder/ and reports saved decisions, recorded facts, open questions, and stale information. It then suggests next skills based on gaps in the folder.

Which files does status read?

It reads files in founder/ and opens ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md. It does not save the report.

Source text

SKILL.md · MIT
---
name: status
description: "Read the founder/ folder and show where the company stands in one screen: what each skill decided, how old it is, which facts are recorded, what is still open, and which skill to run next. Use when a founder asks where things stand, what has been done, or what to do next."
argument-hint: "[optional: a question about the saved work]"
allowed-tools: [Read, Glob, Grep]
---

You are the person who keeps the file on this company. You know what is written down, how old it is, and what is missing.

Input: $ARGUMENTS

## Before you start

Read `${CLAUDE_PLUGIN_ROOT}/shared/conventions.md` and follow it, with one exception stated below.

- Reads: every file in `founder/`
- Needs: nothing. The folder is the input
- Saves to: nothing

This skill does not save a file. It reports the state of the folder, and a saved copy would be wrong the moment the next skill runs. Rule 4 of the conventions does not apply here. Rules 6 and 7 do: never invent a fact, a date or a number that is not in the folder.

If `founder/` does not exist or holds nothing, say so in one line, name the two skills worth running first for a founder at the start, and stop. Do not guess what the company might be.

## Instructions

### 1. The one line

Open with a single sentence that says what this company is and where it stands, built only from what the files say. If the files disagree about what the company is, say that instead.

### 2. What is written down

A table, one row per saved skill output in `founder/`, newest first. `founder/facts.md` is not a row here; section 3 covers it.

| Work | Decided | Age | The headline |
|------|---------|-----|--------------|

- **Work**: the skill that wrote it, from the file's header comment
- **Decided**: the date in that header
- **Age**: days since then, counted from today
- **The headline**: the single decision or verdict that file reached, in under 15 words, quoted or closely paraphrased from the file

### 3. The facts on record

List what `founder/facts.md` holds, grouped as the founder would think of them: what the company is, the numbers, the team, the money. Mark each one with its date.

Then, separately, list anything the folder treats as an open question, including the "Open questions" section of `facts.md` and any bracketed placeholder left in a saved file. A placeholder is a question the company has not answered yet, so name the file it sits in.

### 4. What has gone stale

Flag each of these, with the file and the date:

- Any competitor price, funding figure or market number older than 30 days, because the conventions tell the next skill to re-check those
- Any metric or target whose date has passed
- Any file older than the newest file by more than 30 days, since the later work may have moved past it
- Any place where two files state different numbers for the same thing. Quote both and say which file is newer

If nothing is stale, say so in one line rather than padding the section.

### 5. What to run next

Two or three skills, in order, each with one sentence on what it would decide and what it needs from the founder first. Base the choice on what is missing from the folder, not on a fixed sequence. If the most useful next step is a decision by the founder rather than a skill, say that instead and say what the decision is.

## Rules

- Everything here comes from the files. If the folder does not say it, it does not go in the report.
- Quote the files for verdicts and numbers rather than restating them loosely.
- Age in days, counted from today, not "recently" or "a while ago".
- If a file has no header comment, say that its date is unknown instead of guessing one.
- Keep the whole report under 600 words. It is a screen, not a document.

© emotixco · MIT · emotixco/claude-skills-founder

Similar skills

SKILL.md skills catalog →

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 api-status-communication Samuel Berthe The api-status-communication skill guides the design of external API status pages and incident updates. It helps teams publish trustworthy postmortems, SLO reports, and maintenance notices. CX Codex +1 10,400installs ev-subsidy-status NomaDamas ev-subsidy-status is a Claude Code skill that checks South Korean municipal EV subsidies, remaining funds, application status, and notices. It gives current support details before a purchase. CX Codex +1 9,500installs wiki-status Ar9av wiki-status is a Claude Code skill that reports what an Obsidian wiki has ingested, what changed since the last run, and which pages went stale. Check it before choosing to append or rebuild the vault. CX Codex +1 3,500installs 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 status-colors-and-errors dembrandt status-colors-and-errors — a skill that sets rules for semantic status colours and error copy: how many colours to keep, what each one means, and how to write a message with a way forward. CX Codex +1 1,000installs revenuecat-status RevenueCat revenuecat-status prints a status report for a RevenueCat project: apps, products, entitlements, offerings and webhooks. Useful when you need to see what is configured. CX Codex +1 992installs

From the same set14

The whole set →
validate-idea The validate-idea Claude Code skill evaluates a startup idea before development begins. It scores key business factors, suggests validation experiments, and ends with a build, pivot, or kill verdict. CX Codex +1 ★ 900repo stars user-interviews The user-interviews Claude Code skill builds customer discovery interview scripts using The Mom Test. It helps founders test product assumptions before or after building. CX Codex +1 ★ 900repo stars product-brief This Claude Code skill turns a startup concept into a structured product brief. It covers the problem, intended audience, product value, and an initial go-to-market plan. CX Codex +1 ★ 900repo stars pricing-strategy The pricing-strategy Claude Code skill develops product pricing and plan structures. It runs when a founder needs to set prices or decide what each plan includes. CX Codex +1 ★ 900repo stars pitch-deck The pitch-deck Claude Code skill outlines an investor presentation. It activates for a fundraising deck or a single slide on traction, market size, or competitors. CX Codex +1 ★ 900repo stars persona-gen The persona-gen Claude Code skill builds user personas to clarify or choose a product’s audience. It produces three profiles and a priority matrix to guide which group to build for first. CX Codex +1 ★ 900repo stars mvp-scope The mvp-scope Claude Code skill turns a feature wishlist into a focused MVP plan. It kicks in when a founder needs to choose what to build first. CX Codex +1 ★ 900repo stars metrics-dashboard The metrics-dashboard Claude Code skill selects startup metrics and builds a tracking plan. It activates when a founder asks what to measure or how to report results to investors. CX Codex +1 ★ 900repo stars

Project sponsors

Companies that keep this analytics open