Story Skills

Workflow permissions are limited to read access, and the repository explains the external effects of publishing and draft automation. Drafts go through pull requests, and the docs disclose API key use, public Pages exposure, and release verification, supporting full marks for data flow and external effects. Deductions: the supplied material does not establish confirmation rules for every skill's file writes or external actions, nor consistent handling of sensitive manuscript data across integrations. Rollback relies mainly on ordinary Git workflows, with no dedicated recovery process shown. Package authorship and license are clear, but publisher identity is unverified and ongoing maintenance responsibility is only lightly specified.

The README, package metadata, and workflows consistently describe the markdown project, CLI, and skills, and provide CI, example validation, regression cases, and cross-platform checks. Deductions: this evidence cannot establish that the reviewed revision actually ran successfully; the no-runtime-dependency claim is supported by package metadata, but installation still involves Bun, Node, installers, or external build tools; examples show readable errors, but general install and skill failure handling is not covered in the supplied material.

The materials address fiction writers, list scenarios from premise through publication, support multiple Agent environments, languages, and output formats, and distinguish deterministic CLI maintenance from creative skills. Deduction: skill triggers are mostly described through example prompts, with little systematic guidance on boundary conflicts or false triggers.

The documentation index, project layout, installation steps, command reference, example projects, development guide, security policy, and MIT license have clear entry points. Deductions: the materials are insufficient to verify naming stability across long-term releases; limitations such as the Node requirement, scripts, and private Pages are mentioned but do not form a comprehensive limitation list; a version and changelog entry point exist, but actual change records were not supplied; the security reporting path is clear, while the ongoing maintenance commitment is limited.

The skill catalogue, project templates, continuity-check example, and export formats describe usable outputs; structured state and deterministic CLI checks offer a concrete benefit for long-form continuity. Deductions: there is no independent evidence quantifying time saved or quality gains, and the full workflow requires installing the CLI, maintaining frontmatter, and learning the project format, which adds ordinary-use cost.

The README provides concrete CLI output, test files show assertions in related areas, CI lists validation steps, and the security policy describes release verification, making key claims traceable to source files. Deductions: the supplied README, tests, and workflows cannot independently confirm released artifacts or execution of this revision; product claims and facts verifiable from the supplied files have some distinguishable clues, but are not consistently labeled.