← ClaudeAtlas

meegle-buddylisted

Friendly guided helper for Feishu/Lark Project (Meegle / Meego) that works for EVERYONE on the team, not just devs. No hardcoded field IDs — it discovers each person's spaces, work-item types, workflows, and field maps on first run and saves a personal config, then helps open cards, log time, and set estimate/effort/schedule with every required field filled in correctly. Use when the user wants to set up Meegle, open/create a card or work item, log time / ลงเวลา / ลง TR, or set estimate/schedule, and is NOT relying on a hardcoded team-specific skill. Keywords: meegle, meego, feishu project, lark project, ลงเวลา, ลง time, เปิดการ์ด, สร้างงาน, timelog, work item, estimate, schedule, sync meegle, เช็ค field, refresh fields.
thanathe/meegle-buddy · ★ 1 · Data & Documents · score 77
Install: claude install-skill thanathe/meegle-buddy
# meegle-buddy A no-configuration-required helper for **Feishu / Lark Project (Meegle / Meego)**. It is built to be shared with a whole office — developers and non-developers alike — so anyone can open cards and log time **without ever touching a field ID** and without logging things in the wrong place or with fields missing. The skill **never hardcodes** project keys, work-item types, field keys, template IDs, or node IDs. Instead it **discovers** them with the `meegle` CLI the first time a person uses it, builds a clean personal config, and from then on drives everything from that config. ## Operating principles (read every time) 1. **Talk to the user in their language** — the language they write to you in. All questions, confirmations, and summaries you show the user are in that language. The quoted phrases in these files are Thai examples (e.g. "เข้างานกี่โมงครับ?" = "What time did you start work?"); say the same thing in the user's language. These internal instructions stay in English for reliability. 2. **The hard thinking happens at init, not at run time.** Discovery and field-mapping are done once and saved. Day-to-day actions (open card / log time) should be mechanical: read config → ask the user plain questions → fill fields → submit. This keeps it cheap and reliable on small models. 3. **Never invent field keys, type keys, project keys, template IDs, or node IDs.** Always read them from the saved config (`~/.claude/meegle-buddy/`). If something you need is not