MCP HubMCP Hub
SKILL·FAFBD1

fungi-identification

pjt222
Mis à jour 1 month ago
9 vues
26
3
26
Voir sur GitHub
Autreai

À propos

Cette compétence permet l'identification sur le terrain des champignons par l'analyse de leurs caractéristiques morphologiques, de leurs sporées et de leur habitat. Elle aide à différencier les espèces similaires, à évaluer la toxicité et impose une règle de sécurité prioritaire : une certitude absolue avant toute consommation. Utilisez-la lors de la cueillette, pour confirmer une espèce ou évaluer des champignons inconnus sur une propriété.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add pjt222/agent-almanac -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternatif
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/fungi-identification

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Fungi Identification

Find mushroom ID in field. Use shape, spore prints, habitat, season. Safety first, always.

When Use

  • Unknown fungus, need ID
  • Foraging edible mushrooms, confirm species before eat
  • Garden/property fungi: harmful?
  • Build field ID skill with structured observation
  • Tell edible from dangerous look-alike

Inputs

  • Required: Fungus specimen or clear observation in situ
  • Required: Eye for fine detail (cap, gills, stem, base)
  • Optional: Field guide for region
  • Optional: Paper + glass for spore prints
  • Optional: Knife for cross-section
  • Optional: Hand lens (10x) for fine detail

Steps

Step 1: Cardinal Rule

Before any ID work, burn rule into head.

CARDINAL RULE:
If you are not 100% certain of the identification, DO NOT EAT IT.

There is no "universal edibility test" for mushrooms.
Some deadly species taste pleasant.
Some deadly species have delayed symptoms (24-72 hours).
Some deadly species have NO antidote.

The cost of a false positive (eating a misidentified mushroom) is
organ failure and death. The cost of a false negative (skipping an
edible mushroom) is a missed meal.

ALWAYS ERR TOWARD CAUTION.

Got: Cardinal rule internalized before proceeding.

If fail: No failure mode for this step. Rule not internalized → do not proceed to field ID for consumption.

Step 2: Document Habitat

Context narrows ID before touching specimen.

Habitat Recording:
+--------------------+------------------------------------------+
| Factor             | Record                                   |
+--------------------+------------------------------------------+
| Substrate          | Soil, wood (dead/living), dung, leaf      |
|                    | litter, moss, other fungi                |
+--------------------+------------------------------------------+
| Tree association   | What trees are within 10m? (Many fungi    |
|                    | are mycorrhizal with specific tree genera)|
+--------------------+------------------------------------------+
| Moisture           | Dry, damp, wet, waterlogged              |
+--------------------+------------------------------------------+
| Light              | Full shade, dappled, open                |
+--------------------+------------------------------------------+
| Season             | Early spring, late spring, summer, early  |
|                    | autumn, late autumn, winter              |
+--------------------+------------------------------------------+
| Altitude           | Lowland, mid-altitude, montane           |
+--------------------+------------------------------------------+
| Growth pattern     | Solitary, scattered, clustered, ring,    |
|                    | shelf/bracket                            |
+--------------------+------------------------------------------+

Got: Complete habitat record gives context for species ID.

If fail: Habitat unclear (urban garden, mixed plantings)? Record what visible. Incomplete habitat = lower ID confidence — factor into safety check.

Step 3: Examine Morphological Features

Systematic look at specimen.

Morphological Checklist:

CAP (Pileus):
- Shape: convex, flat, concave, conical, umbonate, bell-shaped
- Diameter (measure or estimate)
- Surface: smooth, scaly, fibrous, slimy, dry, cracked
- Colour (note if colour changes with age or moisture)
- Margin: smooth, striate, inrolled, appendiculate (veil remnants)

GILLS / PORES / SPINES (Hymenium):
- Type: gills (lamellae), pores (tubes), spines (teeth), smooth
- Attachment: free, adnexed, adnate, decurrent
- Spacing: crowded, close, distant
- Colour (important — note changes with age)
- Bruising: do gills change colour when damaged?

STEM (Stipe):
- Height and diameter
- Shape: equal, tapered, bulbous, club-shaped
- Surface: smooth, fibrous, scaly, reticulate (netted)
- Interior: solid, hollow, stuffed (pithy center)
- Ring (annulus): present/absent, position, persistent/fragile
- Volva (cup at base): present/absent — ALWAYS check by
  carefully excavating the base (Amanita species have a volva)

FLESH (Context):
- Colour when cut
- Colour change on exposure to air (note time to change)
- Texture: firm, brittle, fibrous, gelatinous
- Smell: mushroomy, anise, radish, flour, chlorine, unpleasant
- Taste: (ONLY if species is confirmed non-deadly by an expert;
  for unknown species, DO NOT taste)

SPORE PRINT:
- Remove the stem; place the cap gill-side down on paper
  (half white, half dark paper to see any colour)
- Cover with a glass or bowl to maintain humidity
- Wait 4-12 hours
- Record spore colour: white, cream, pink, brown, purple-brown,
  black, rust-orange

Got: Full morphological description — all major features.

If fail: Feature not observable (no ring visible, may have been lost)? Record "not observed" not "absent." Distinction matters for ID.

Step 4: ID with Multiple Confirmations

Cross-reference all data vs reference material.

