agentleFS
Sign inStart free
ZhouYinLong-labZhouYinLong-lab/Dog-Skills/claude-to-im-skill/CLAUDE.md

Dog-Skills / claude-to-im-skill

CLAUDE.md7 starsChanged 5 months agoMITView on GitHub

When replying to user-reported issues, always include a self-help prompt at the end of the reply. Guide users to use their AI coding assistant (Claude Code / Codex) to diagnose and fix the problem themselves. Example: 自助排查提示： 你可以直接在 Claude Code（或 Codex）中发送以下提示，让 AI 帮你诊断问题： This approach: - Reduces maintainer burden by enabling users to self-diagnose - Leverages the fact that users already have an AI coding assistant installed - Provides actionable next steps rather than just error explanations

  • Reads credentials

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When replying to user-reported issues, always include a self-help prompt at the end of the reply.

    line 5

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md — Project Guidelines for claude-to-im-skill

Replying to GitHub Issues

When replying to user-reported issues, always include a self-help prompt at the end of the reply. Guide users to use their AI coding assistant (Claude Code / Codex) to diagnose and fix the problem themselves. Example:

自助排查提示： 你可以直接在 Claude Code（或 Codex）中发送以下提示，让 AI 帮你诊断问题：

请帮我排查 claude-to-im 桥接服务的问题。
1. 读取 ~/.claude-to-im/logs/bridge.log 最近 50 行日志
2. 读取 ~/.claude-to-im/config.env 检查配置是否正确
3. 运行 bash ~/.claude/skills/claude-to-im/scripts/doctor.sh 并分析输出
4. 根据日志和配置给出具体的修复建议

This approach:

  • Reduces maintainer burden by enabling users to self-diagnose
  • Leverages the fact that users already have an AI coding assistant installed
  • Provides actionable next steps rather than just error explanations

Download now (ZIP)

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.

Check your setup, free