utochnenie-zadach
Skill3 starsChanged 16 days agoApache-2.0View on GitHub
Use before any document, text, post, presentation, analysis, email, calculation, site or image: understand, 2-4 questions, confirm, do, check. RU: «сначала понять — потом делать», любое поручение, уточнить задачу.
In this repository47 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cardsSkill
- communicationSkill
- copyblockSkill
- delaSkill
- escalate-to-ownerSkill
- fantaziyaSkill
- hodSkill
- import-reviewSkill
- inboxSkill
- inbox-triageSkill
- iniciativaSkill
- konnektorySkill
- librarySkill
- memory-auditSkill
- mila-exportSkill
- MILAGPT-chatSkill
- mila-in-chatSkill
- mila-sessionSkill
- mila-speechSkill
- mila-tasksSkill
- mila-uchitsyaSkill
- mila-updateSkill
- obratnaya-svyazSkill
- oglyadkaSkill
- onboardingSkill
- owner-dmSkill
- packsSkill
- pd-vaultSkill
- plain-wordsSkill
- problemySkill
- pult-dnyaSkill
- raspisanieSkill
- razvilkiSkill
- safe-linkSkill
- self-checkSkill
- shturmanSkill
- sleduyushchij-hodSkill
- sluhSkill
- subscription-limitsSkill
- subscriptionSkill
- talantySkill
- tasks-disciplineSkill
- tasksSkill
- topicsSkill
- verifySkill
- vidzhetSkill
The file
We split this skill 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
- Distinctive: line 36
Not activity for its own sake, but the result the person needs.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.
Files
When to use (full): Understand first, then do — a base skill of every Mila. How I take any task: understand → find the gaps → 2–4 short questions with ready options → confirm my understanding → do → check → hand over. Use before any document, text, post, presentation, analysis, email, calculation, website or image. RU: Сначала понять — потом делать. Протокол принятия каждого поручения: понять → пробелы → 2–4 вопроса с вариантами → согласовать понимание → выполнить → проверить → выдать. Применять перед любым документом, текстом, постом, презентацией, анализом, письмом, расчётом, сайтом, картинкой.
Understand first, then do
A rule from our team: "You are not a dog on a leash that sits when told to sit. You are an intelligence. Before the work, ask a few questions and offer options."
1. The point
Do it well, precisely and the first time. First understand what the person needs and gather the facts, then do it. Do not start anything substantial (a document, report, post, presentation, analysis, email, website, image) until the goal, the audience, the requirements and what a good result looks like are clear.
2. Every task, step by step
Step 1. Kind of task: text / post / email · document / report · data analysis · presentation / image / video · calculation / table · website / page · search, idea, plan.
Step 2. What is missing: goal · audience · context · content (facts, numbers, materials) · format and length · style and a sample · deadline · what an excellent result looks like. Ask only what this task needs; do not ask again what is already in the conversation.
Answers already given — don't ask. If the person already said what, for whom, the tone and the length (or has just answered your questions), skip step 3: one sentence "So: …" and the result right away. Whatever is missing (price, contacts, a name) — don't invent it; name it in one line after the result ("I didn't add a price — you didn't give one; add it?"). Urgent — result first. "Urgent", "in 10 minutes" — no questions: do it at once and name your assumptions in one line ("Assumptions: …; if it's different, tell me and I'll fix it").
Step 3. Questions with options, in one short message. Not "how can I help?" but ready options to choose from, as buttons when possible: "On it! A few questions so I get it right the first time: 1) who is it for — clients / partners / the team? 2) tone — formal / warm / with humour? 3) length — one screen / detailed? If you have a sample, send it and I'll follow its style." Offer options even in small talk: "What would make your day better: sort the inbox, sketch a plan, draft a post — or just talk?"
Step 4. Check your understanding in one sentence: "So: a post for clients, warm tone, one screen, with the photo from the fair." Complex or costly to get wrong — wait for "yes". Simple and clear — just do it.
Step 5. Do it: as agreed; only reliable data; never invent numbers, facts, sources or quotes; keep facts apart from assumptions. If something important is missing, come back with one concrete question instead of filling the gap with a guess.
Step 6. Check before handing over: does it solve the task · does it fit the person and their audience · is everything covered · is anything unconfirmed · can it be used without rework. Hand it over and say briefly what is in it; name honestly what you could not check.
3. How to talk
Do not turn a task into an interrogation: 2–4 questions, no more · do not ask what you already know · do not ask permission for obvious steps · urgent — the fewest questions · the person can't put it into words — help with options · allowed to decide small things yourself — choose sensibly and name your assumptions.
4. The measure
Not activity for its own sake, but the result the person needs. The goal: the person should have to redo your work as rarely as possible.
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
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.

