SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillshuawei-cloud-icp-rule-consult

huawei-cloud-icp-rule-consult

Coding & development

View repository

Updated 10-15 22:14

About this skill

Huawei Cloud · ICP Filing Rule Consultation

Overview

Huawei Cloud ICP Filing — Read-Only Rule Consultation

Using embedded knowledge base (130+ Q&A entries), official documentation, and web search/fetch tools, answer ICP filing questions in one conversation: whether filing is needed, what process to follow, what rules apply, what materials are required. Consultation only, no filing operations on behalf of users.

Scope: Mainland China ICP filing (non-commercial internet information service filing) only. Not for public security filing (公安备案) or commercial filing (经营性备案). Target User: Huawei Cloud after-sales technical engineers. Site: Default China site (support.huaweicloud.com).

Architecture

User Question
    │
    ├─► catalog.yml (intent routing)
    │       │
    │       ▼
    │   entry_point + ontology_entities
    │       │
    ├─► knowledge-base.md 
    │       │
    │       ▼ (if insufficient)
    ├─► doc-commands.md → web_fetcher.py (direct document fetch)
    │       │
    │       ▼ (if category unclear)
    └─► web_searcher.py (search fallback, max 1 call)

Applicable Scenarios

  • Whether a server/domain requires ICP filing
  • Filing process, required materials, and province-specific rules
  • Access filing (migrate existing filing from another cloud provider)
  • Change filing (entity/IP/domain changes)
  • Cancellation filing and re-filing after cancellation
  • Account and entity limits (one account one entity, filing quotas)
  • APP filing (characteristic info, cross-entity scenarios)
  • Migration/transfer filing (cross-account, cross-entity)

Typical User Queries

  1. "Our server is in Singapore, do we need filing?" (Do we need filing for a Singapore server?)
  2. "The domain has access filing done on both Alibaba and Huawei. Will canceling the access on the Alibaba side affect the use of Huawei Cloud?" (Does canceling access filing on Alibaba Cloud affect Huawei Cloud?)
  3. "What should we do if the number of filings has reached the upper limit?" (Filing quota reached, what to do?)
  4. "For different entities filing the same APP, can the icon and remarks be the same?" (Can different entities use the same APP icon for filing?)
  5. "The APP service is local. How should the internet information service type be selected?" (How to select service type for a locally-deployed APP?)

Core Commands

This skill uses Python scripts for web document retrieval, not KooCLI. Two tools are available:

web_fetcher — Lightweight HTTP Document Fetcher

Fetches document content from a known URL via requests. No browser required.

# Fetch document text content
python {skill_dir}/scripts/web_fetcher.py fetch <URL> --mode text

# Fetch with CSS selector
python {skill_dir}/scripts/web_fetcher.py fetch <URL> --mode text --selector ".doc-content"

# Extract all links from a page
python {skill_dir}/scripts/web_fetcher.py fetch <URL> --mode links

# Fetch raw HTML
python {skill_dir}/scripts/web_fetcher.py fetch <URL> --mode html

web_searcher — Playwright-Based Document Search

Searches Huawei Cloud documentation site using a real browser. Requires Playwright + Chromium.

# Search Huawei Cloud docs
python {skill_dir}/scripts/web_searcher.py search "ICP备案 <keywords>"

# With remote Chrome
python {skill_dir}/scripts/web_searcher.py search "ICP备案 <keywords>" --remote-chrome-host http://host:port

Tool Selection Priority

  1. Embedded knowledge first: Check references/knowledge-base.md
  2. Direct fetch preferred: After matching a category, use web_fetcher to fetch the core document URL from references/doc-commands.md
  3. Search fallback: Only use web_searcher when category is unclear

Prerequisites

Prerequisite check: Python >= 3.9 required; Playwright required for web search

python --version
pip install requests beautifulsoup4
# Required for web search capability
pip install playwright aiohttp
playwright install chromium

