agentleFS
Sign inStart free
vladcheckvladcheck/agentic/skills/gost-report-rebuild/SKILL.md

gost-report-rebuild

Skill1 starsChanged 12 days agoMITView on GitHub

Use when rebuilding existing GOST 7.32 reports to DOCX/PDF with ensure_env.py and soffice. Not for new reports, non-GOST files, or DOCX editing.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use <project> as the report project root and working directory.

    line 12
  2. Very specific:

    Use <gost-report-skill> as the installed gost-report skill directory containing scripts/ensure_env.py.

    line 13
  3. Very specific:

    Read personal data from the default configuration locations ~/.config/gost-report/config and <course>/.gost-report.env.

    line 15
  4. Very specific:

    If a FAIL occurs, edit only the report source and rerun the build.

    line 26
  5. Distinctive:

    Do not use em or en dashes in prose.

    line 27
  6. Very specific:

    Create figure, table, listing, and formula handles through r.ref.* before their first citation.

    line 28
  7. Very specific:

    If the builder consumes rendered scheme figures, first re-export them from the cleaned .kicad_sch with kicad-cli sch export svg, then …

    line 34
  8. Distinctive:

    Run the conversion next to the generated DOCX, using the actual basename reported by the builder:

    line 35
  9. Very specific:

    If soffice is unavailable, report the exact error and stop.

    line 41
  10. Very specific:

    Never read or parse a .docx with the Read tool.

    line 45
  11. Very specific:

    Never modify the installed gost-report skill source.

    line 46
  12. Very specific:

    Never commit .kicad_prl or default .kicad_pro churn as design changes.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

GOST 7.32 Report Rebuild

Rebuild an existing GOST 7.32 report project reproducibly. Preserve the report builder and its conventions; change report source only to fix build failures.

Paths and inputs

  • Use <project> as the report project root and working directory.
  • Use <gost-report-skill> as the installed gost-report skill directory containing scripts/ensure_env.py.
  • Resolve figures from <project>/docs/figures/; pass bare filenames to r.figure().
  • Read personal data from the default configuration locations ~/.config/gost-report/config and <course>/.gost-report.env; never hardcode it.

Build the DOCX

  1. Set the working directory to <project> and run:

    python3 <gost-report-skill>/scripts/ensure_env.py .gost-report/build.py
  2. Require exit status 0 and a single Wrote ...docx line. Require zero FAIL entries. Accept a WARN only when it belongs to the same category as the established baseline.
  3. If a FAIL occurs, edit only the report source and rerun the build. Preserve these source conventions:
    • Do not use em or en dashes in prose.
    • Create figure, table, listing, and formula handles through r.ref.* before their first citation; do not introduce forward references.
    • Cite every r.listing in the text.
  4. Rebuild twice from unchanged source. Extract word/document.xml from each DOCX and compare its MD5 digest; the digests must match. The outer ZIP digest may differ because docProps/core.xml contains timestamps; this is expected and is not a failure.

Build the PDF

  1. If the builder consumes rendered scheme figures, first re-export them from the cleaned .kicad_sch with kicad-cli sch export svg, then convert SVG to PNG with rsvg-convert, so title and visibility changes reach the report.

  2. Run the conversion next to the generated DOCX, using the actual basename reported by the builder:

    soffice --headless --convert-to pdf "<name>.docx" --outdir .
  3. If soffice is unavailable, report the exact error and stop. Never substitute a fake PDF.

Prohibitions

  • Never read or parse a .docx with the Read tool; verify it through file size and the rebuild log only.
  • Never modify the installed gost-report skill source.
  • Never commit .kicad_prl or default .kicad_pro churn as design changes.

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.

Check your setup, free