Identification Protocol:
1. Use habitat + season to narrow to likely genera
2. Use cap shape + gill type + spore colour to narrow to species group
3. Check ALL features against the candidate species description
4. Specifically check against dangerous look-alikes:
   - Does this species have a deadly doppelganger?
   - What feature distinguishes the edible from the deadly?
   - Can I see that distinguishing feature clearly?

Confidence Levels:
+----------+---------------------------+---------------------------+
| Level    | Criteria                  | Action                    |
+----------+---------------------------+---------------------------+
| Certain  | All features match; no    | Safe to collect (for      |
|          | look-alike confusion;     | experienced identifiers)  |
|          | experienced with species  |                           |
+----------+---------------------------+---------------------------+
| Probable | Most features match;      | DO NOT eat. Collect for   |
|          | one or two uncertain;     | further study (spore      |
|          | look-alike eliminated     | print, expert review)     |
+----------+---------------------------+---------------------------+
| Possible | Some features match;      | DO NOT eat. Photograph    |
|          | look-alike not fully      | and seek expert opinion   |
|          | eliminated                |                           |
+----------+---------------------------+---------------------------+
| Unknown  | Cannot narrow to species  | DO NOT eat. DO NOT        |
|          |                          | handle extensively        |
+----------+---------------------------+---------------------------+

Got: Species-level ID with explicit confidence + look-alike assessment.

If fail: ID stalls at genus level? OK for learning. For eating, only species-level "Certain" ID acceptable.

Checks

  • Cardinal rule acknowledged before starting
  • Habitat documented before examining specimen
  • All morphological features examined systematically
  • Base excavated to check volva
  • Spore print taken (if time allows)
  • Dangerous look-alikes explicitly checked + eliminated
  • Confidence level honestly assessed
  • Only "Certain" IDs considered for eating

Pitfalls

  • One-feature ID: "Looks like chanterelle" by colour alone. True chanterelles have false gills (ridges), grow from soil near trees, apricot smell. False chanterelles + Jack-o'-lanterns share colour but differ every other feature
  • Skipping base check: No dig = no volva — single most important feature for deadly Amanita (death cap, destroying angel)
  • Trust apps blind: AI mushroom ID apps big error rates for look-alikes. Use as start, never as confirmation
  • "Common = safe": Abundance no tell edibility. Deadly species can be locally abundant
  • Tasting unknowns: Some mycologists taste as diagnostic, needs expert knowledge of safe-to-taste species. Non-experts → no taste unknown fungi
  • Ignoring delayed toxins: Some species (Amanita phalloides) pleasant taste + delayed symptoms. When symptoms appear (24-48h), liver damage severe

See Also

  • mushroom-cultivation — growing known species kills ID risk entire
  • forage-plants — complementary field ID skill; same multi-feature confirmation method

Dépôt GitHub

pjt222/agent-almanac
Chemin: i18n/caveman/skills/fungi-identification
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams
FAQ

Frequently asked questions

What is the fungi-identification skill?

fungi-identification is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform fungi-identification-related tasks without extra prompting.

How do I install fungi-identification?

Use the install commands on this page: add fungi-identification to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does fungi-identification belong to?

fungi-identification is in the Other category, tagged ai.

Is fungi-identification free to use?

Yes. fungi-identification is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Compétences associées

llamaguard
Autre

LlamaGuard est le modèle de Meta, doté de 7 à 8 milliards de paramètres, conçu pour modérer les entrées et sorties des LLM selon six catégories de sécurité comme la violence et les discours haineux. Il offre une précision de 94 à 95 % et peut être déployé avec vLLM, Hugging Face ou Amazon SageMaker. Utilisez cette compétence pour intégrer facilement le filtrage de contenu et des garde-fous de sécurité dans vos applications d'IA.

Voir la compétence
cost-optimization
Autre

Cette compétence de Claude aide les développeurs à optimiser les coûts du cloud grâce au redimensionnement des ressources, aux stratégies d'étiquetage et à l'analyse des dépenses. Elle fournit un cadre pour réduire les dépenses cloud et mettre en œuvre une gouvernance des coûts sur AWS, Azure et GCP. Utilisez-la lorsque vous devez analyser les coûts d'infrastructure, redimensionner les ressources ou respecter des contraintes budgétaires.

Voir la compétence
sports-betting-analyzer
Autre

Cette compétence Claude analyse les marchés des paris sportifs, incluant les spreads, les over/under et les paris spéciaux, en examinant les tendances historiques et les statistiques situationnelles pour identifier les paris à valeur ajoutée. Elle fournit une sortie en markdown structuré avec des recommandations actionnables à des fins éducatives. Les développeurs doivent l'utiliser pour des outils d'analyse de paris sportifs tout en notant qu'elle est conçue uniquement pour le divertissement et l'éducation.

Voir la compétence
quantizing-models-bitsandbytes
Autre

Cette compétence quantifie les LLMs en précision 8 bits ou 4 bits à l'aide de bitsandbytes, permettant une réduction de 50 à 75 % de la mémoire utilisée avec une perte de précision minime. Elle est idéale pour exécuter des modèles plus volumineux sur une mémoire GPU limitée ou pour accélérer l'inférence, prenant en charge des formats comme INT8, NF4 et FP4. La compétence s'intègre à HuggingFace Transformers et permet l'entraînement QLoRA ainsi que l'utilisation d'optimiseurs en 8 bits.

Voir la compétence