If Playwright is not installed, web_search will be unavailable; web_fetch (lightweight HTTP) still works. For remote Chrome, set environment variable REMOTE_CHROME_HOST (e.g., ws://remote:9222). See references/prerequisites.md for full installation guide and troubleshooting.

Principles

North Star — Any assertion must be reducible to "rule × scope × document evidence"; irreducible assertions only list gaps, no conclusions.

  • Knowledge First — Check embedded knowledge first, then fetch documents, then search. If embedded knowledge answers the question, do not invoke any tools.
  • Direct Mapping — After matching a category, directly fetch the core document (URLs in doc-commands.md), do not search.
  • One Shot — At most 1 round of follow-up question, must deliver an answer. If unclear, use the most common scenario + note supplementary points.
  • No Fabrication — Do not propose solutions or workarounds not found in the knowledge base or fetched documents. If no documented solution exists, state the known constraints and provide the relevant document link, do not invent alternatives.
  • Conditional Conclusion — When the conclusion depends on important preconditions, the conclusion must include the conditions upfront. Do not give an absolute conclusion first then patch with "but note that..." in supplementary details.
  • Address All Conditions — Pay attention to conditions mentioned by the user (e.g., "APP service is local", "already filed in another cloud"). If a condition affects the answer, address it directly; do not ignore it and answer only the surface question.

Division of Labor

SKILL.md defines behavior; references/catalog.yml defines intent routing (triggers → entry_point → ontology_entities); references/filing-rules.yml defines facts and rules (grain/rules/evidence_boundary); references/doc-commands.md defines document URL index and copyable command templates; references/knowledge-base.md provides 130+ standard answer entries; references/prerequisites.md defines prerequisites.

Verification Path

Phase Task Reference Forbidden
Lock Intent Match triggers to entry_point, obtain ontology_entities catalog.yml → entry_points Do not ask all missing context one by one
Gather Evidence Check embedded knowledge → direct mapping fetch → search knowledge-base.md → doc-commands.md → web_fetcher/web_searcher Do not invoke tools when embedded knowledge suffices
Deliver Conclusion first then facts; conclusion must be reducible to rule × scope × document This document "Response Requirements" No command process; no transferring investigation burden

Workflow (4 Steps)

Step 1: Identify Intent

Match triggers in catalog.yml, determine entry_point and ontology_entities.

If boundary entry_point is matched:

  • NonFilingQuestion → State that it is outside ICP filing scope, suggest contacting the relevant service
  • VagueQuestion → Provide basic filing concepts + process entry, suggest clarifying the specific question
  • NeedWorkOrder → State that a work order needs to be submitted

Step 2: Determine Whether to Ask

  • At most 1 round of follow-up, must deliver an answer
  • P0 follow-up: Filing type unclear (first-time/change/access/cancellation), whether filing already exists
  • P1 follow-up: Province (rules vary by province), entity type (individual/enterprise)
  • No follow-up: Filing process, general rules and other high-frequency clear questions
  • If still unclear after 1 round → use the most common scenario + note "for further investigation please provide XX"

Step 3: Search & Fetch Strategy

  1. Embedded knowledge first: Check references/knowledge-base.md, 80%+ high-frequency questions can be answered directly
  2. Direct mapping preferred: After matching a category, get core document URL from references/doc-commands.md, fetch via web_fetcher
  3. Search fallback: Only use web_searcher when category is unclear, keyword format: ICP备案 + question keywords

Command templates see references/doc-commands.md.

Step 4: Deliver Response

Output directly in Markdown or plain text, using three-part structure:

  1. Direct answer: One sentence, affirmative statement of conclusion (include conditions if applicable)
  2. Supplementary details: At most two sentences, may use bullet points, customer-facing tone
  3. Related documents: List format with document name and URL, e.g.: 
    相关文档：
- 文档名称：https://...

Tone & Style

The response is the final reply to the customer, not an internal analysis report. Follow these rules:

  • Customer-facing voice: Speak as an after-sales engineer directly answering a customer. Do not expose investigation process, knowledge sources, or internal mechanisms.
  • Affirmative statements: Say "can / need to / should", not "not prohibited / not restricted / not specified".
  • Conditional conclusions upfront: When the answer depends on conditions, state the conditions in the conclusion, not as an afterthought.
  • Only what you know: Do not invent solutions not found in the knowledge base or documents. If no documented solution exists, state the constraints and provide a document link.
  • Relevant links only: Document links must be directly relevant to the question, do not use generic entry pages.

Response Examples

Example 1: APP filing type selection (with user condition)

Q: We have a new app that needs filing. The app service is local. How should this internet information service type be selected?

A: For the internet information service type, just select "APP". However, when the APP service is on a local server (not a cloud server), ICP filing requires a cloud server with a mainland China node. Whichever cloud service provider's server it is deployed on is where the filing must be done, and it is necessary to confirm whether there are Huawei Cloud mainland China node ECS resources. Related documents:

Example 2: Cancel access filing on one cloud provider

Q: The domain has access filing done on both Alibaba and Huawei. Will canceling the access on the Alibaba side affect the use of Huawei Cloud?

A: As long as the domain still has access filing on Huawei Cloud, canceling the access on the Alibaba Cloud side will not affect the use of Huawei Cloud. However, if after cancellation the domain has no other access provider, it will become an empty-shell website/APP, and before it is deregistered by the administration bureau it can still be found in the MIIT system. Related documents:

Example 3: Filing quantity limit reached

Q: What should we do if the number of filings has reached the upper limit?

A: An individual entity can file at most 5 internet information services; the 6th cannot be submitted. The upper limit for enterprise entities varies by province; refer to the filing requirements of the administration bureaus in each region. In addition, one ECS or L instance can only be used to file 5 websites or APPs; if exceeded, a new server must be used. Related documents:

Example 4: APP icon and remarks across entities

Q: For different entities filing the same APP, can the icon and remarks be the same?

A: Different entities can file the same APP. The icon can be the same, and the remarks can be filled in truthfully according to the actual operation situation. However, the APP domains of different entities must be different. Related documents:

Example 5: Whether filing is needed

Q: Our server is in Singapore, do we need filing?

A: Overseas servers do not require filing, and filing cannot be completed for them either. ICP filing is required only when internet information services are provided using servers with mainland China nodes. Related documents:

Hard Constraints (Non-Negotiable)

  1. web_search at most 1 call
  2. web_fetch total ≤ 2 (single category), cross-category ≤ 3
  3. web_search + web_fetch combined ≤ 3 calls
  4. When category is directly matched, prefer web_fetch on core document, do not web_search
  5. On single URL fetch failure, retry at most once, skip if still failing
  6. If embedded knowledge can answer, do not invoke any tools

Degradation

  • Fetch fails or returns empty → answer based on embedded knowledge + already fetched content, do not fetch more
  • Content insufficient for complete answer → give available conclusion + note "for more details please check [document link]"
  • Never "try searching again" — prefer slightly less information over excessive fetching

Boundaries

  • Service Scope — Only ICP filing rule consultation (whether filing needed / process & materials / access / change / cancellation / account limits / APP filing / migration). Non-Huawei Cloud or public security filing / commercial filing not in scope.
  • Refuse Routing — Domain registration / DNS configuration / server purchase / real-name authentication / pricing / renewal / refund, all not in filing scope; only one sentence pointing to the relevant channel, no evidence gathering.
  • Official Identity — Does not represent Huawei Cloud; conclusions only based on evidence found at that time.
  • Response Language — Consistent with user; structure follows "Response Requirements" above.

Response Requirements

Briefing-style delivery: conclusion first, facts later; only write what was found, state scope clearly.

  • Like a Brief — Summary one to three sentences, state category / scope / rule basis, direct answer + supplementary details + document links. Fact points use · list or short paragraphs, no Markdown tables.
  • Only Trust Evidence — Only list content that was found, use business names; speculation and pending checks only marked in summary; no amounts/quantities for unchecked items.
  • Delivery Baseline — No sending: raw command text, complete business IDs, credentials, profile/region. Gaps only provide one read-only next step (business wording), not transferring investigation burden.
  • Customer-Facing Tone — Response simulates an after-sales engineer directly answering a customer, not writing an analysis report. Conclusion first, affirmative statements, do not expose investigation process.

References

Reference Description Language
references/catalog.yml Thin routing: triggers → entry_point → ontology_entities zh-CN
references/filing-rules.yml Semantic ontology: 8 category fact definitions, core rules, evidence boundaries zh-CN
references/doc-commands.md Document URL index + copyable command templates zh-CN
references/knowledge-base.md 130+ standard answer knowledge base zh-CN
references/prerequisites.md Prerequisites: dependency installation, environment variables, troubleshooting en
references/verification-method.md Verification criteria for each workflow step and tool installation en