[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAV9GQ9P1FH18AW69JFS43":3,"skill-same:01M7DAV9GQ9P1FH18AW69JFS43":213},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7DAV9GQ9P1FH18AW69JFS43","hotspot-radar-workflow-skill",null,"alicewe1\u002Falice_skill","alicewe1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F102134151?v=4","01M7D9STCM8HAESM958JP0989K","Alice_we","01M7D9STDR22MTD9FTTWPAZNV8",64,"MIT","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hotspot-radar-workflow\ndescription: Use when the user gives a content theme or niche and wants Douyin benchmark accounts, benchmark content, evidence-backed topic candidates, and an owner checklist for do\u002Fobserve\u002Fdo-not decisions.\nlicense: MIT\nmetadata:\n  version: \"0.1.1\"\n  author: \"Dalin AI Works\"\nx-alice-class: assist\n---# Hotspot Radar Workflow\n\n## Role\n\nAct as the internal \"热点雷达\" workflow controller.\n\nGiven a content direction, run or guide the radar workflow:\n\n`theme -> keyword expansion -> Douyin candidate fetch -> normalization -> metrics and comment evidence -> opportunity scoring -> 10-topic owner checklist -> owner do\u002Fobserve\u002Fdo-not review -> rule calibration`\n\nThe goal is not to collect every hotspot or generate finished scripts. The goal is to find high-interaction, account-fit, evidence-backed benchmark content that can become a short list of topic opportunities for the owner to judge.\n\n## Use When\n\nUse this Skill when the user asks to:\n\n- find domestic short-video hotspot\u002Ftopic candidates for a theme;\n- validate a content niche such as AI, Codex, Skill, AI automation, real projects, or content workflow;\n- use existing TikHub access to search Douyin candidates;\n- score candidate content with likes, comments, favorites, shares, fit, transferability, and risk;\n- output a simple 10-topic owner checklist for \"要做 \u002F 可观察 \u002F 不要做\";\n- continue Gate 1 hotspot-radar workflow validation.\n\n## Do Not Use When\n\nDo not use this Skill for:\n\n- Web MVP, Next.js UI, desktop app, authorization, SaaS, or commercial packaging;\n- automatic publishing, editing, video rendering, or talking-head production;\n- claims that a topic is guaranteed viral;\n- direct synonym-level rewriting or \"洗稿\";\n- downloading videos, bypassing login, ASR\u002FOCR, or scraping beyond the authorized API path;\n- showing or exporting internal reports, API keys, raw crawl data, candidate tables, scoring JSON, or source creators' media as public video material;\n- treating script quality, conversion, filming, or publishing performance as the radar's first-stage acceptance gate.\n\n## Required Inputs\n\nIf missing, infer conservatively only when safe. Ask only when the missing item would change the workflow materially.\n\n- `theme`: content direction, for example `AI 自动化真实项目`.\n- `target_audience`: audience served by the account.\n- `content_goal`: trust, followers, series validation, education, leads, etc.\n- `primary_platform`: Gate 1 defaults to Douyin.\n- `owned_cases`: the owner's projects, views, skills, or real cases that can support original content.\n- `forbidden_directions`: exaggerated income, copying, internal data, unverified tools, sensitive claims.\n\nOptional:\n\n- `seed_keywords`\n- `max_requests`, default 25\n- `content_formats`, default oral short video first\n- `must_include_view`\n- `exclude_keywords`\n\n## Default Assumptions\n\nWhen the user does not specify otherwise:\n\n- Platform: Douyin.\n- Theme family: AI \u002F Codex \u002F Skill \u002F AI workflow \u002F real projects.\n- Owner audience: people using AI to make content, projects, workflows, and real useful things.\n- Request budget: 25 TikHub requests per run.\n- Public output: no internal reports, raw data, keys, screenshots, creator media, or comment identities.\n- Owner-facing default output: topic checklist, not full script.\n\n## Prerequisite Check\n\nBefore every real fetch, run the first-run check or token preflight.\n\nFor a shared Skill package, prefer:\n\n`node scripts\u002Ffirst-run-check.mjs`\n\nThe first-run check verifies Node.js, TikHub API base URL, local Token availability, and required scripts.\n\nRun:\n\n`node scripts\u002Frun-gate1-topic-validation.mjs --check-token`\n\nIf `ok: false`, stop and ask the owner to provide a TikHub API Token. Do not continue to mock or stale data unless the owner explicitly asks for a no-fetch dry run.\n\nFirst-time setup:\n\n1. Open TikHub dashboard: `https:\u002F\u002Fuser.tikhub.io\u002Fdashboard\u002Fapi`\n2. Copy the API Token.\n3. Run `node scripts\u002Fsetup-tikhub-token.mjs`.\n4. Paste the Token into the prompt and press Enter. Interactive input should be hidden by the terminal.\n5. Re-run `node scripts\u002Ffirst-run-check.mjs`.\n\nThe default API base URL is `https:\u002F\u002Fapi.tikhub.io`. Only use another base URL when the owner explicitly approves that exact domain.\n\nToken storage rules:\n\n- Prefer macOS Keychain service `hotspot_radar_tikhub_api_token` with the current local account.\n- Keep backward compatibility with legacy service `ai_anget_tikhub_api_token` and account `dalin`.\n- `TIKHUB_API_KEY` may be used for a temporary shell session, but it disappears when that session ends.\n- Never write API Keys into project files, reports, logs, Git, screenshots, or public Skill packages.\n- If the terminal still echoes Token input in a specific environment, stop and use a safer local terminal path before sharing the screen or logs.\n\n## Workflow\n\n### 0. User-Facing Usage\n\nThe simplest usage is one theme in, one owner checklist out:\n\n`node scripts\u002Frun-topic-checklist.mjs \"AI 自动化真实项目\"`\n\nThe user only needs to provide one broad content direction, such as:\n\n- `AI 自动化真实项目`\n- `Codex Skill 工作流`\n- `母婴睡眠`\n- `本地生活探店`\n\nThe Skill then:\n\n1. checks whether TikHub Token is available;\n2. expands the theme into 6 to 8 enabled search keywords;\n3. searches Douyin candidate content through TikHub;\n4. normalizes likes, comments, favorites, shares, author, title, description, source keyword, and missing fields;\n5. scores each candidate with content opportunity score;\n6. excludes same-theme candidates already returned in previous runs;\n7. outputs a 10-topic checklist for `要做 \u002F 可观察 \u002F 不要做`.\n\nWhen the user gives only one keyword or theme, do not ask them to manually provide expanded keywords unless the first run is clearly off-track.\n\n### 1. Establish TrackBrief\n\nCreate a concise TrackBrief:\n\n- theme;\n- target audience;\n- content goal;\n- platform;\n- owned cases;\n- forbidden directions;\n- request budget;\n- run id.\n\n### 2. Expand Keywords\n\nGenerate 6 to 8 enabled keywords.\n\nExpansion means the user does not need to know every search term. For example:\n\nInput theme: `AI 自动化真实项目`\n\nPossible enabled keywords:\n\n- `AI 自动化真实项目`\n- `AI 做项目`\n- `一个人 AI 工作流`\n- `AI 项目复盘`\n- `AI 工作流 保姆级教程`\n- `Codex 项目实战`\n- `Codex 工作流`\n- `Skill 工作流`\n\nEach keyword should have a reason and status. Status can be `enabled`, `candidate`, or `paused`. Only `enabled` keywords are fetched in the current run.\n\nPrefer:\n\n- Codex project;\n- Skill workflow;\n- AI real project;\n- AI content production line;\n- one-person AI workflow;\n- AI project review;\n- tool-specific terms only when the owner has evidence or can avoid tool review claims.\n\nAvoid or downweight:\n\n- AI making money;\n- AI side hustle;\n- replacing jobs;\n- violent income claims;\n- generic AI news;\n- film\u002Fvisual effects if not tied to Codex\u002FSkill\u002Freal projects.\n\n### 3. Fetch Candidates\n\nFor a real run, use the lower-level project script when intermediate files need inspection:\n\n`node scripts\u002Frun-gate1-topic-validation.mjs \u003Crun-id> '\u003Ctheme>'`\n\nFor a shared Skill package, prefer the simpler end-to-end entry:\n\n`node scripts\u002Frun-topic-checklist.mjs \"\u003Ctheme>\"`\n\nImportant:\n\n- Run from the repository root or installed skill root.\n- Use the preflight token check first.\n- Do not print or store secrets.\n- Default endpoint is `https:\u002F\u002Fapi.tikhub.io`.\n- Do not send the token to an alternative domain unless the user explicitly approves that exact domain.\n- Do not download videos.\n- Do not publish or call video production.\n\nExpected outputs:\n\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fkeywords\u002Fkeyword-nodes.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fraw\u002Fsearch\u002F`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fraw\u002Fcomments\u002F`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fnormalized\u002Fcontent-candidates.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fscores\u002Fopportunity-scores.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fanalyses\u002Fstructured-analyses.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Flogs\u002Frun-log.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Flogs\u002Ffailure-summary.json`\n- `reports\u002Fgate-1\u002F\u003Crun-id>-candidate-selection-report.md`\n\n### 4. Score Candidates\n\nUse \"content opportunity score\", not viral score.\n\nSuggested v0.1 weights:\n\n- basic metrics: 25\n- user demand: 15\n- track relevance: 20\n- account fit: 20\n- transferability: 15\n- structure clarity: 8\n- freshness: 4\n- evidence completeness: 3\n- risk penalty: up to -30\n\nMissing play count, completion rate, follower count, transcript, or OCR must be marked as missing. Do not fake them as valid zeros.\n\n### 5. Filter With Judgment\n\nDo not mechanically accept Top 1 to Top 5.\n\nDownweight even high-data candidates when:\n\n- topic is off-account, such as factory automation unrelated to AI\u002FCodex\u002FSkill content;\n- income claim is exaggerated;\n- content depends on source creator's personal story;\n- content requires copying screenshots, music, visuals, comments, or unique expression;\n- tool review would require unverified hands-on use.\n\nPrefer candidates that:\n\n- have strong metrics or strong comment demand;\n- fit AI\u002FCodex\u002FSkill\u002Freal-project positioning;\n- can be rebuilt with owner's own project or process;\n- can become oral explanation, screen-recording demo, or abstract workflow content;\n- have clear \"cannot copy\" boundaries.\n\nRecording samples must pass a stricter evidence gate than A\u002FB candidates:\n\n- score is at least the A-tier threshold;\n- has minimum interaction volume;\n- has comment evidence and demand comments, or very strong interaction;\n- confidence estimate is at least `0.55`;\n- account fit is acceptable;\n- does not rely on copying source creator materials.\n\nLow-interaction, no-comment, low-confidence candidates may stay in the candidate pool or owner-view pool, but must not automatically enter recording packages.\n\nWhen selecting Top 3 recording samples, keep angle diversity where possible:\n\n- Skill\u002Fworkflow;\n- Codex usage or onboarding;\n- content\u002Fvideo workflow;\n- real project case.\n\n### 6. Generate Owner Checklist\n\nDefault Gate 1A output is a 10-topic checklist.\n\nUse the helper when a score file already exists:\n\n`node scripts\u002Fbuild-gate1a-owner-review.mjs \u003Csource-run-id> reports\u002Fgate-1\u002F\u003Crun-id>-owner-review-checklist.md`\n\nThe checklist must include:\n\n- 10 candidate topics;\n- recommendation level: `S`, `A`, `B`, `C`, or `Noise`;\n- metrics: likes, comments, favorites, shares;\n- short recommendation reason;\n- missing data and risk;\n- owner checkbox: `[ ] 要做  [ ] 可观察  [ ] 不要做`.\n\nSame-theme dedupe is required:\n\n- The helper records returned candidates in `data\u002Fgate-1\u002Fowner-review-history.json`.\n- On the next run with the same normalized theme, previously returned `candidate_id` and near-duplicate topic fingerprints are excluded.\n- If fewer than 10 new candidates remain, output fewer and say the same-theme candidate pool is exhausted; do not refill with old topics unless the owner explicitly asks.\n- Use `--no-history` only for debugging or reproducing an old report.\n\nThe owner should only need to judge the checklist. Do not ask the owner to inspect raw JSON, sort metrics, or approve every scoring detail.\n\nGate 1A passes when one run has 3 to 5 `要做` items, and is stable when two comparable runs reach that bar.\n\n### 7. Optional Downstream Creation\n\nOnly after the owner marks topics as `要做`, downstream content skills may generate briefs, scripts, recording plans, or conversion routes.\n\nThese outputs belong to content production, not radar acceptance.\n\n### 7.1 Generate Creation Briefs\n\nBefore writing briefs, generate one structured analysis per selected recording candidate.\n\nThe structured analysis must include:\n\n- user problem;\n- retention reason;\n- borrowable structure;\n- do-not-copy boundaries;\n- original angle;\n- owner-owned case;\n- three recreation routes;\n- title options;\n- cover copy options;\n- evidence used;\n- evidence limitations;\n- confidence and confidence reason;\n- risk notes.\n\nUse OpenAI only when `HOTSPOT_AI_ANALYSIS=1` or `--ai-analysis` is explicitly set and `OPENAI_API_KEY` exists. If OpenAI is disabled, missing, or fails, use the heuristic fallback and record the provider reason. Do not let AI analysis failure break candidate selection.\n\nFor selected candidates, output three routes when useful:\n\n1. Same pain point, different viewpoint.\n2. Same structure, owner's own case.\n3. Hotspot joined with a real project.\n\nEach brief must include:\n\n- source candidate and metrics;\n- what can be borrowed;\n- what cannot be copied;\n- owner-owned case;\n- original angle;\n- target audience;\n- title options;\n- risk notes;\n- evidence limitations.\n\n### 7.2 Generate Recording Packages\n\nOnly for candidates confirmed as worth doing or for validation samples.\n\nRecording package includes:\n\n- recommended title;\n- cover copy;\n- teleprompter script;\n- short shot plan;\n- required shots;\n- subtitle highlights;\n- forbidden materials;\n- pinned comment suggestion;\n- owner review gate.\n\nMark:\n\n- `publish_ready: false`\n- `status: recording_material_ready_for_owner_review`\n\nDo not call `talking-head-video-production` unless the user explicitly asks to enter actual filming\u002Fproduction.\n\n### 7.5 Review Data Source Failures\n\nEvery real run must preserve a failure summary.\n\nClassify failed or weak requests as:\n\n- `network_error`: local\u002Fnetwork\u002FAPI host unreachable;\n- `http_error`: HTTP 4xx or 5xx;\n- `api_error`: API returned a non-success code;\n- `parse_error`: response was not valid JSON;\n- `field_shape_changed`: expected result arrays are missing;\n- `empty_result`: request succeeded but produced zero usable candidates or comments.\n\nUse this to decide whether a bad run was caused by the theme, the keyword set, API stability, quota\u002Fauth, or response field changes. Do not hide these failures behind a low candidate count.\n\n### 8. Owner Review Gate\n\nThe owner should only need to judge:\n\n- whether the theme direction is right;\n- which Top candidates are `要做 \u002F 可观察 \u002F 不要做`.\n\nDo not require the owner to manually:\n\n- sort metrics;\n- inspect raw JSON;\n- write scoring reasons;\n- approve every small step.\n- judge script quality before radar acceptance.\n\n### 9. Review And Calibrate\n\nEnd every run with a concise workflow review:\n\n- search success;\n- comment success;\n- candidate count;\n- selected count;\n- accepted candidates;\n- rejected or risky candidates;\n- scoring issues;\n- keyword adjustments;\n- next run recommendation.\n\n## Current Known Project Facts\n\nAs of 2026-08-05:\n\n- Gate 0 has validated Douyin search\u002Fdetail\u002Fcomment availability with limitations.\n- Gate 1 round 2 produced 82 deduplicated candidates and 20 A\u002FB candidates.\n- Owner selected ranks 6, 11, and 4; all three were later judged worth recording.\n- A new topic rerun for `AI 自动化真实项目` produced 117 deduplicated candidates and 20 A\u002FB candidates.\n- `sort_type` and `publish_time` must be strings for the current TikHub endpoint.\n- Web MVP is not ready.\n- This Skill may be drafted\u002Fused for workflow validation, but should not imply commercial product readiness.\n\n## Output Style\n\nPrefer:\n\n- Chinese;\n- concise but evidence-backed;\n- direct decisions when the evidence is enough;\n- clear \"do \u002F do not \u002F wait\" boundaries;\n- file outputs for reusable reports and packages.\n\nAvoid:\n\n- saying the owner is right by default;\n- calling candidates \"viral\" when play\u002Fcompletion\u002Ffollower data are missing;\n- burying risk caveats;\n- producing long generic marketing copy without evidence;\n- step-by-step confirmation for every small artifact.\n\n## Completion Criteria\n\nA successful run should produce:\n\n- candidate report;\n- structured scores;\n- 10-topic owner checklist;\n- owner review fields;\n- workflow review and rule adjustments;\n- no leakage of secrets or internal data;\n- no claim of publishing, Web MVP, script readiness, recording readiness, or Skill installation unless actually done.\n","## Role\n\nAct as the internal \"热点雷达\" workflow controller.\n\nGiven a content direction, run or guide the radar workflow:\n\n`theme -> keyword expansion -> Douyin candidate fetch -> normalization -> metrics and comment evidence -> opportunity scoring -> 10-topic owner checklist -> owner do\u002Fobserve\u002Fdo-not review -> rule calibration`\n\nThe goal is not to collect every hotspot or generate finished scripts. The goal is to find high-interaction, account-fit, evidence-backed benchmark content that can become a short list of topic opportunities for the owner to judge.\n\n## Use When\n\nUse this Skill when the user asks to:\n\n- find domestic short-video hotspot\u002Ftopic candidates for a theme;\n- validate a content niche such as AI, Codex, Skill, AI automation, real projects, or content workflow;\n- use existing TikHub access to search Douyin candidates;\n- score candidate content with likes, comments, favorites, shares, fit, transferability, and risk;\n- output a simple 10-topic owner checklist for \"要做 \u002F 可观察 \u002F 不要做\";\n- continue Gate 1 hotspot-radar workflow validation.\n\n## Do Not Use When\n\nDo not use this Skill for:\n\n- Web MVP, Next.js UI, desktop app, authorization, SaaS, or commercial packaging;\n- automatic publishing, editing, video rendering, or talking-head production;\n- claims that a topic is guaranteed viral;\n- direct synonym-level rewriting or \"洗稿\";\n- downloading videos, bypassing login, ASR\u002FOCR, or scraping beyond the authorized API path;\n- showing or exporting internal reports, API keys, raw crawl data, candidate tables, scoring JSON, or source creators' media as public video material;\n- treating script quality, conversion, filming, or publishing performance as the radar's first-stage acceptance gate.\n\n## Required Inputs\n\nIf missing, infer conservatively only when safe. Ask only when the missing item would change the workflow materially.\n\n- `theme`: content direction, for example `AI 自动化真实项目`.\n- `target_audience`: audience served by the account.\n- `content_goal`: trust, followers, series validation, education, leads, etc.\n- `primary_platform`: Gate 1 defaults to Douyin.\n- `owned_cases`: the owner's projects, views, skills, or real cases that can support original content.\n- `forbidden_directions`: exaggerated income, copying, internal data, unverified tools, sensitive claims.\n\nOptional:\n\n- `seed_keywords`\n- `max_requests`, default 25\n- `content_formats`, default oral short video first\n- `must_include_view`\n- `exclude_keywords`\n\n## Default Assumptions\n\nWhen the user does not specify otherwise:\n\n- Platform: Douyin.\n- Theme family: AI \u002F Codex \u002F Skill \u002F AI workflow \u002F real projects.\n- Owner audience: people using AI to make content, projects, workflows, and real useful things.\n- Request budget: 25 TikHub requests per run.\n- Public output: no internal reports, raw data, keys, screenshots, creator media, or comment identities.\n- Owner-facing default output: topic checklist, not full script.\n\n## Prerequisite Check\n\nBefore every real fetch, run the first-run check or token preflight.\n\nFor a shared Skill package, prefer:\n\n`node scripts\u002Ffirst-run-check.mjs`\n\nThe first-run check verifies Node.js, TikHub API base URL, local Token availability, and required scripts.\n\nRun:\n\n`node scripts\u002Frun-gate1-topic-validation.mjs --check-token`\n\nIf `ok: false`, stop and ask the owner to provide a TikHub API Token. Do not continue to mock or stale data unless the owner explicitly asks for a no-fetch dry run.\n\nFirst-time setup:\n\n1. Open TikHub dashboard: `https:\u002F\u002Fuser.tikhub.io\u002Fdashboard\u002Fapi`\n2. Copy the API Token.\n3. Run `node scripts\u002Fsetup-tikhub-token.mjs`.\n4. Paste the Token into the prompt and press Enter. Interactive input should be hidden by the terminal.\n5. Re-run `node scripts\u002Ffirst-run-check.mjs`.\n\nThe default API base URL is `https:\u002F\u002Fapi.tikhub.io`. Only use another base URL when the owner explicitly approves that exact domain.\n\nToken storage rules:\n\n- Prefer macOS Keychain service `hotspot_radar_tikhub_api_token` with the current local account.\n- Keep backward compatibility with legacy service `ai_anget_tikhub_api_token` and account `dalin`.\n- `TIKHUB_API_KEY` may be used for a temporary shell session, but it disappears when that session ends.\n- Never write API Keys into project files, reports, logs, Git, screenshots, or public Skill packages.\n- If the terminal still echoes Token input in a specific environment, stop and use a safer local terminal path before sharing the screen or logs.\n\n## Workflow\n\n### 0. User-Facing Usage\n\nThe simplest usage is one theme in, one owner checklist out:\n\n`node scripts\u002Frun-topic-checklist.mjs \"AI 自动化真实项目\"`\n\nThe user only needs to provide one broad content direction, such as:\n\n- `AI 自动化真实项目`\n- `Codex Skill 工作流`\n- `母婴睡眠`\n- `本地生活探店`\n\nThe Skill then:\n\n1. checks whether TikHub Token is available;\n2. expands the theme into 6 to 8 enabled search keywords;\n3. searches Douyin candidate content through TikHub;\n4. normalizes likes, comments, favorites, shares, author, title, description, source keyword, and missing fields;\n5. scores each candidate with content opportunity score;\n6. excludes same-theme candidates already returned in previous runs;\n7. outputs a 10-topic checklist for `要做 \u002F 可观察 \u002F 不要做`.\n\nWhen the user gives only one keyword or theme, do not ask them to manually provide expanded keywords unless the first run is clearly off-track.\n\n### 1. Establish TrackBrief\n\nCreate a concise TrackBrief:\n\n- theme;\n- target audience;\n- content goal;\n- platform;\n- owned cases;\n- forbidden directions;\n- request budget;\n- run id.\n\n### 2. Expand Keywords\n\nGenerate 6 to 8 enabled keywords.\n\nExpansion means the user does not need to know every search term. For example:\n\nInput theme: `AI 自动化真实项目`\n\nPossible enabled keywords:\n\n- `AI 自动化真实项目`\n- `AI 做项目`\n- `一个人 AI 工作流`\n- `AI 项目复盘`\n- `AI 工作流 保姆级教程`\n- `Codex 项目实战`\n- `Codex 工作流`\n- `Skill 工作流`\n\nEach keyword should have a reason and status. Status can be `enabled`, `candidate`, or `paused`. Only `enabled` keywords are fetched in the current run.\n\nPrefer:\n\n- Codex project;\n- Skill workflow;\n- AI real project;\n- AI content production line;\n- one-person AI workflow;\n- AI project review;\n- tool-specific terms only when the owner has evidence or can avoid tool review claims.\n\nAvoid or downweight:\n\n- AI making money;\n- AI side hustle;\n- replacing jobs;\n- violent income claims;\n- generic AI news;\n- film\u002Fvisual effects if not tied to Codex\u002FSkill\u002Freal projects.\n\n### 3. Fetch Candidates\n\nFor a real run, use the lower-level project script when intermediate files need inspection:\n\n`node scripts\u002Frun-gate1-topic-validation.mjs \u003Crun-id> '\u003Ctheme>'`\n\nFor a shared Skill package, prefer the simpler end-to-end entry:\n\n`node scripts\u002Frun-topic-checklist.mjs \"\u003Ctheme>\"`\n\nImportant:\n\n- Run from the repository root or installed skill root.\n- Use the preflight token check first.\n- Do not print or store secrets.\n- Default endpoint is `https:\u002F\u002Fapi.tikhub.io`.\n- Do not send the token to an alternative domain unless the user explicitly approves that exact domain.\n- Do not download videos.\n- Do not publish or call video production.\n\nExpected outputs:\n\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fkeywords\u002Fkeyword-nodes.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fraw\u002Fsearch\u002F`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fraw\u002Fcomments\u002F`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fnormalized\u002Fcontent-candidates.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fscores\u002Fopportunity-scores.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Fanalyses\u002Fstructured-analyses.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Flogs\u002Frun-log.json`\n- `data\u002Fgate-1\u002Fruns\u002F\u003Crun-id>\u002Flogs\u002Ffailure-summary.json`\n- `reports\u002Fgate-1\u002F\u003Crun-id>-candidate-selection-report.md`\n\n### 4. Score Candidates\n\nUse \"content opportunity score\", not viral score.\n\nSuggested v0.1 weights:\n\n- basic metrics: 25\n- user demand: 15\n- track relevance: 20\n- account fit: 20\n- transferability: 15\n- structure clarity: 8\n- freshness: 4\n- evidence completeness: 3\n- risk penalty: up to -30\n\nMissing play count, completion rate, follower count, transcript, or OCR must be marked as missing. Do not fake them as valid zeros.\n\n### 5. Filter With Judgment\n\nDo not mechanically accept Top 1 to Top 5.\n\nDownweight even high-data candidates when:\n\n- topic is off-account, such as factory automation unrelated to AI\u002FCodex\u002FSkill content;\n- income claim is exaggerated;\n- content depends on source creator's personal story;\n- content requires copying screenshots, music, visuals, comments, or unique expression;\n- tool review would require unverified hands-on use.\n\nPrefer candidates that:\n\n- have strong metrics or strong comment demand;\n- fit AI\u002FCodex\u002FSkill\u002Freal-project positioning;\n- can be rebuilt with owner's own project or process;\n- can become oral explanation, screen-recording demo, or abstract workflow content;\n- have clear \"cannot copy\" boundaries.\n\nRecording samples must pass a stricter evidence gate than A\u002FB candidates:\n\n- score is at least the A-tier threshold;\n- has minimum interaction volume;\n- has comment evidence and demand comments, or very strong interaction;\n- confidence estimate is at least `0.55`;\n- account fit is acceptable;\n- does not rely on copying source creator materials.\n\nLow-interaction, no-comment, low-confidence candidates may stay in the candidate pool or owner-view pool, but must not automatically enter recording packages.\n\nWhen selecting Top 3 recording samples, keep angle diversity where possible:\n\n- Skill\u002Fworkflow;\n- Codex usage or onboarding;\n- content\u002Fvideo workflow;\n- real project case.\n\n### 6. Generate Owner Checklist\n\nDefault Gate 1A output is a 10-topic checklist.\n\nUse the helper when a score file already exists:\n\n`node scripts\u002Fbuild-gate1a-owner-review.mjs \u003Csource-run-id> reports\u002Fgate-1\u002F\u003Crun-id>-owner-review-checklist.md`\n\nThe checklist must include:\n\n- 10 candidate topics;\n- recommendation level: `S`, `A`, `B`, `C`, or `Noise`;\n- metrics: likes, comments, favorites, shares;\n- short recommendation reason;\n- missing data and risk;\n- owner checkbox: `[ ] 要做  [ ] 可观察  [ ] 不要做`.\n\nSame-theme dedupe is required:\n\n- The helper records returned candidates in `data\u002Fgate-1\u002Fowner-review-history.json`.\n- On the next run with the same normalized theme, previously returned `candidate_id` and near-duplicate topic fingerprints are excluded.\n- If fewer than 10 new candidates remain, output fewer and say the same-theme candidate pool is exhausted; do not refill with old topics unless the owner explicitly asks.\n- Use `--no-history` only for debugging or reproducing an old report.\n\nThe owner should only need to judge the checklist. Do not ask the owner to inspect raw JSON, sort metrics, or approve every scoring detail.\n\nGate 1A passes when one run has 3 to 5 `要做` items, and is stable when two comparable runs reach that bar.\n\n### 7. Optional Downstream Creation\n\nOnly after the owner marks topics as `要做`, downstream content skills may generate briefs, scripts, recording plans, or conversion routes.\n\nThese outputs belong to content production, not radar acceptance.\n\n### 7.1 Generate Creation Briefs\n\nBefore writing briefs, generate one structured analysis per selected recording candidate.\n\nThe structured analysis must include:\n\n- user problem;\n- retention reason;\n- borrowable structure;\n- do-not-copy boundaries;\n- original angle;\n- owner-owned case;\n- three recreation routes;\n- title options;\n- cover copy options;\n- evidence used;\n- evidence limitations;\n- confidence and confidence reason;\n- risk notes.\n\nUse OpenAI only when `HOTSPOT_AI_ANALYSIS=1` or `--ai-analysis` is explicitly set and `OPENAI_API_KEY` exists. If OpenAI is disabled, missing, or fails, use the heuristic fallback and record the provider reason. Do not let AI analysis failure break candidate selection.\n\nFor selected candidates, output three routes when useful:\n\n1. Same pain point, different viewpoint.\n2. Same structure, owner's own case.\n3. Hotspot joined with a real project.\n\nEach brief must include:\n\n- source candidate and metrics;\n- what can be borrowed;\n- what cannot be copied;\n- owner-owned case;\n- original angle;\n- target audience;\n- title options;\n- risk notes;\n- evidence limitations.\n\n### 7.2 Generate Recording Packages\n\nOnly for candidates confirmed as worth doing or for validation samples.\n\nRecording package includes:\n\n- recommended title;\n- cover copy;\n- teleprompter script;\n- short shot plan;\n- required shots;\n- subtitle highlights;\n- forbidden materials;\n- pinned comment suggestion;\n- owner review gate.\n\nMark:\n\n- `publish_ready: false`\n- `status: recording_material_ready_for_owner_review`\n\nDo not call `talking-head-video-production` unless the user explicitly asks to enter actual filming\u002Fproduction.\n\n### 7.5 Review Data Source Failures\n\nEvery real run must preserve a failure summary.\n\nClassify failed or weak requests as:\n\n- `network_error`: local\u002Fnetwork\u002FAPI host unreachable;\n- `http_error`: HTTP 4xx or 5xx;\n- `api_error`: API returned a non-success code;\n- `parse_error`: response was not valid JSON;\n- `field_shape_changed`: expected result arrays are missing;\n- `empty_result`: request succeeded but produced zero usable candidates or comments.\n\nUse this to decide whether a bad run was caused by the theme, the keyword set, API stability, quota\u002Fauth, or response field changes. Do not hide these failures behind a low candidate count.\n\n### 8. Owner Review Gate\n\nThe owner should only need to judge:\n\n- whether the theme direction is right;\n- which Top candidates are `要做 \u002F 可观察 \u002F 不要做`.\n\nDo not require the owner to manually:\n\n- sort metrics;\n- inspect raw JSON;\n- write scoring reasons;\n- approve every small step.\n- judge script quality before radar acceptance.\n\n### 9. Review And Calibrate\n\nEnd every run with a concise workflow review:\n\n- search success;\n- comment success;\n- candidate count;\n- selected count;\n- accepted candidates;\n- rejected or risky candidates;\n- scoring issues;\n- keyword adjustments;\n- next run recommendation.\n\n## Current Known Project Facts\n\nAs of 2026-08-05:\n\n- Gate 0 has validated Douyin search\u002Fdetail\u002Fcomment availability with limitations.\n- Gate 1 round 2 produced 82 deduplicated candidates and 20 A\u002FB candidates.\n- Owner selected ranks 6, 11, and 4; all three were later judged worth recording.\n- A new topic rerun for `AI 自动化真实项目` produced 117 deduplicated candidates and 20 A\u002FB candidates.\n- `sort_type` and `publish_time` must be strings for the current TikHub endpoint.\n- Web MVP is not ready.\n- This Skill may be drafted\u002Fused for workflow validation, but should not imply commercial product readiness.\n\n## Output Style\n\nPrefer:\n\n- Chinese;\n- concise but evidence-backed;\n- direct decisions when the evidence is enough;\n- clear \"do \u002F do not \u002F wait\" boundaries;\n- file outputs for reusable reports and packages.\n\nAvoid:\n\n- saying the owner is right by default;\n- calling candidates \"viral\" when play\u002Fcompletion\u002Ffollower data are missing;\n- burying risk caveats;\n- producing long generic marketing copy without evidence;\n- step-by-step confirmation for every small artifact.\n\n## Completion Criteria\n\nA successful run should produce:\n\n- candidate report;\n- structured scores;\n- 10-topic owner checklist;\n- owner review fields;\n- workflow review and rule adjustments;\n- no leakage of secrets or internal data;\n- no claim of publishing, Web MVP, script readiness, recording readiness, or Skill installation unless actually done.\n",{},"main","19a54ac988e9929160334271f5c1924ddd9b227e","_modules\u002Fhotspot-radar-workflow-skill",19,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill","https:\u002F\u002Fgithub.com\u002Falicewe1","写一些自己用得上的工具，能自动化就绝不手动 · 自动化 \u002F 工程效率 \u002F Agent 技能生态 · 保持好奇，持续构建","2026-09-30 00:41:20",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add alicewe1\u002Falice_skill --skill hotspot-radar-workflow-skill",{"tool":38,"command":39},"bunx","bunx skills add alicewe1\u002Falice_skill --skill hotspot-radar-workflow-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add alicewe1\u002Falice_skill --skill hotspot-radar-workflow-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FSKILL.md",true,[46,52,58,62,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,163,169,173,177,181,185,189,193,197,201,205,209],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},".env.example","OTHER","其他",212,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002F.env.example",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},".github\u002Fworkflows\u002Fci.yml","REFERENCE","参考文档",251,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002F.github\u002Fworkflows\u002Fci.yml",{"path":59,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":60,"sourceHtmlUrl":61},".gitignore",111,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002F.gitignore",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fkeyword-expansion.svg","ASSET","资产文件",2545,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fassets\u002Fkeyword-expansion.svg",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Fworkflow-overview.svg",2616,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fassets\u002Fworkflow-overview.svg",{"path":73,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":74,"sourceHtmlUrl":75},"CHANGELOG.md",1131,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FCHANGELOG.md",{"path":77,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":78,"sourceHtmlUrl":79},"CONTRIBUTING.md",587,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FCONTRIBUTING.md",{"path":81,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":82,"sourceHtmlUrl":83},"docs\u002Fapi-provider.md",1871,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fapi-provider.md",{"path":85,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":86,"sourceHtmlUrl":87},"docs\u002Fen\u002Flimitations.md",603,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fen\u002Flimitations.md",{"path":89,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":90,"sourceHtmlUrl":91},"docs\u002Fen\u002Fproductization-map.md",922,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fen\u002Fproductization-map.md",{"path":93,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":94,"sourceHtmlUrl":95},"docs\u002Fen\u002Fquickstart.md",766,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fen\u002Fquickstart.md",{"path":97,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":98,"sourceHtmlUrl":99},"docs\u002Fen\u002FREADME.md",526,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fen\u002FREADME.md",{"path":101,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":102,"sourceHtmlUrl":103},"docs\u002Fen\u002Fusage.md",571,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fen\u002Fusage.md",{"path":105,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":106,"sourceHtmlUrl":107},"docs\u002Ffaq.md",1063,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Ffaq.md",{"path":109,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":110,"sourceHtmlUrl":111},"docs\u002Finstallation.md",1615,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Finstallation.md",{"path":113,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":114,"sourceHtmlUrl":115},"docs\u002Fproductization-map.md",855,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fproductization-map.md",{"path":117,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":118,"sourceHtmlUrl":119},"docs\u002Fsecurity-and-compliance.md",889,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fsecurity-and-compliance.md",{"path":121,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":122,"sourceHtmlUrl":123},"docs\u002Fusage.md",1259,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fusage.md",{"path":125,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":126,"sourceHtmlUrl":127},"docs\u002Fworkflow.md",1166,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fdocs\u002Fworkflow.md",{"path":129,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":130,"sourceHtmlUrl":131},"FIRST-RUN-CHECKLIST.md",2359,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FFIRST-RUN-CHECKLIST.md",{"path":133,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":134,"sourceHtmlUrl":135},"INSTALL.md",4767,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FINSTALL.md",{"path":137,"resourceType":137,"resourceTypeDesc":138,"sizeBytes":139,"sourceHtmlUrl":15},"LICENSE","许可证",1071,{"path":141,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":142,"sourceHtmlUrl":143},"package.json",897,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fpackage.json",{"path":145,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":146,"sourceHtmlUrl":147},"README_EN.md",3440,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FREADME_EN.md",{"path":149,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":150,"sourceHtmlUrl":151},"README.md",6901,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FREADME.md",{"path":153,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":154,"sourceHtmlUrl":155},"REPOSITORY_DESCRIPTION.md",401,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FREPOSITORY_DESCRIPTION.md",{"path":157,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":158,"sourceHtmlUrl":159},"repository-audit-report.md",1203,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Frepository-audit-report.md",{"path":161,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":142,"sourceHtmlUrl":162},"repository-publication-manifest.yaml","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Frepository-publication-manifest.yaml",{"path":164,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":167,"sourceHtmlUrl":168},"scripts\u002Fbuild-gate1a-owner-review.mjs","SCRIPT","脚本",10190,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Fbuild-gate1a-owner-review.mjs",{"path":170,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":171,"sourceHtmlUrl":172},"scripts\u002Ffirst-run-check.mjs",5321,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Ffirst-run-check.mjs",{"path":174,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":175,"sourceHtmlUrl":176},"scripts\u002Frun-gate1-topic-validation.mjs",53727,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Frun-gate1-topic-validation.mjs",{"path":178,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":179,"sourceHtmlUrl":180},"scripts\u002Frun-topic-checklist.mjs",2294,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Frun-topic-checklist.mjs",{"path":182,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":183,"sourceHtmlUrl":184},"scripts\u002Fsetup-tikhub-token.mjs",1713,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Fsetup-tikhub-token.mjs",{"path":186,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":187,"sourceHtmlUrl":188},"scripts\u002Ftikhub-token.mjs",2877,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Fscripts\u002Ftikhub-token.mjs",{"path":190,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":191,"sourceHtmlUrl":192},"SECURITY.md",399,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FSECURITY.md",{"path":194,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":195,"sourceHtmlUrl":196},"tests\u002Fbuild-gate1a-owner-review.test.mjs",3615,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Ftests\u002Fbuild-gate1a-owner-review.test.mjs",{"path":198,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":199,"sourceHtmlUrl":200},"tests\u002Ffirst-run-check.test.mjs",2632,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Ftests\u002Ffirst-run-check.test.mjs",{"path":202,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":203,"sourceHtmlUrl":204},"tests\u002Frun-topic-checklist.test.mjs",806,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Ftests\u002Frun-topic-checklist.test.mjs",{"path":206,"resourceType":165,"resourceTypeDesc":166,"sizeBytes":207,"sourceHtmlUrl":208},"tests\u002Ftikhub-token.test.mjs",2763,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002Ftests\u002Ftikhub-token.test.mjs",{"path":210,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":211,"sourceHtmlUrl":212},"VERSION",6,"https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002F_modules\u002Fhotspot-radar-workflow-skill\u002FVERSION",[214,222,229,236,243,250],{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":19},"01M7DBMD9P6R27SWQCW5HYVWG0","alice","Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时，严格输出固定菜单；输入攻\u002F防模式、六类入口或直接描述任务时，按类别→领域→模块渐进路由。","GPL-3.0","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Faliceskill\u002FSKILL.md",[],[],{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":228,"publishedAt":19},"01M7DBM8X5M7YXPYBVFMWF8HRC","alice-reverse","逆向分析渐进路由（二进制 \u002F 移动端 \u002F 协议 \u002F 取证 \u002F 保护机制 \u002F 运行时观测）。触发词：二进制\u002F移动端\u002F反编译\u002FFrida\u002FIDA\u002FGhidra\u002FPE\u002FELF\u002FAPK\u002F协议\u002F取证；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-reverse\u002FSKILL.md",[],[],{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":233,"categories":234,"keywords":235,"publishedAt":19},"01M7DBM630E2YKQP29194TT7HC","alice-pentest","web安全渐进路由（Web \u002F API \u002F 资产发现 \u002F 漏洞验证 \u002F 云与网络安全）。触发词：Web\u002FAPI\u002F资产发现\u002F端口\u002F漏洞验证\u002F云与网络安全；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-pentest\u002FSKILL.md",[],[],{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":19},"01M7DBM20M2VDYV5D3MYDGBTQX","alice-game","游戏攻防渐进路由（游戏客户端 \u002F 内存 \u002F 图形 \u002F 反作弊 \u002F 安全研究）。触发词：游戏客户端\u002F内存\u002F图形\u002F偏移\u002F反作弊\u002F模拟器\u002F覆盖层；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-game\u002FSKILL.md",[],[],{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":249,"publishedAt":19},"01M7DBKXVEKB8931MZG23VACFN","alice-crack","卡密授权渐进路由（卡密 \u002F 激活 \u002F 授权验证 \u002F 许可证管理 \u002F 本地授权分析）。触发词：卡密\u002F激活\u002F授权验证\u002Flicense\u002F机器码\u002F试用状态；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-crack\u002FSKILL.md",[],[],{"skillNo":251,"name":252,"nameZh":6,"description":253,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":218,"licenseFileUrl":6,"sourceHtmlUrl":254,"categories":255,"keywords":256,"publishedAt":19},"01M7DBKTMT90MGV2WP8K73TMQD","alice-assist","技能指令渐进路由（技能路由 \u002F 评分 \u002F 吸收 \u002F 迁移 \u002F 自动化 \u002F 文档与平台集成）。触发词：技能创建\u002F吸收\u002F评分\u002F迁移\u002F自动化\u002F文档\u002F平台指令；先选领域索引，再按任务匹配度与评分选模块，禁止一次读取全部领域。","https:\u002F\u002Fgithub.com\u002Falicewe1\u002Falice_skill\u002Fblob\u002Fmain\u002Falice-assist\u002FSKILL.md",[],[]]