skills
AGENTS.md1 starsChanged 3 months agoApache-2.0View on GitHub
This repository publishes Agent Skills for Tines products. Keep every skill portable across Agent Skills-compatible clients unless its purpose specifically depends on a Tines product. Place each skill at skills/<skill-name>/SKILL.md. Optional agent-readable supporting files belong in scripts/, references/, or assets/ within that skill’s directory. Product-specific client metadata belongs in agents/; keep it optional so clients that do not support it can still use the skill. Follow the Agent Skills specification: Run gh skill publish --dry-run before submitting a change.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository22 other files it gives its agents.
- building-agentsSkill
- building-workflowsSkill
- claude-apiSkill
- cross-tool-researchSkill
- daily-briefingSkill
- dashboard-designSkill
- docxSkill
- frontend-designSkill
- internal-commsSkill
- mcp-builderSkill
- mcp-clientSkill
- pdfSkill
- pptxSkill
- skill-creatorSkill
- status-updateSkill
- tines-casesSkill
- tines-export-to-3bSkill
- workflow-discoverySkill
- workflow-operationsSkill
- workflow-reviewSkill
- workflow-volume-designSkill
- xlsxSkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Place each skill at skills/<skill-name>/SKILL.md.
- Very specific: line 9
Follow the Agent Skills specification:
- Distinctive: line 11
Use a lowercase, hyphenated directory name no longer than 64 characters.
- Very specific: line 13
Write a concrete description that says what the skill does and when it should trigger.
- Distinctive: line 15
Keep the body focused on instructions an agent needs after the skill triggers.
- Very specific: line 17
Put OpenAI-specific interface metadata in agents/openai.yaml, not in SKILL.md.
- Very specific: line 20
Run gh skill publish --dry-run before submitting a change.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Repository guidance
This repository publishes Agent Skills for Tines products. Keep every skill portable across Agent Skills-compatible clients unless its purpose specifically depends on a Tines product.
Skill structure
Place each skill at skills/<skill-name>/SKILL.md. Optional agent-readable supporting files belong in scripts/, references/, or assets/ within that skill’s directory. Product-specific client metadata belongs in agents/; keep it optional so clients that do not support it can still use the skill.
Follow the Agent Skills specification:
- Use a lowercase, hyphenated directory name no longer than 64 characters.
- Set the frontmatter
nameto the exact directory name. - Write a concrete
descriptionthat says what the skill does and when it should trigger. - Set
compatibilityto the intended Tines product when a skill is product-specific (for example,Tines 3B). - Keep the body focused on instructions an agent needs after the skill triggers.
- Link supporting files directly from
SKILL.mdso an agent can load them only when needed. - Put OpenAI-specific interface metadata in
agents/openai.yaml, not inSKILL.md. - Preserve copyright and modification notices in derivative skills.
Run gh skill publish --dry-run before submitting a change.
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.