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

Dpis Hook API Routing

by Kwensiu in Kwensiu/DPIS

Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing.

GPL-3.0Auto-check passedDevelopment

Install Dpis Hook API Routing

skills CLI
$ npx skills add Kwensiu/DPIS --skill dpis-hook-api-routing -a claude-code

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

GitHub CLI
$ gh skill install Kwensiu/DPIS dpis-hook-api-routing --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/Kwensiu/DPIS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/agents/skills/dpis-hook-api-routing .claude/skills/dpis-hook-api-routing && 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
dpis-hook-api-routing
GitHub stars
111
Token cost
~1.8k tokens
SKILL.md length
893 words
Files
11 (incl. references, assets)
Skills in repo
6
Repo updated
First seen
Licence
GPL-3.0

At a glance

Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing.

  • Works in 7 steps: Classify the touched code as legacy,… → Identify the hook kind: method,… → Pick the owning flavor workflow → …
  • Debugging Legacy Xposed hooks
  • SKILL.md covers Trigger, Do Not Use, Required Reads and Core Rule, plus 6 more sections
  • Runs Java scripts from its folder

What it does

Dpis Hook API Routing is an agent skill from Kwensiu/DPIS. Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing. Use when implementing, reviewing, migrating, or debugging Legacy Xposed hooks, libxposed hooks, API 101 or 102 capability gating, modern/legacy flavor hook wiring, hook entry selection, or fallback behavior between old and new framework capabilities.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files and assets (for example `agents/openai.yaml`, `references/legacy.md` and `references/libxposed.md`).

It sits in Development. It works with Java. The repository describes itself as: 独立调节应用 DPI 与字体缩放 | Per-app DPI and font scaling. The licence is GPL-3.0.

When your agent uses it

  • Debugging Legacy Xposed hooks
  • Libxposed hooks
  • 102 capability gating
  • Modern/legacy flavor hook wiring

Example prompts

  • “/dpis-hook-api-routing”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Classify the touched code as legacy, modern, or shared.
  2. Identify the hook kind: method, resource, app-process, system_server,
  3. Pick the owning flavor workflow
  4. For Modern, prove the capability boundary before selecting a higher-capability
  5. If a capability is absent, choose an explicit fallback: API 101-compatible
  6. Implement the narrowest hook shape that preserves the flavor boundary.
  7. Verify entry, install, callback, visible effect, and fallback behavior with

What it can do on your machine

Read from SKILL.md and the folder at commit 9491f2c. 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

    Ships script files (Java), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Dpis Hook API Routing loads about 1.8k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 893 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

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 Kwensiu/DPIS at commit 9491f2c, republished under its GPL-3.0 licence (© Kwensiu). 893 words, ~1,824 tokens.

Download SKILL.mdSave it as .claude/skills/dpis-hook-api-routing/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
dpis-hook-api-routing
description
Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing. Use when implementing, reviewing, migrating, or debugging Legacy Xposed hooks, libxposed hooks, API 101 or 102 capability gating, modern/legacy flavor hook wiring, hook entry selection, or fallback behavior between old and new framework capabilities.

DPIS Hook API Routing

This is a project-local skill bundle. It keeps DPIS hook work aligned with the repository's split between pure Legacy Xposed behavior and Modern libxposed behavior, while making API 101 and 102 capability decisions explicit.

Trigger

Use this skill before work involving:

  • hook implementation under app/src/legacy/java/ or app/src/modern/java/
  • changes to shared runtime code that affects both hook stacks
  • migration from a Legacy-only pattern to a libxposed-capable pattern
  • deciding whether a new libxposed API should be used or gated off
  • diagnosing why a hook works on one framework/API level but not another
  • reviewing branch changes whose main risk is hook entry, install, callback, or framework API compatibility

Do Not Use

Do not use this skill for:

  • ordinary UI changes unrelated to runtime hooks
  • pure localization or documentation edits
  • general Java cleanup that does not alter hook behavior or API routing
  • route-policy diagnosis already covered by docs/agents/skills/dpis-runtime-route-diagnose/SKILL.md unless the task also requires API-family routing or hook-stack selection

Required Reads

Read only what applies to the task:

Core Rule

Treat legacy and modern as different hook families with different API contracts.

  • Keep Legacy pure. Do not force libxposed concepts into Legacy code just to unify style.
  • Keep Modern unified across libxposed capability levels, but only by explicit capability gating.
  • Do not use a newer libxposed API only because the source compiles. First prove that the target framework API level and capability surface permit it.
  • Every use of a newer API must have a fallback or a deliberate unsupported decision that is documented in code comments and the task summary.

