find-example
Skill658 starsChanged 3 months agoApache-2.0View on GitHub
Find the runnable examples and tutorials that demonstrate a Membrane interceptor or config element, given its XML name (the @MCElement value), e.g. "is there an example for <call>?", "which tutorials use the rewriter?", "show me examples of apiKey". Use whenever the user wants to locate existing examples or tutorials under distribution/examples or distribution/tutorials for a given element / plugin / interceptor, or asks whether one has any. This is the usage-finding counterpart to find-interceptor-impl (which finds the Java class).
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- config-error-handlingSkill
- create-tutorialSkill
- find-interceptor-implSkill
- membrane-configSkill
- optimize-interceptor-docsSkill
- refactorSkill
- release-notesSkill
- review-branchSkill
- run-example-testSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run the helper with the element name (the @MCElement(name = "...") value):
- Very specific: line 50
Matches config, not prose: Only proxies.xml, *.yaml and *.yml are searched, against both the XML (<name ...>) and YAML (name:) tag forms, …
≈ “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
Find Examples and Tutorials
Membrane ships runnable demos in two trees:
distribution/examples/<category>/<name>/— a self-contained example, usually with aproxies.xmland/orapis.yamlconfig plus aREADME.md.distribution/tutorials/<category>/NN-Title.yaml— numbered, self-teaching tutorial steps (one YAML file each).
An element appears in these as a config tag — <call .../> in XML or - call:
in YAML. This skill greps both trees for that tag and reports where the element
is actually used (not just mentioned in prose). It's the inverse of
find-interceptor-impl: that maps a name to its Java class, this maps a name to
its demos.
Usage
Run the helper with the element name (the @MCElement(name = "...") value):
.claude/skills/find-example/find-example.sh rateLimiterIt lists example directories (with the first line of each README as a summary) and tutorial files:
Examples using <rateLimiter>:
distribution/examples/rate-limiting The `rateLimiter` helps you maintain ...
distribution/examples/xml/namespaces Namespaces are a powerful XML feature ...
Tutorials using <rateLimiter>:
distribution/tutorials/operation/70-Production-Settings.yamlNarrow to one tree when that's all the user wants:
.claude/skills/find-example/find-example.sh rewriter --tutorials
.claude/skills/find-example/find-example.sh apiKey --examplesBehaviour to trust
- Matches config, not prose. Only
proxies.xml,*.yamland*.ymlare searched, against both the XML (<name ...>) and YAML (name:) tag forms, so a README that merely names the element won't produce a false hit. - Examples are deduped to their directory; tutorials are listed per file
(they're individual steps sharing one category directory).
- No match → exit 3. Either the element genuinely has no demo, or the name is
off. Confirm the name with
find-interceptor-impland retry.
- No match → exit 3. Either the element genuinely has no demo, or the name is
off. Confirm the name with
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.

