SW

    storyledger word count

    1

    Word counts per chapter, progress toward your target, and a writing log you own. Counts only prose, never frontmatter or notes, and keeps planned chapters separate.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more
    SW

    storyledger word count

    Example session with this skill installed

    Show me the word count for my manuscript in the /chapters folder and log today's progress. My target is 80,000 words.

    • Read your context and instructions
    • Compiled the storyledger word count

    I have analyzed the 12 files in your /chapters folder. I also created a new progress/log.yml file with your 80,000-word target and recorded today's entry.

    Manuscript Progress Report

    ChapterStatusWords
    ch1-intro.mddrafted2,450
    ch2-inciting-incident.mddrafted3,120
    ch3-rising-action.mddrafted1,890
    ch4-the-turn.mdplanned0
    Totals11 Files7,460

    Progress Details

    • Target: 80,000 words (9.3% complete)
    • Daily Streak: 1 day
    • 7-Day Average: 1,065 words/day
    • Projection: Approximately 68 days to target at current pace

    Log Update
    Today's count of 7,460 total words has been appended to progress/log.yml.

    Next steps

    • Add status: planned to any new outline files to keep them out of your drafted totals.
    • Run this command again tomorrow to update your writing streak and 7-day average.
    • View the full history in progress/log.yml at any time.
    ch1-intro.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing word counts across dozens of chapter files is a manual chore that distracts from drafting. This skill automates manuscript tracking by parsing your chapter files, calculating progress against a target, and maintaining a flat-file writing log.

    What it does

    • Chapterized counting parses individual files to provide word counts per chapter while ignoring frontmatter and markup.
    • Status filtering distinguishes between drafted prose and planned chapters or outlines based on file metadata.
    • Progress tracking calculates the percentage of completion against a user-defined target word count.
    • Velocity analysis computes writing streaks and average daily word gains over 7-day and 30-day windows.
    • Automated logging generates and appends daily progress entries to a version-controlled YAML log file.

    How it works

    1. Source identification detects manuscript files in folders like chapters/ or manuscript/ using Markdown or text formats.
    2. Analysis execution runs a Node.js script to extract word counts, excluding non-prose elements like HTML comments and scene markers.
    3. Data reporting generates a table showing chapter lengths, total drafted words, current streak, and projected completion dates.
    4. Log updates appends or replaces the daily entry in progress/log.yml when prompted to record writing progress.

    Frameworks & tools

    This tool requires Node 18 or later for the core analysis script. It operates on plain text files, specifically Markdown and .txt, and manages data via a log.yml file using a standardized workspace format.

    Why this beats prompting it yourself

    Generic prompts often include notes, outlines, and frontmatter in the total count, leading to inflated progress reports. This skill uses a dedicated parser to ensure only actual prose is counted and maintains a persistent, queryable history of your writing pace that survives chat session resets.

    Use cases

    • Generate a per-chapter breakdown of a full-length novel manuscript.
    • Monitor a writing streak and daily word count velocity during challenges like NaNoWriMo.
    • Estimate the number of days until a draft is finished based on recent output.
    • Maintain a portable writing log that stays inside your project repository.

    Known limitations

    Does not natively support .docx or .pdf files without conversion to text. Requires Node.js to be available in the environment for precise counting.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    Requires Node 18+ for script execution. Only reads .md and .txt files. Cannot edit log entries older than the current date.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    • Free with an Agensi account

    Nothing to install. It runs in your AI agent.

    Optional
    Node.js 18+

    Skill estimates without the node helper app.

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    *txt
    *.md
    progress/**
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    The skill uses a dedicated parser that excludes frontmatter, HTML comments, scene markers, and outline notes, ensuring your progress reflects actual prose rather than meta-data or world-building notes.

    The tool is designed for plain-text environments and currently supports Markdown (.md) and text (.txt) files; it does not natively parse proprietary formats like .docx or .pdf.

    You will receive the core analysis script, the configuration schema for your YAML log, and the integration instructions to connect the tool to your AI agent's workspace.

    Yes, since the skill maintains a portable `log.yml` file within your project directory, your writing history and velocity data remain intact even if you start a new chat session or switch AI agents.

    The skill requires a Node.js environment (v18+) to run the analysis script and works best with AI agents that have access to a local or cloud-based file system to read your manuscript folders.

    Free