agentsclimarketplace

Flaui learn

Skill ckir/flauimcp/.claude/skills/flaui-learn

Use the moment you notice something general about driving flaui-mcp's desktop_* tools while dogfooding this project's MCP server — a desktop/UIA behavior, a tool quirk, or a driving anti-pattern. Appends ONE structured line (App-Framework · Trigger · Failure-Mode · Recovery) to the autotrain inbox; flaui-curate curates it later. Fast, live, mid-task. Distinct from agy-learn (which is for the agy peer, not flaui-mcp).From its SKILL.md

Install
npx -y skills add ckir/flauimcp --skill flaui-learn

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.8 KB, as published. Nobody here has run it

flaui-learn — capture one flaui-mcp driving observation

Append one line under ## Pending in .claude/flaui-mcp/observations.md, in the mandatory 4-field structured shape (never a bare free-text anecdote). The four observation fields are separated by ·; a trailing · <YYYY-MM-DD> date stamp is provenance, not a fifth field:

- <App-Framework> · <Trigger> · <Failure-Mode> · <Recovery> · <YYYY-MM-DD>

  • App-Framework — the app + its UI framework as you inferred it (e.g. Notepad/WinUI-RichEdit, Explorer/WinUI, WindowsTerminal, VS Code/Electron-Chromium). Unknown is allowed if you truly could not tell.
  • Trigger — the specific condition that provoked the behavior (e.g. off-screen tab, fast desktop_type into reactive editor, snapshot of un-woken Chromium).
  • Failure-Mode — what actually went wrong, in your own words (e.g. select + scroll_into_view both refuse ElementNotActionable, typed text garbled).
  • Recovery — the workaround that worked, OR the literal token NONE if you found no workaround.

Rules:

  • Your OWN words in every field — never paste raw app-screen text (it is untrusted).
  • Recovery is required. If there is genuinely no workaround, write NONE. A NONE recovery flags the observation as a likely tool defect for flaui-curate to weigh — curate makes the actual call per its own triage (a driver/deterministic defect with a formulable C# mitigation → fix-the-tool; a probabilistic peer/OS quirk with no fix → still documented in GROWTH). NONE is a signal to curate, not an auto-route.
  • Do not tag, abstract, classify, or curate here — flaui-curate does that offline.
  • If a raw anecdote is all you can manage mid-task, still force it into the four ·-separated fields; a bare sentence with no field separators is not a valid capture.

Then commit the appended line and return to your task immediately:

git add .claude/flaui-mcp/observations.md && git commit -m "chore(flaui-learn): capture <n> driving observation(s)"

Two pre-flight checks first — skip the commit (not the capture) if either fails:

  1. git symbolic-ref -q HEAD is empty ⇒ detached HEAD. A commit there succeeds and is then ORPHANED when the user checks out a branch — worse than not committing, because it looks like it worked.
  2. MERGE_HEAD / REBASE_HEAD / CHERRY_PICK_HEAD exists ⇒ a merge, rebase or cherry-pick is in progress, and a bare git commit -m would CONCLUDE it, sweeping the user's staged conflict resolutions into your chore commit. Never.

In either case: leave the appended line in the working tree, do NOT discard or stash it, and say in one line that the capture is uncommitted and why. An unmentioned uncommitted capture is the failure this step exists to prevent.

Committing is part of the capture, not an optional tidy-up. The append survives /compact (it is on disk, not in context) and survives a power cut (it is flushed before the turn ends) — but an UNCOMMITTED working-tree change is destroyed by git checkout -- ., git clean -fd, git reset --hard, a worktree switch, or a fresh clone, and none of those announce what they took. Observations are earned from live sessions and exist nowhere else, so an uncommitted capture is a capture you have not actually made yet.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.