agentsclimarketplace
Sign in

Make tex docstring

Skill MoeenNehzati/famulus/skills/make-tex-docstring

Use when the user asks to create or standardize a TeX document-profile comment, or when a selected TeX task requires profile information that the document does not state clearly. Do not use merely because the target is a `.tex` file.From its SKILL.md

Install
npx -y skills add MoeenNehzati/famulus --skill make-tex-docstring

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

<!-- BEGIN BLUEPRINT CONTRACT -->

Generated from blueprint.yaml. Do not edit this block by hand.

Catalog: research; topics: scholarly-documents, research-writing; visibility: listed Activation: user-request, skill-workflow; persistent modifier: no

Skill Version: 2

Uses Interfaces: none

Public Interfaces:

  • make-tex-docstring.interface.default
<!-- END BLUEPRINT CONTRACT --> <!-- BEGIN BLUEPRINT INTERFACES -->

Generated from blueprint.yaml. Do not edit this block by hand.

Instruction Interfaces:

These interfaces are documented prompt surfaces. They are not executed through dispatcher:

  • make-tex-docstring.interface.default — Inspect a TeX document against the canonical profile standard, infer cautiously, and gate any edit on approval.
<!-- END BLUEPRINT INTERFACES -->

When this skill is used, begin with:

Skill: make-tex-docstring

1. Goal

Your job is to create a short top-of-document TeX comment block that records the document profile.

Use this skill when a document-oriented task needs profile information and the source file does not already state it clearly near the top.

2. Canonical schema

Read ../../references/document-standards/document-profile.md. Use that generated standard view as the canonical profile and TeX block format. Do not create alternate schema variants here.

3. How to fill it

Identify or infer the fields from the shared schema, as reliably as possible. Infer only when the inference is reliable from the document or conversation. If important items cannot be inferred safely, ask the user.

4. Existing docstrings

Before proposing a new block, check whether the document already has a suitable top-of-document profile comment.

If it does:

  • do not replace it mechanically
  • only suggest revisions if information is missing, unclear, or inconsistent

5. Output

Start with:

  • Mode: Explore
  • Skill: make-tex-docstring

Keep the answer concise.

By default:

  1. state whether a suitable docstring already exists
  2. identify any missing or unclear fields
  3. propose a canonical comment block
  4. ask before inserting or editing the file

6. What not to do

Do not:

  • edit the file automatically
  • invent profile details that are not reasonably inferable
  • create multiple schema variants across different documents
  • turn the docstring into a long prose preface

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.