Individual skill

friction-log

Draft a short, honest account of where using Mycelium was confusing or slow, for the user to edit and choose whether to send. Reports experience; never prescribes fixes. Based on Hoskins's friction logging.

plugins/mycelium/skills/friction-log/SKILL.md

Read pinned source

Source commit d44421b0667bb71ad515ae7576dfc0f47b00504f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
51
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Friction Log

**What this is, in Hoskins's words:** *"A friction log is an informal document that you write as you
use a product. You report any confusion or roadblocks you experience. When you've finished, **you
hand it off** to the engineers or PMs responsible for the product."* Its purpose: *"we also need
outside perspectives. Since outsiders don't have all day, we need a lightweight option for them to
help out."*

**Mycelium has the opposite problem from most products: it can see its own friction and has no way to
send it back.** Measured 2026-09-20 in the dogfood repo: of 91 completed outreach tasks, ~71 were
outbound and ~4 inbound. The channel runs one way.

---