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.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add MoeenNehzati/famulus --skill make-tex-docstring --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Make Tex Docstring?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/moeennehzati-make-tex-docstring)More formats (shields.io, HTML) on the badges page.
---
name: make-tex-docstring
description: >-
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.
---
<!-- BEGIN BLUEPRINT INTERFACES -->
> Generated from `blueprint.yaml`. Do not edit this block by hand.
Used Interfaces: none
<!-- 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!