claudemods
中文English

Modswriting-clearly-and-concisely

writing-clearly-and-concisely e945056ea182 Immutable snapshotLatest

Pinned to commit e945056ea1826a54351f59d85ab95b41535d8d6c, captured .

Download e945056ea182 source archive Choose something to compare with View commit on GitHub

More actions and subscriptions

All versions

Current package description (not historical)

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

Install

No verified marketplace install command.

This package is not a plugin listed in a verified marketplace. The registry has no installer of its own; download the source archive or read the usage notes in the upstream repository.

Collection warnings
  • author not declared; showing repository owner

Contents 1

Skill1
Dependencies, compatibility and skill declarations

Recorded dependencies 0

No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.

Recorded compatibility

No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.

Skill file declarations 1

The content below was read separately from the header of each skill file (SKILL.md) at its pinned commit. It is text the file declares about itself, shown as an annotation only. It is stored apart from the snapshot's dependencies and compatibility (manifest fields) above and does not overwrite them. It is not the package license, version, install count or a release record, and none of it is verified.

Evidence scope and limits
  • Each entry is one file at one pinned commit, and field states hold for that file only. Components that point to the same file are merged into one entry; files with identical content share one extraction.
  • “Declared in file” means the file's header has the field. “Not declared in this file” appears only when the header parsed successfully and lacks the field. “Invalid declaration” means the field is present but its type, length or characters do not meet the requirements; it is never rewritten or truncated. “Not read” means no usable header was obtained (not yet read, read failed, no header, or an unparseable header), which says neither that the field was declared nor that it was not.
  • Compatibility and license text are the file's own wording. They do not show that anything runs, are not legal advice, and are not a license verification. metadata.version is only an annotation inside the file; it is not the package version and is not used to judge which is newer.
  • This list groups the version's skill components by their recorded source. A listed source may still be unpinned, unread or unavailable; each entry shows its state. Collection runs in bounded batches and does not promise complete coverage.
  • A file whose read failed shows a “retry eligible” time. It is only when the collector may try again, not a schedule, and it does not promise a read or completion.

1–1 of 1 skill file sources · As of

  1. File path not recorded yet

    Not read

    Components using this file 1

    • writing-clearly-and-concisely cli-tool/components/skills/enterprise-communication/writing-clearly-and-concisely/SKILL.md

    Fields declared in the file

    Compatibility (declared in file)
    Not readNo usable header, which says neither that it was declared nor that it was not.
    License text (declared in file, unverified)
    Not readNo usable header, which says neither that it was declared nor that it was not.
    metadata.version (file annotation)
    Not readNo usable header, which says neither that it was declared nor that it was not.

    This file has no usable extraction record yet, so all three fields show as “Not read”.

    File identity
    No file identity recorded yet
    Header parse
    Not read
    Why not read
    This file has no identity record yet, and no stored read failure. source_uncollected

    No extraction record yet.

Read this page as JSON

Versions of this package1
VersionCommitCapturedComponentsActions
e945056ea182 Latest e945056 1 View Download Compare…