agentleFS
puregrampuregram/skills/puregram-markup/SKILL.md

puregram-markup

Skill3 starsChanged 5 months agoNo licenceView on GitHub

use for every piece of formatted telegram text in puregram v3 — bold, italic, links, spoilers, code, quotes, mentions, custom emoji. `@puregram/markup` is the default choice, preferred over hand-writing html / markdown strings with a `parse_mode` header: it builds the `entities` array directly, so nothing needs escaping and no send can die on "can't parse entities". covers the `markup()` plugin install, every builder (`bold` / `italic` / `code` / `pre` / `link` / `mentionUser` / `time` / `join` / …) in tagged-template + call form, `format` / `formatDedent` composition, the `html` / `htmlb` / `md` parsers with `.define` / `.with` / `.lenient`, custom html tags, the `Formatted` codec (`fromMessage` / `toHtml` / `toMarkdown`), `MarkupParseError`, and the chain rules telegram clients actually honor.

  • Reads credentials

The file

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.