agentleFS
RobThePCGuyRobThePCGuy/Claude-Patent-Creator/skills/mpep-search/SKILL.md

mpep-search

Skill206 starsChanged 8 months agoMITView on GitHub

Expert system for searching USPTO MPEP, 35 USC statutes, 37 CFR regulations, and post-Jan 2024 updates.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Search MPEP corpus through hybrid RAG (FAISS vector + BM25 keyword + HyDE + cross-encoder reranking).

    line 8
  2. Distinctive:

    No empty/whitespace-only queries

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MPEP Search Skill

Search MPEP corpus through hybrid RAG (FAISS vector + BM25 keyword + HyDE + cross-encoder reranking).

Sources:

  • MPEP: Manual of Patent Examining Procedure
  • 35 USC: United States Code Title 35
  • 37 CFR: Code of Federal Regulations Title 37
  • Subsequent Publications: Federal Register updates (post-Jan 2024)

Core Operations

1. search_mpep

Inputs:

  • query (string, required): Search query (minimum 3 characters)
  • top_k (int, optional): Number of results (default: 5, max: 20)
  • retrieve_k (int | None, optional): Candidates before reranking (default: top_k * 4, max: 100)
  • source_filter (string | None, optional): Filter by source ("MPEP", "35_USC", "37_CFR", "SUBSEQUENT", or None)
  • is_statute (bool | None, optional): Filter for statute content
  • is_regulation (bool | None, optional): Filter for regulation content
  • is_update (bool | None, optional): Filter for recent updates

Outputs:

{
    "rank": int,
    "source": str,
    "section": str,
    "file": str,
    "page": int,
    "has_statute": bool,
    "has_mpep_ref": bool,
    "has_rule_ref": bool,
    "is_statute": bool,
    "is_regulation": bool,
    "is_update": bool,
    "relevance_score": float,
    "text": str,
    # Optional for SUBSEQUENT:
    "doc_type": str,
    "fr_citation": str,
    "effective_date": str
}

Examples:

# Basic search
search_mpep("enablement requirement 35 USC 112", top_k=5)

# Search only statutes
search_mpep("written description", top_k=10, is_statute=True)

# Search recent updates
search_mpep("AI inventorship", is_update=True)

# Filter by source
search_mpep("fee schedule", source_filter="37_CFR")

2. get_mpep_section

Retrieve all content from specific MPEP section.

Inputs:

  • section_number (string, required): MPEP section number (e.g., "2100", "608.01")
  • max_chunks (int, optional): Maximum chunks to return (default: 50)

Outputs:

{
    "section": str,
    "total_chunks": int,
    "chunks": [
        {
            "text": str,
            "metadata": {
                "source": str,
                "file": str,
                "page": int,
                "section": str,
                "has_statute": bool,
                "has_mpep_ref": bool,
                "has_rule_ref": bool,
                "is_statute": bool,
                "is_regulation": bool,
                "is_update": bool
            }
        }
    ]
}

Error Response:

{"error": "No content found for MPEP section {section_number}"}

Examples:

# Get MPEP 2100 (Patentability)
get_mpep_section("2100", max_chunks=50)

# Get subsection
get_mpep_section("608.01")

Input Validation

Query validation:

  • Minimum 3 characters
  • Case-insensitive
  • No empty/whitespace-only queries

Section number validation:

  • Numeric with optional decimal (e.g., "100", "2100", "608.01")

Limits:

  • top_k capped at 20
  • retrieve_k capped at 100

Implementation Notes

Index Location:

  • FAISS index: mcp_server/index/mpep_index.faiss
  • Metadata: mcp_server/index/mpep_metadata.json
  • BM25 index: mcp_server/index/mpep_bm25.json

Search Architecture:

  1. HyDE Query Expansion (hypothetical documents)
  2. Hybrid Retrieval (FAISS vector + BM25 keyword via RRF)
  3. Cross-Encoder Reranking (final relevance scores)
  4. Metadata Filtering (source/type filters)

Dependencies:

  • sentence-transformers (BGE-base-en-v1.5)
  • FAISS (vector search)
  • rank-bm25 (keyword search)
  • Cross-encoder (reranking)
  • HyDE (optional, graceful degradation)

Error Handling:

  • Clear error messages for missing index/invalid queries
  • Graceful degradation if HyDE fails
  • Input validation before processing

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.