make-tex-docstring
Skill4 starsChanged 4 months agoMITView on GitHub
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.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bib-auditSkill
- bootstrap-dispatcher-runtimeSkill
- ci-debugSkill
- cloud-filesSkill
- connect-googleSkill
- daily-planSkill
- distill-to-ruttersSkill
- email-clientSkill
- email-triageSkill
- find-handoff-candidatesSkill
- formal-prose-reviewSkill
- get-weatherSkill
- git-workflowSkill
- hook-makerSkill
- initialize-tddSkill
- install-launchersSkill
- latex-workshopSkill
- list-managerSkill
- llm-wakeupSkill
- loose-modeSkill
- math-dependency-graphSkill
- milestone-loggingSkill
- node-certifySkill
- node-driftSkill
- notation-reviewSkill
- online-calendarSkill
- pdf-to-markdownSkill
- prepare-handoffSkill
- proof-auditSkill
- recurring-tasksSkill
- refactor-nodeSkill
- regenerate-blueprintsSkill
- relocate-nodesSkill
- semantic-integrationSkill
- send-feedbackSkill
- setup-interface-managerSkill
- skill-makerSkill
- technical-flow-reviewSkill
- tight-modeSkill
- tool-applicabilitySkill
- update-standardsSkill
- using-compassSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When this skill is used, begin with:
- Distinctive: line 20
Use this skill when a document-oriented task needs profile information and the source file does not already state it clearly near the top.
- Distinctive: line 25
Use that generated standard view as the canonical profile and TeX block format.
- Distinctive: line 26
Do not create alternate schema variants here.
- Distinctive: line 32
If important items cannot be inferred safely, ask the user.
- Distinctive: line 36
Before proposing a new block, check whether the document already has a suitable top-of-document profile comment.
- Distinctive: line 39
do not replace it mechanically
- Distinctive: line 40
only suggest revisions if information is missing, unclear, or inconsistent
- Distinctive: line 49
Keep the answer concise.
- Distinctive: line 55
ask before inserting or editing the file
- Distinctive: line 62
create multiple schema variants across different documents
≈ “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.
Files
<!-- 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: ExploreSkill: make-tex-docstring
Keep the answer concise.
By default:
- state whether a suitable docstring already exists
- identify any missing or unclear fields
- propose a canonical comment block
- 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
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
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.