nanoclaw-gmail: Skill for Claude Code

.claude/skills/channel-formatting/SKILL.md

channel-formatting is a skill for Claude Code from nanocoai/nanoclaw-gmail. It costs 54 tokens per session (1,023 once invoked), scanned A, a copy of channel-formatting, MIT.

A formatting helper that changes Markdown into the text style expected by WhatsApp, Telegram, Slack, and Signal. It protects code blocks from being changed.

In plain words
What is it for?
Use it when sending agent responses through WhatsApp, Telegram, Slack, or Signal so bold text, links, headings, and other styles render correctly.
Why use it?
It prevents messages from showing raw Markdown characters, such as double asterisks, when a channel uses different formatting rules.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is nanocoai/nanoclaw-gmail's own configuration. It tells Claude Code how to work on nanoclaw-gmail itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nanoclaw-gmail configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { parseSignalStyles, SignalTextStyle } from '../text-styles.js';.

Reuse

Borrowing it

Nothing to install: this file belongs to nanocoai/nanoclaw-gmail. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nanocoai/nanoclaw-gmail/main/.claude/skills/channel-formatting/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/nanocoai/nanoclaw-gmail

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for channel-formatting

README.md
[![agentmods](https://agentmods.dev/badge/skills/nanocoai/nanoclaw-gmail/channel-formatting/github.svg)](https://agentmods.dev/skills/nanocoai/nanoclaw-gmail/channel-formatting)
Your own site
<a href="https://agentmods.dev/skills/nanocoai/nanoclaw-gmail/channel-formatting"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw-gmail/channel-formatting/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for channel-formatting

Your own site · 80×15
<a href="https://agentmods.dev/skills/nanocoai/nanoclaw-gmail/channel-formatting"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw-gmail/channel-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,023 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01023
Opus 5 $0.00027 $0.00511
Sonnet 5 $0.00011 $0.00205
Haiku 4.5 $0.00005 $0.00102

Measured 9d ago against content hash f5704feec89e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

channel-formatting scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to channel-formatting — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/channel-formatting/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Channel Formatting

This skill wires channel-aware Markdown conversion into the outbound pipeline so Claude's responses render natively on each platform — no more literal **asterisks** in WhatsApp or Telegram.

Channel Transformation
WhatsApp **bold***bold*, *italic*_italic_, headings → bold, links → text (url)
Telegram same as WhatsApp, but [text](url) links are preserved (Markdown v1 renders them natively)
Slack same as WhatsApp, but links become <url|text>
Discord passthrough (Discord already renders Markdown)
Signal passthrough for parseTextStyles; parseSignalStyles in src/text-styles.ts produces plain text + native textStyle ranges for use by the Signal skill

Code blocks (fenced and inline) are always protected — their content is never transformed.

Phase 1: Pre-flight

Check if already applied

test -f src/text-styles.ts && echo "already applied" || echo "not yet applied"

If already applied, skip to Phase 3 (Verify).

Phase 2: Apply Code Changes

Ensure the upstream remote

git remote -v

If an upstream remote pointing to https://github.com/qwibitai/nanoclaw.git is missing, add it:

git remote add upstream https://github.com/qwibitai/nanoclaw.git

Merge the skill branch

git fetch upstream skill/channel-formatting
git merge upstream/skill/channel-formatting

If there are merge conflicts on package-lock.json, resolve them by accepting the incoming version and continuing:

git checkout --theirs package-lock.json
git add package-lock.json
git merge --continue

For any other conflict, read the conflicted file and reconcile both sides manually.

This merge adds:

  • src/text-styles.tsparseTextStyles(text, channel) for marker substitution and parseSignalStyles(text) for Signal native rich text
  • src/router.tsformatOutbound gains an optional channel parameter; when provided it calls parseTextStyles after stripping <internal> tags
  • src/index.ts — both outbound sendMessage paths pass channel.name to formatOutbound
  • src/formatting.test.ts — test coverage for both functions across all channels

Read the full file on GitHub · 137 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 137 lines · 54 tokens per session scan A f5704feec89e

Subscribe to this mod's changes

channel-formatting is a skill published in the GitHub repository nanocoai/nanoclaw-gmail (2 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,023 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to channel-formatting, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens