oh-chromium-knowledge

Routes ArkWeb feature queries to Chromium GitCode knowledge paths via token-based indexing and GitCode content API reads.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-chromium-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oh-chromium-knowledge
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/workflows/arkweb/.aceharness/skills/oh-chromium-knowledge
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-chromium-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of quickly finding the correct Chromium/ArkWeb knowledge for a specific ArkWeb feature, code analysis, or upgrade design decision without wasting time on manual searching.

Core Features & Use Cases

  • Feature-to-route retrieval: Uses a required routing/index-first workflow to locate the most relevant documents (e.g., routing table and module indices) for the requested ArkWeb capability.
  • Cross-repo architectural context: Provides repository metadata, architecture docs, and upgrade path references to ground code review and design discussions in the right versioned context.
  • Workflow-ready guidance for analysis/architect: Enables repeatable steps for arkweb-sdd flows by directing an agent to specific knowledge paths, including OHOS adaptation guidance when needed.

Quick Start

Use the skill to plan an ArkWeb code analysis by first loading index.json, then selecting the recommended file(s) from routing_table.json based on the feature name, and finally using the related repository architecture.md to explain the implementation context.

Frequently Asked Questions about oh-chromium-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Chromium architecture documents for an ArkWeb code analysis?

To perform an ArkWeb code analysis, you must first load the index.json file, then select recommended files from routing_table.json based on the feature name to locate the correct Chromium architecture documents.

What is the correct workflow for retrieving ArkWeb feature implementation details?

ArkWeb feature retrieval requires an index-first access order that prohibits bulk scanning. You use a routing table to locate specific knowledge paths, then read architecture documents to explain the implementation context.

Does this ArkWeb knowledge retrieval approach support Chromium version upgrade evaluation?

Yes, ArkWeb knowledge retrieval supports Chromium version upgrade evaluation by providing repository metadata, architecture docs, and upgrade path references to ground code review and design discussions in the correct versioned context.

Can I use a bulk scanning approach to search ArkWeb repositories for design tasks?

No, the ArkWeb retrieval workflow explicitly prohibits bulk scanning. You must follow an index-first access order using the routing table and module indices to find relevant documents for design and architect tasks.

Do I need a token to access Chromium routing tables and search indexes?

Yes, accessing Chromium routing tables and search indexes requires using the GitCode content API with token-based authorization to read routing tables, search indexes, and architecture documents across multiple repositories.