Automated summary
Enables debug logging for the XMTP CLI through the XMTP_FORCE_DEBUG and XMTP_FORCE_DEBUG_LEVEL environment variables.
Strengths
- Minimal setup: just two environment variables
- Works either in a .env file or as a shell export
- Points to a dedicated rules file (rules/force-debug-env.md) for details
Limitations
- Only controls log verbosity, not the diagnosis of the underlying error
- Requires being able to change the environment and restart the CLI
- Says nothing about where logs are written or how to redact sensitive data
Use it when the XMTP CLI misbehaves or you need verbose logs to inspect its behavior.
Avoid it when the issue lies in an XMTP client library rather than the CLI, or when environment variables cannot be changed.
Security analysis
SafeThe skill only documents setting XMTP debug-related environment variables. It declares no tools, runs no commands, accesses no secrets, and performs no destructive or network operations.
No concerns found
How this analysis is madeExamples
The XMTP CLI keeps failing to connect — show me how to enable debug logging with environment variables.Set XMTP_FORCE_DEBUG_LEVEL so the XMTP CLI prints debug-level logs, and tell me whether to put it in .env or export it in the shell.name: xmtp-cli-debugging description: Enable CLI debug logging with environment variables. Use when troubleshooting or inspecting CLI behavior. license: MIT metadata: author: xmtp version: "1.0.0"
CLI debugging
Enable debug logging for the XMTP CLI via environment variables.
When to apply
- Troubleshooting CLI behavior or connection issues
- Inspecting verbose logs (debug level)
Rules
force-debug-env–XMTP_FORCE_DEBUGandXMTP_FORCE_DEBUG_LEVEL
Quick start
Set in .env or export:
XMTP_FORCE_DEBUG=true
XMTP_FORCE_DEBUG_LEVEL=debug
Read rules/force-debug-env.md for details.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/xmtp-cli-debugging-mrwakfok' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/xmtp-cli-debugging-mrwakfok/download' --output '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md.part' && mv '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md.part' '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && test -s '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/xmtp-cli-debugging' && cp -R '.skill-downloads/xmtp-cli-debugging-mrwakfok' '.claude/skills/xmtp-cli-debugging'Cursor
test -f '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && test -s '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/xmtp-cli-debugging' && cp -R '.skill-downloads/xmtp-cli-debugging-mrwakfok' '.cursor/skills/xmtp-cli-debugging'Codex
test -f '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && test -s '.skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/xmtp-cli-debugging' && cp -R '.skill-downloads/xmtp-cli-debugging-mrwakfok' '.agents/skills/xmtp-cli-debugging'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/xmtp-cli-debugging-mrwakfok'openskills read 'xmtp-cli-debugging-mrwakfok'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/xmtp-cli-debugging-mrwakfok/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.