Interest Management
Use when the user asks about interest management, area of interest, network relevancy, network culling, replication priority or observer sets in multiplayer games. Produces visibility, priority and bandwidth budgeting design. Not for rendering culling (use render-graph) or matchmaking (use matchmaking-lobby).
Install
npx skills add j4flmao/agent-skills --skill interest-managementgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/game/game-server/interest-management ~/.claude/skills/interest-managementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Interest Management — Deep Engineering Guide
## Purpose
Nobody needs everything. A 100-player battle server could broadcast 6 MB/s to everyone — unviable. Interest management (IM) decides **who gets what**, at what rate, with the least CPU — turning O(players²) broadcast into near-O(visible) traffic.
## Agent Protocol
### Trigger
"interest management", "area of interest", "relevancy", "network culling", "replication priority", "observer set".
### Input Context
- Player and entity counts, world size
- Bandwidth budget per client
- Existing replication system
### Output Artifact
Interest/priority design and code. No file unless requested.
### Response Format
```
Relevancy: {grid | radius | PVS}
Budget: {bytes/s per client}
Priority: {formula}
Code: {snippet}
```
## 1. The Two Sides of the Problem
1. **State replication** — entity position/hp/anim may repeat at different rates.
2. **Event delivery** — spell casts, deaths, pickups happen once, must be reliable.
IM solves *state* (per-entity rate, per-observer mask). Events live in a separate **reliable queue** (see `references/event-queue.md`).
## 2. The Interest Model
```
observer O (a client)
interest(O) = { entities E : dist(O,E) <= radius && comesFrom(visibility(O,E)) && O.state needs }
```
Two classic models:
| Model | Idea | Cost |
|-------|------|------|
| **Spatial (distance/relevance)** | entities within radius get replicated | cheap; dumb (sees through walls) |Details
- Skill name
interest-management- Repository
- j4flmao/agent-skills
- Path
skills/game/game-server/interest-management/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Interest Management skill do?
Use when the user asks about interest management, area of interest, network relevancy, network culling, replication priority or observer sets in multiplayer games. Produces visibility, priority and bandwidth budgeting design. Not for rendering culling (use render-graph) or matchmaking (use matchmaking-lobby).
How do I install the Interest Management skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill interest-management. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Interest Management popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Zero Trust Identity
45j4flmao/agent-skills
Advanced Zero Trust Identity, OIDC/SAML Mechanics, and JWT Validation
Ecmwf Polytope
23ecmwf/ecmwf-weather-skills
Extracts just the data needed from ECMWF's operational forecasts with Polytope feature extraction — hourly point time series (meteograms), 50-member ensemble percentiles at a point, vertical profiles, polygons, bounding boxes, circles and trajectories — in kilobytes instead of downloading global fields. Use when the user has ECMWF credentials (POLYTOPE_USER_KEY, ~/.polytopeapirc or ~/.ecmwfapirc) and asks for a forecast, feels-like temperature or meteogram at a place, forecast uncertainty, ensemble spread, percentiles or likely ranges at a location (preferred over open-data for any ensemble qu
Meituan Living
9ysansan98/meituan-living
当用户提到优惠券、优惠、省钱、福利、活动,或想要吃饭(餐饮、奶茶、咖啡、火锅、烧烤、日料等),或问"附近有什么"、"去哪吃"、"今天有什么活动"时触发 —— 覆盖美团团购美食搜索、优惠券领取、餐饮和生活服务下单。
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.