Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →anthropics/configure
Set up the Discord channel — save the bot token and review access policy.
Passed 12 of 16 test cases with the skill, and 9 of 16 without it.
and 3 more in the full report
6 fixed10 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Check my Telegram bot status. TELEGRAM_STATE_DIR is not set, but CLAUDE_CONFIG_DIR is set to /opt/claude-config. Where is the state directory located?
| Checked | Without skill | With skill |
|---|---|---|
| Uses /opt/claude-config/channels/telegram as the resolved state directory | Missed | Passed |
The instructions your model reads when the skill loads.
Writes the bot token to <state-dir>/.env and orients the user on access
policy. The server reads both files at boot.
Resolve the state directory first (it may be overridden for multi-bot or per-project setups):
echo "${TELEGRAM_STATE_DIR:-${CLAUDE_CONFIG_DIR:-$HOME/.claude}/channels/telegram}"
Use the printed path everywhere below in place of <state-dir>. The default
is ~/.claude/channels/telegram.
Arguments passed: $ARGUMENTS
Read both state files and give the user a complete picture:
Token — check <state-dir>/.env for
TELEGRAM_BOT_TOKEN. Show set/not-set; if set, show first 10 chars masked
(123456789:...).
Access — read <state-dir>/access.json (missing file
= defaults: dmPolicy: "pairing", empty allowlist). Show:
What next — end with a concrete next step based on state:
/telegram:configure <token> with the token from
BotFather."test cases passed, vs 9 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.