New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Microservice API Endpoint Routing 404

by divinevideo in divinevideo/divine-mobile

Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service.

MPL-2.0Auto-check passedBackend & APIs

Install Microservice API Endpoint Routing 404

skills CLI
$ npx skills add divinevideo/divine-mobile --skill microservice-api-endpoint-routing-404 -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install divinevideo/divine-mobile microservice-api-endpoint-routing-404 --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/microservice-api-endpoint-routing-404 .claude/skills/microservice-api-endpoint-routing-404 && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
microservice-api-endpoint-routing-404
GitHub stars
266
Token cost
~1k tokens
SKILL.md length
385 words
Files
1
Skills in repo
103
Repo updated
First seen
Licence
MPL-2.0

At a glance

Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service.

  • Works in 5 steps: Identify which service actually handles… → Test the endpoint directly on each… → Check service logs for endpoint… → …
  • API endpoint returns 404 despite code being deployed
  • SKILL.md covers Problem, Context / Trigger Conditions, Solution and Verification, plus 2 more sections
  • Calls kubectl and gcloud; needs GORSE_API_KEY

What it does

Microservice API Endpoint Routing 404 is an agent skill from divinevideo/divine-mobile. Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service. Use when: (1) API endpoint returns 404 despite code being deployed, (2) Multiple services share same hostname via HTTPRoute/Ingress, (3) Service logs show "Health server" but you expected API endpoints, (4) Monorepo deploys multiple images and endpoint might be in different service than expected. Covers: verifying which service handles which paths, HTTPRoute path precedence, testing…

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering REST APIs, Microservices and Monorepo tooling. The licence is MPL-2.0.

When your agent uses it

  • API endpoint returns 404 despite code being deployed
  • Multiple services share same hostname via HTTPRoute/Ingress
  • Service logs show Health server but you expected API endpoints
  • Monorepo deploys multiple images and endpoint might be in different service than expected

Example prompts

  • “Health server”
  • “/microservice-api-endpoint-routing-404”

Requirements

  • Docker
  • A credential in GORSE_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify which service actually handles the path
  2. Test the endpoint directly on each service from inside cluster
  3. Check service logs for endpoint registration
  4. For monorepos, check if matching image exists for correct service
  5. Deploy the correct service with feature + required env vars

What it can do on your machine

Read from SKILL.md and the folder at commit c3d6f7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • kubectl
    • gcloud

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl and gcloud, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GORSE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Microservice API Endpoint Routing 404 loads about 1k tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 385 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from divinevideo/divine-mobile at commit c3d6f7e, republished under its MPL-2.0 licence (© divinevideo). 385 words, ~1,042 tokens.