Workflow

  1. Classify the touched code as legacy, modern, or shared.
  2. Identify the hook kind: method, resource, app-process, system_server, entry-point registration, or framework capability detection.
  3. Pick the owning flavor workflow:
    • Legacy: use the pure Legacy route in references/legacy.md.
    • Modern: use the libxposed family route in references/libxposed.md.
    • Shared: define the flavor boundary first, then read references/migration.md.
  4. For Modern, prove the capability boundary before selecting a higher-capability behavior.
  5. If a capability is absent, choose an explicit fallback: API 101-compatible behavior, manual validation step, or documented non-support.
  6. Implement the narrowest hook shape that preserves the flavor boundary.
  7. Verify entry, install, callback, visible effect, and fallback behavior with references/verification-checklist.md.

Decision Order

Make decisions in this order:

  1. Which flavor owns this behavior?
  2. Does the implementation belong in flavor-specific code or shared code?
  3. What is the minimum API surface needed for the desired behavior?
  4. Is that API surface guaranteed on the target framework?
  5. If not, what is the fallback: API 101-compatible behavior, Legacy behavior, manual validation, or explicit non-support?

Do not invert this order by starting from a preferred new API and searching for somewhere to force it in.

Show full SKILL.md (398 more words)Show less

Implementation Rules

  • Prefer flavor-specific code over shared branching when the behavior is truly different.
  • Prefer shared helpers only for stable concepts such as capability detection, planner decisions, or common config parsing.
  • If a helper mentions framework callback types, hook registration objects, or framework-owned lifecycle entry types, it is no longer semantic-only shared code.
  • Leave comments where the code chooses between API families or intentionally avoids a newer API. State the reason, not the obvious syntax.
  • When a higher API path is optional, make the fallback path readable and test worthy. Do not hide it behind reflection-heavy indirection unless the framework contract requires it.
  • When a framework or LSPosed UI exposes only one primary API version, do not assume that all runtime capability questions collapse to that label. Prove the capability actually used by the hook.
  • Do not copy Modern lifecycle timing assumptions into Legacy code. A behavior that installs around Application.attach(...) in Modern may still need a different Legacy-owned entry or callback boundary.

Capability Proof

Treat capability proven as a task-level gate, not a vibe.

For a newer Modern/libxposed API path, require all of these before enabling it:

  1. The framework exposes the required API version or capability signal.
  2. The exact feature used by the newer path is identified in the task or code comments.
  3. The API 101-safe path is still present and understandable.
  4. There is a concrete reason the newer path improves correctness, safety, or maintainability beyond style.
  5. Verification covers both the chosen higher-capability path and the fallback path, at least by tests, logs, or an explicit unsupported decision.

Version number alone is acceptable only when the newer feature is fully defined by that version boundary and the task does not rely on extra runtime probing for that specific API. If feature-specific runtime probing exists and is cheap, use it. If a capability is absent, do not silently continue through a partial higher-capability path.

Templates

Use the template snippets only as starting points:

Adapt naming, ownership, and comments to the touched module instead of copying the template shape verbatim.

Output

When finishing hook work or review, report:

  • flavor and hook family touched
  • whether the change is Legacy-only, Modern-only, or shared
  • which libxposed capability boundary was assumed or proven
  • fallback behavior when the new API is unavailable
  • tests, runtime checks, or log evidence used
  • docs or route records updated

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

Files

SKILL.md and 10 other files (references, assets) in docs/agents/skills/dpis-hook-api-routing of Kwensiu/DPIS.

  • SKILL.md
  • agents/openai.yaml
  • assets/legacy-method-hook-template.java
  • assets/legacy-resource-hook-template.java
  • assets/libxposed-101-hook-template.java
  • assets/libxposed-102-gated-hook-template.java
  • assets/shared-capability-gate-template.java
  • references/legacy.md
  • references/libxposed.md
  • references/migration.md
  • references/verification-checklist.md

Open the folder on GitHubat commit 9491f2c

Compare with similar skills

Dpis Hook API Routing 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.

