How do I install the Find Interceptor Impl skill?

Run npx skillmds@latest add membrane/find-interceptor-impl in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Find Interceptor Impl safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Find Interceptor Impl?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Find Interceptor Impl free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Find Interceptor Impl?

membrane (@membrane) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Find Interceptor Impl by membrane — Agent Skill

Name: Find Interceptor Impl
Author: membrane

Find Interceptor Impl

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.

membrane cda3012 2 files · 4.9 KB Updated Sep 17, 2026

File contents

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 groovy

It 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.java

Class → 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: name need not be the first annotation attribute (@MCElement(component = false, name = "...") is fine), and both name="x" and name = "x" spacings match.

---name: find-interceptor-impldescription: 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.---# Find Interceptor ImplementationIn Membrane, every interceptor (and most config elements) is wired to an XMLconfig 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 thetwo directions.## Name → implementation class (the common case)Run the helper with the XML element name:```bash.claude/skills/find-interceptor-impl/find-interceptor-impl.sh groovy```It prints the class and file, searching every module's `src/main/java` (theannotation is not limited to `core`):```textImplementation class for <groovy>: GroovyInterceptor -> ./core/src/main/java/.../groovy/GroovyInterceptor.java```## Class → element name (reverse direction)Given a class name, find its file and annotation in one shot — no need to knowwhich module it lives in first:```bashgrep -rn --include='GroovyInterceptor.java' '@MCElement' .```The `name = "..."` value is the tag used in `proxies.xml`. No match means theclass isn't directly configurable — it's likely an abstract base or exposedunder a parent element; check its subclasses for the nearest one carrying`@MCElement`, or grep `distribution/examples` / `proxies.xml` for how it'sactually 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**: `name` need not be the first annotation attribute (`@MCElement(component = false, name = "...")` is fine), and both `name="x"` and `name = "x"` spacings match.

Frequently asked questions