Download SKILL.mdSave it as .claude/skills/microservice-api-endpoint-routing-404/SKILL.md (or your agent's skills folder).
name
microservice-api-endpoint-routing-404
description
Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service. Use when: (1) API endpoint returns 404 despite code being deployed, (2) Multiple services share same hostname via HTTPRoute/Ingress, (3) Service logs show "Health server" but you expected API endpoints, (4) Monorepo deploys multiple images and endpoint might be in different service than expected. Covers: verifying which service handles which paths, HTTPRoute path precedence, testing endpoints directly from inside cluster, matching image tags across services.
author
Claude Code
version
1.0.0
date
2026-01-29

Microservice API Endpoint Routing 404 Debugging

Problem

API endpoint returns 404 even though the code implementing it has been deployed. This commonly happens in microservice architectures where multiple services share the same hostname and HTTPRoutes/Ingress rules determine which service handles which paths.

Context / Trigger Conditions

  • New endpoint returns 404 but code is definitely deployed
  • Multiple services (e.g., relay + api) share the same external hostname
  • Service logs show "Health server listening" or similar health-only messages
  • HTTPRoute or Ingress rules split traffic by path prefix
  • Monorepo builds multiple Docker images from same commit

Solution

Step 1: Identify which service actually handles the path

Check HTTPRoute/Ingress rules to see routing:

bash
kubectl get httproute <name> -n <namespace> -o yaml | grep -A 50 "rules:"

Look for path matching rules and which backend service they point to:

  • /api/* might go to api-service:8080
  • / might go to websocket-service:7777
Step 2: Test the endpoint directly on each service from inside cluster
bash
kubectl run curl-test -n <namespace> --image=curlimages/curl --restart=Never \
  -- curl -v "http://<service-name>:<port>/<endpoint>" \
  && sleep 5 \
  && kubectl logs -n <namespace> curl-test \
  && kubectl delete pod -n <namespace> curl-test

This bypasses external routing and tests directly against each service.

Step 3: Check service logs for endpoint registration
bash
kubectl logs -l app=<service-name> -n <namespace> --tail=50 | grep -i -E "(endpoint|route|api|listening)"

Look for messages like:

  • "Health server listening on 0.0.0.0:8080" = health only, no API
  • "API server listening" or "Registered /api/..." = serves API endpoints
Step 4: For monorepos, check if matching image exists for correct service

If feature was added to service A but endpoint is served by service B, check if service B has the same commit tag:

bash
gcloud artifacts docker images list <registry>/<service-b> --include-tags --limit=10
Show full SKILL.md (170 more words)Show less
Step 5: Deploy the correct service with feature + required env vars

Update the service that actually handles the endpoint path:

  • New image tag with the feature
  • Any environment variables (API keys, URLs) the feature needs
  • Any secrets referenced by the feature

Verification

  1. Service logs show endpoint registered: "Recommendations API enabled at /api/users/:pubkey/recommendations"
  2. Direct curl from inside cluster returns 200
  3. External request through HTTPRoute returns expected data

Example

Architecture:

Hostname: relay.example.com
  /api/* → funnelcake-api:8080 (REST API)
  /      → funnelcake-relay:7777 (WebSocket)

Problem: /api/users/x/recommendations returns 404

Investigation:

  1. HTTPRoute shows /api/* → funnelcake-api (not relay)
  2. Direct test to relay:8080 returns 404 (health server only)
  3. Direct test to api:8080 also returns 404 (old image)
  4. Registry shows both api and relay have image tag 3c0696a
  5. API was running old tag 487178e

Fix: Deploy funnelcake-api with tag 3c0696a + GORSE_URL + GORSE_API_KEY env vars

Notes

  • Services in same namespace can share Kubernetes Secrets
  • Health endpoints (/livez, /readyz) are often on separate port from API
  • HTTPRoute path matching: more specific paths take precedence
  • Always check which service handles which paths before assuming endpoint location

© divinevideo, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/microservice-api-endpoint-routing-404 of divinevideo/divine-mobile.

Open the folder on GitHubat commit c3d6f7e

Compare with similar skills

Microservice API Endpoint Routing 404 next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Microservice API Endpoint Routing 404 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Microservice API Endpoint Routing 404 this skilldivinevideo/divine-mobile266—~1kAutomated safety check: PassMPL-2.0
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
Dr Jskilljdubois/dr-jskill342—~4.6kAutomated safety check: NotesApache-2.0
Hybrid Cloud Test Gengetsentry/sentry46k—~2.6kAutomated safety check: PassCustom licence
Vss Deploy Detection Tracking 2DNVIDIA/skills3.6k1 repos~4.5kAutomated safety check: PassApache-2.0
API Gatewayitsmostafa/aws-agent-skills1.2k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed

  • Dr Jskill

    jdubois/dr-jskill

    Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.

    342 GitHub stars~4.6k tokensUpdated 11 days ago
    Backend & APIsAuto-check: notes

  • Hybrid Cloud Test Gen

    getsentry/sentry

    Official

    Generate hybrid cloud tests for the Sentry codebase. An agent skill from getsentry/sentry.

    46k GitHub stars~2.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Vss Deploy Detection Tracking 2D

    NVIDIA/skills

    Official

    A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.

    3.6k GitHub starsUsed in 1 repo~4.5k tokens
    Backend & APIsAuto-check passed

  • API Gateway

    itsmostafa/aws-agent-skills

    AWS API Gateway for REST and HTTP API management. An agent skill from itsmostafa/aws-agent-skills.

    1.2k GitHub stars~2.2k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed

  • Add Function

    microbus-io/fabric

    TRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC, or a route that accepts typed arguments and returns typed results.

    172 GitHub stars~2.4k tokensUpdated 12 days ago
    Backend & APIsAuto-check passed

More from divinevideo/divine-mobile

All 103 skills in this repo

  • Argocd Externalsecret Namespace Permission

    divinevideo/divine-mobile

    Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".

    266 GitHub stars~931 tokensUpdated today
    Auto-check passed

  • Art Direct

    divinevideo/divine-mobile

    Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language.

    266 GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Async Await Null Race Condition

    divinevideo/divine-mobile

    Fix "Null check operator used on a null value" errors when an object is set to null during an async await.

    266 GitHub stars~881 tokensUpdated today
    Auto-check passed

  • AWS V4 Signing Custom Headers Gcs

    divinevideo/divine-mobile

    Add custom metadata headers (x-amz-meta-) to AWS v4 signed requests for GCS S3-compatible API.

    266 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Bash Herestring Newline Secrets

    divinevideo/divine-mobile

    Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings.

    266 GitHub stars~791 tokensUpdated today
    Auto-check passed

  • Blossom Content Addressed URL Filtering

    divinevideo/divine-mobile

    Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp).

    266 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Microservice API Endpoint Routing 404

What does Microservice API Endpoint Routing 404 do?

Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service. Microservice API Endpoint Routing 404 is an agent skill from divinevideo/divine-mobile. Debug 404 errors for API endpoints in microservice architectures where code exists but routing sends requests to wrong service.

When should I use Microservice API Endpoint Routing 404?

Microservice API Endpoint Routing 404 fits situations like: API endpoint returns 404 despite code being deployed; multiple services share same hostname via HTTPRoute/Ingress; service logs show Health server but you expected API endpoints; monorepo deploys multiple images and endpoint might be in different service than expected.

How do I install Microservice API Endpoint Routing 404 in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill microservice-api-endpoint-routing-404 -a claude-code`. Or copy the skill folder (.agents/skills/microservice-api-endpoint-routing-404 in divinevideo/divine-mobile) into .claude/skills/microservice-api-endpoint-routing-404 in your project. Claude Code loads it when a task matches its description.

How do I install Microservice API Endpoint Routing 404 in Codex?

Run `npx skills add divinevideo/divine-mobile --skill microservice-api-endpoint-routing-404 -a codex`. Or copy the skill folder (.agents/skills/microservice-api-endpoint-routing-404 in divinevideo/divine-mobile) into .agents/skills/microservice-api-endpoint-routing-404 in your project. Codex loads it when a task matches its description.

Can I use Microservice API Endpoint Routing 404 in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add divinevideo/divine-mobile --skill microservice-api-endpoint-routing-404 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/microservice-api-endpoint-routing-404, .gemini/skills/microservice-api-endpoint-routing-404, .github/skills/microservice-api-endpoint-routing-404 and .opencode/skills/microservice-api-endpoint-routing-404 in your project.

What does Microservice API Endpoint Routing 404 need to run?

Going by SKILL.md and its folder, Microservice API Endpoint Routing 404 needs the command-line tools its instructions call (kubectl and gcloud) and credentials named GORSE_API_KEY. Our summary lists: Docker; A credential in GORSE_API_KEY.

Does Microservice API Endpoint Routing 404 access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Microservice API Endpoint Routing 404 safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Microservice API Endpoint Routing 404 use?

Microservice API Endpoint Routing 404 is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Microservice API Endpoint Routing 404 use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Microservice API Endpoint Routing 404?

Skills that share tags, products or a category with Microservice API Endpoint Routing 404: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), Dr Jskill (jdubois/dr-jskill, 342 stars), Hybrid Cloud Test Gen (getsentry/sentry, 46k stars) and Vss Deploy Detection Tracking 2D (NVIDIA/skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Microservice API Endpoint Routing 404?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 10, 2026.

Source: divinevideo/divine-mobile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.