A guided conversation for finding work tasks that could benefit from AI and deciding which to prioritize. It starts by exploring the user's job, team size, repeated work, documents, and frustrations.

Use it to identify repetitive or time-consuming work and assess which tasks are good candidates for automation.

It helps when you know AI might help but do not know where to begin. The questions turn vague interest into a list of concrete tasks to evaluate.

How ai-swiss/base configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ai-swiss/base. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ai-swiss/base/main/.ai/agents/createur-agent/skills/processes/diagnostic/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ai-swiss/base

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ai-swiss/base/diagnostic/github.svg)](https://agentmods.dev/skills/ai-swiss/base/diagnostic)

Your own site

<a href="https://agentmods.dev/skills/ai-swiss/base/diagnostic"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/diagnostic/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ai-swiss/base/diagnostic"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/diagnostic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,039 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.01039
Opus 5.5	$0.00026	$0.00416
Sonnet 5.5	$0.00013	$0.00208
Haiku 4.5	$0.00007	$0.00104

Measured 1mo ago against content hash 4bb9840196f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

diagnostic scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.ai/agents/createur-agent/skills/processes/diagnostic/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Diagnostic: par où commencer avec l'IA?

Faire parler une personne de son quotidien quand elle n'a rien à montrer. La conversation remplace la discussion ou les documents que d'autres apportent; au bout, ses notes passent par la même porte, adopter-ce-dossier, qui juge chaque tâche et rend la même fiche de proposition. Ce process recueille et passe la main: il ne juge pas, ne classe pas et ne recommande rien. Si la personne a quelque chose à montrer, c'est la porte qui commence, pas ce process.

Inputs

Demande à l'utilisateur:

Son métier ou activité: que fait son entreprise?
Sa taille: seul, petite équipe, PME?

Pas besoin de plus: le diagnostic se construit au fil de la conversation.

Étapes

1. Explorer le quotidien

Commence par des questions ouvertes, une à la fois:

«Décrivez-moi une journée type dans votre travail. Pas les grandes lignes, le concret: les tâches, les documents, les échanges.»

Puis creuse:

«Quelles tâches reviennent chaque semaine, presque à l'identique?»
«Quels documents rédigez-vous le plus souvent?»
«Qu'est-ce qui vous frustre dans votre quotidien? Ce qui prend trop de temps, ce qui est rébarbatif?»
«Y a-t-il des tâches que vous repoussez parce qu'elles sont longues ou pénibles?»
«Qu'est-ce qui ne doit jamais sortir de vos mains, même si un assistant pouvait le faire?»

Note chaque tâche mentionnée.

«Si je résume, vos principales tâches répétitives sont: [liste]. C'est bien ça? J'en oublie?»

← Reformulation

2. Passer la main

Une fois le résumé validé, écris des notes d'entretien sous .temp/{AAAA-MM-JJ}_{sujet}/notes-entretien.md, avec les mots de la personne: les tâches relevées avec leur fréquence, ce qui prend de l'énergie, les règles dites à l'oral, les lignes rouges. Rien d'autre ne s'écrit, pas même le journal: la porte l'écrit après l'export.

«Je résume ce que vous m'avez dit dans une page, puis je vous prépare une fiche: ce qu'un assistant ferait pour vous, ce qu'il ne fera jamais, et par où commencer. Vous la lirez tranquillement, et rien ne se construit avant votre retour.»

Read the full file on GitHub · 82 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · -29 lines · +29 tokens per session 4bb9840196f5
2mo ago First seen · 111 lines · 37 tokens per session scan A 61194b3f2b9f

Subscribe to this mod's changes

diagnostic is a skill published in the GitHub repository ai-swiss/base (65 stars, last pushed 8d ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,039 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning ai ai-agents automatiser cli cognitive-sovereignty commencer diagnostic digital-sovereignty opportunités premier quotidien tâches

diagnostic next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
diagnosticai-swiss/base	Skill	65	8d ago	Apache-2.0	A	66	Claude Code
feishuHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	33	Claude Code, Codex
interviewHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	40	Claude Code, Codex
atmos-validationcloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	31	Claude Code
atmos-configcloudposse/atmos	Skill	1.4k	yesterday	Apache-2.0	A	31	Claude Code
gamedev-shadersericrisco/rsc-harness	Skill	503	2d ago	MIT	A	102	Claude Code, Codex
loongsuite-pilot-insightalibaba/loongsuite-pilot	Skill	239	yesterday	Apache-2.0	A	111	Claude Code, Codex

base: Skill for Claude Code