Dpis Hook API Routing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dpis Hook API Routing this skillKwensiu/DPIS111—~1.8kAutomated safety check: PassGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Code Review Skillawesome-skills/code-review-skill2.1k—~2.8kAutomated safety check: NotesMIT
Caffeine Cache Optimization Experimentsben-manes/caffeine18k—~2.6kAutomated safety check: NotesApache-2.0
Coding Standardsapache/shardingsphere21k—~2.2kAutomated safety check: PassApache-2.0
Git History Bug Auditben-manes/caffeine18k—~3.3kAutomated safety check: PassApache-2.0

Similar skills

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Code Review Skill

    awesome-skills/code-review-skill

    Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…

    2.1k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • Caffeine Cache Optimization Experiments

    ben-manes/caffeine

    Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.

    18k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check: notes

  • Coding Standards

    apache/shardingsphere

    Apply Apache ShardingSphere's written coding standards when explicitly requested, or when code-implementation routes task-changed production, test, script, build, generated, or Maven POM artifacts…

    21k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Git History Bug Audit

    ben-manes/caffeine

    Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.

    18k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed

  • CI Act Run

    chewiebug/GCViewer

    Run the full build-and-deploy.yaml workflow locally via act + Docker.

    4.6k GitHub stars~2.4k tokensUpdated 3 mo ago
    DevelopmentAuto-check: notes

More from Kwensiu/DPIS

  • Dpis Hyperos Smoke

    Kwensiu/DPIS

    Run automated DPIS HyperOS device smoke tests for package-specific dp/font emulation or replacement.

    111 GitHub stars~715 tokensUpdated today
    Auto-check passed

  • Dpis Localization

    Kwensiu/DPIS

    Project-local DPIS localization workflow. An agent skill from Kwensiu/DPIS.

    111 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Dpis Release Notes

    Kwensiu/DPIS

    Rewrite DPIS release notes for ordinary users. An agent skill from Kwensiu/DPIS.

    111 GitHub stars~713 tokensUpdated today
    Auto-check passed

  • Dpis Precommit Review

    Kwensiu/DPIS

    Review DPIS changes before committing or opening a pull request, including scope, domain-rule compliance, tests, Android validation, SonarQube MCP checks, and Git hygiene.

    111 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Dpis Runtime Route Diagnose

    Kwensiu/DPIS

    Project-local DPIS runtime hook diagnosis workflow. An agent skill from Kwensiu/DPIS.

    111 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Dpis Hook API Routing

What does Dpis Hook API Routing do?

Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing. Dpis Hook API Routing is an agent skill from Kwensiu/DPIS. Project-local DPIS hook implementation and diagnosis workflow for Xposed API routing.

When should I use Dpis Hook API Routing?

Dpis Hook API Routing fits situations like: debugging Legacy Xposed hooks; libxposed hooks; 102 capability gating; modern/legacy flavor hook wiring.

How do I install Dpis Hook API Routing in Claude Code?

Run `npx skills add Kwensiu/DPIS --skill dpis-hook-api-routing -a claude-code`. Or copy the skill folder (docs/agents/skills/dpis-hook-api-routing in Kwensiu/DPIS) into .claude/skills/dpis-hook-api-routing in your project. Claude Code loads it when a task matches its description.

How do I install Dpis Hook API Routing in Codex?

Run `npx skills add Kwensiu/DPIS --skill dpis-hook-api-routing -a codex`. Or copy the skill folder (docs/agents/skills/dpis-hook-api-routing in Kwensiu/DPIS) into .agents/skills/dpis-hook-api-routing in your project. Codex loads it when a task matches its description.

Can I use Dpis Hook API Routing 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 Kwensiu/DPIS --skill dpis-hook-api-routing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dpis-hook-api-routing, .gemini/skills/dpis-hook-api-routing, .github/skills/dpis-hook-api-routing and .opencode/skills/dpis-hook-api-routing in your project.

What does Dpis Hook API Routing need to run?

Going by SKILL.md and its folder, Dpis Hook API Routing needs Java for the scripts in its folder.

Does Dpis Hook API Routing 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 Dpis Hook API Routing 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 Dpis Hook API Routing use?

Dpis Hook API Routing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dpis Hook API Routing use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.3k tokens, read only when the agent opens those files.

What are the alternatives to Dpis Hook API Routing?

Skills that share tags, products or a category with Dpis Hook API Routing: Creating Description For Gh PR (redis/jedis, 12k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Caffeine Cache Optimization Experiments (ben-manes/caffeine, 18k stars) and Coding Standards (apache/shardingsphere, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dpis Hook API Routing?

Kwensiu (a GitHub user) maintains it in Kwensiu/DPIS, which has 111 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

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