find-interceptor-impl
Skill658 starsChanged 3 months agoApache-2.0View on GitHub
Find the Java implementation class behind a Membrane interceptor or config element given its XML name (the @MCElement value), e.g. "which class implements the <groovy> interceptor?". Use whenever the user references an interceptor / plugin / config element by its proxies.xml tag name (groovy, apiKey, rewriter, log, ...) and wants the source file or class, or asks where an interceptor is implemented / defined / configured. Also use the reverse direction — going from a class name to its config element name.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- config-error-handlingSkill
- create-tutorialSkill
- find-exampleSkill
- 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
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Run the helper with the XML element name:
≈ “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 Interceptor Implementation
In Membrane, every interceptor (and most config elements) is wired to an XML
config tag by an @MCElement(name = "...") annotation on its Java class. The tag
<groovy> in proxies.xml is implemented by the class annotated
@MCElement(name = "groovy") — GroovyInterceptor. This skill maps between the
two directions.
Name → implementation class (the common case)
Run the helper with the XML element name:
.claude/skills/find-interceptor-impl/find-interceptor-impl.sh groovyIt prints the class and file, searching every module's src/main/java (the
annotation is not limited to core):
Implementation class for <groovy>:
GroovyInterceptor -> ./core/src/main/java/.../groovy/GroovyInterceptor.javaClass → element name (reverse direction)
Given a class name, find its file and annotation in one shot — no need to know which module it lives in first:
grep -rn --include='GroovyInterceptor.java' '@MCElement' .The name = "..." value is the tag used in proxies.xml. No match means the
class isn't directly configurable — it's likely an abstract base or exposed
under a parent element; check its subclasses for the nearest one carrying
@MCElement, or grep distribution/examples / proxies.xml for how it's
actually used.
Behaviour to trust
- Several results — some names are declared on more than one class (a base plus an override, or per-module variants); the script lists all of them, pick by package/context.
- No exact match — exits non-zero and suggests the closest declared names
(handles typos like
grovy→groovy); re-run with the corrected name. - Matching is lenient:
nameneed not be the first annotation attribute (@MCElement(component = false, name = "...")is fine), and bothname="x"andname = "x"spacings match.
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.

