agentleFS
denismrvoljakdenismrvoljak/claude-scholar/.claude/skills/status/SKILL.md

status

Skill1 starsChanged 3 months agoMITView on GitHub

Show a progress dashboard for the document. Use when the user wants to see overall progress, character counts, section status, or how much is left. Triggers on "how far along", "what's done", "show progress", "how many characters", "status".

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 6 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • MistralSkill

    import

    Import the user's setup from other coding CLIs (Claude Code, Codex, OpenCode) into Vibe — instructions, skills, subagents, commands, hooks, MCP servers, permissions, and plugins. Load when the user wants to switch to Vibe, import or reuse another CLI's configuration, or asks whether a file from another CLI works in Vibe.

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • VercelSkill

    next

    Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.

    Also in 11 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 157 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep it short. This is a glance, not a review — if something looks wrong, say which command to run next.

    line 42
  2. Distinctive:

    Do not edit any files. This skill is read-only.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 157 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/status — Where the document stands

Steps

  1. Measure each section in sections/: wc -m for characters and wc -w for words, and classify the file as empty, outline, drafted, or reviewed by reading it. A file of headings with no prose is an outline, not a draft.

    These counts are a planning estimate, not the submitted figure. wc -m includes markdown syntax that will not survive compiling, and excludes the fixed per-image allowance most institutions charge for a pasted figure. Say so when the total gets close to the limit, and point at docs/COMPILING.md — the authoritative count comes from the compiled document, and it needs checking well before the deadline rather than on submission day.

  2. Read the budgets from .claude/rules/structure.md and the hard limit from docs/requirements.md.
  3. Build the dashboard.
## Progress — <date>

| Section | Status | Chars | Budget | % |
|---------|--------|------:|-------:|--:|
| ... | | | | |
| **Total** | | | | |

Figures: N at <cost> each = <total> chars against the limit
Remaining budget: <chars>   (estimate — the real count comes from the compiled document)

## Material
Theoretical sources: N · Practical sources: N · Research logs: N · Verified reference list: yes/no

## Plans
Sections with a plan: N/M. Without: <list>

## Recently touched
<Files modified in the last week, with dates.>
  1. Flag what needs attention, in order of urgency: sections over budget, the total against the limit, sections with content but no citations, sections with no plan and no draft, and anything untouched for a long time while its deadline approaches.

Keep it short. This is a glance, not a review — if something looks wrong, say which command to run next.

Do not edit any files. This skill is read-only.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.