agentleFS
Sign inStart free
DraganoiderDraganoider/claude-code-telegram/.claude/skills/wiki/SKILL.md

wiki

Skill1 starsChanged 4 months agoMITView on GitHub

Consult and maintain the project knowledge wiki in docs/wiki. Use BEFORE working on the permission bridge, SDK integration, Telegram limits, or architecture — and AFTER learning any durable fact or making a design decision, to record it.

42 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 4 projects that use this

  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • ibahgatSkill

    hud

    Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the relevant page before touching an area it covers:

    line 12
  2. Very specific:

    Do not re-research a fact the wiki already records (e.g.

    line 22
  3. Distinctive:

    If a recorded fact proves wrong, correct it in place — a stale wiki page is a bug.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “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
SKILL.md

Project wiki workflow

The wiki at docs/wiki/ is this project's long-term memory. Two duties:

1. Recall (before working)

Read the relevant page before touching an area it covers:

Working on…Read first
Permissions, approval buttons, modesdocs/wiki/architecture.md (permission bridge) + ADR-004 in decisions.md
Anything calling claude_agent_sdkdocs/wiki/sdk-notes.md
Message rendering, buttons, limits, parse errorsdocs/wiki/telegram-notes.md
"Why is X like this?" / changing a designdocs/wiki/decisions.md
Picking what to build nextdocs/wiki/roadmap.md

Do not re-research a fact the wiki already records (e.g. re-fetching SDK docs for the can_use_tool signature) — trust the wiki unless evidence contradicts it.

2. Record (after learning or deciding)

In the SAME session, update the wiki when you:

  • discover a non-obvious API fact, limit, or footgun → add to sdk-notes.md or telegram-notes.md with the version it was verified against;
  • make or change a design decision → append a dated ADR to decisions.md (newest first: context → decision → consequences);
  • change the architecture → fix architecture.md so it stays true;
  • complete/decide a roadmap item → remove it from roadmap.md (and ADR it).

If a recorded fact proves wrong, correct it in place — a stale wiki page is a bug.

Style: distilled facts and reasons, no narration. Keep pages skimmable.

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