Add Xquik research skill

README.md

@@ -68,6 +68,7 @@ daily work  ->  repeatable workflow  ->  SKILL.md  ->  reusable agent capability
 
 - [`daily-notes-vp`](knowledge-skills/daily-notes-vp/)：把个人学习中的短期目标、疑问、代码记录、概念和踩坑经验轻量追加到 `E:\LLM_wiki\LLM_wiki\01.raw\02.DailyNotes`，10 天一个文件，按 Goal / Question / Code / Concept / Pitfall 组织。
 - [`image-to-md-vp`](knowledge-skills/image-to-md-vp/)：把多轮输入的截图或图片 OCR 成指定路径下的 Markdown 文件，保留标题层级、表格、公式、emoji 和原始结构。
+- [`xquik-research-vp`](knowledge-skills/xquik-research-vp/)：把 Xquik REST API 的 X/Twitter 数据整理成研究笔记、结构化摘要、对比表或仪表盘行。
 
 ### `job-skills/`
 

knowledge-skills/README.md

@@ -56,6 +56,7 @@ knowledge-skills/
 ├── zhihu-clippings-vp/     # 知乎文章定位、正文补全、公式图片表格保留与 Obsidian Markdown 剪藏
 ├── wechat-clippings-vp/    # 微信公众号文章定位、TikHub 正文抓取、页面噪声清理与 Markdown 剪藏
 ├── tech-article-rewriter-vp/ # URL/截图语料采集、技术文章深度重写、模板化 Markdown 草稿生成与迭代
+├── xquik-research-vp/      # Xquik REST API 的 X/Twitter 数据研究、结构化摘要与表格整理
 └── README.md            # 知识类技能目录说明
 ```
 
@@ -93,6 +94,10 @@ knowledge-skills/
 
 用于技术文章深度重写：从 URL、截图、OCR 或现成语料出发，先获取并缓存可信全文，再提取事实、观点、代码和坑点，重建文章逻辑，按 Markdown 模板生成专业标题、轻松正文、逻辑清晰且带参考资料的技术博客草稿
 
+### [`xquik-research-vp/`](xquik-research-vp/)
+
+用于 Xquik REST API 数据研究：围绕推文搜索、资料查询、时间线、趋势、社区或监控输出，规范化 ID、时间戳和捕获时间，把 X/Twitter 数据整理成研究笔记、结构化摘要、对比表或仪表盘行
+
 ## 适合沉淀的技能
 
 - 自顶向下学习流程

knowledge-skills/xquik-research-vp/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: xquik-research-vp
+description: Use when planning, collecting, normalizing, or summarizing Xquik REST API data for X/Twitter research, trend tracking, profiles, communities, timelines, or monitor outputs.
+---
+
+# xquik-research-vp
+
+Use this skill when a user wants to turn Xquik REST API data into research notes, structured summaries, comparison tables, or dashboard-ready rows.
+
+## Inputs
+
+- Research goal, such as tweet search, profile lookup, timelines, trends, communities, or monitors.
+- Xquik endpoint path or public OpenAPI reference.
+- User-provided API response JSON, export files, or permission to fetch data with credentials already configured in the runtime.
+
+## Workflow
+
+1. Clarify the research goal and the exact X/Twitter entity or query.
+2. Select the matching public Xquik endpoint or ask for the endpoint path.
+3. Keep API keys in the runtime environment or approved credential store.
+4. Fetch data only when credentials and user approval are already available, or parse user-provided JSON.
+5. Normalize IDs as strings, preserve source timestamps, and record the capture time.
+6. Group records by the question being answered: author, topic, trend, community, timeline position, or monitor event.
+7. Summarize findings with clear evidence fields and mark any inferred labels as analysis.
+
+## Output
+
+- Endpoint path and capture time.
+- Short findings summary.
+- Structured rows or a Markdown table for the selected entities.
+- Notes on missing fields, pagination limits, or assumptions.
+
+## Guardrails
+
+- Do not print, paste, or store API keys.
+- Do not claim private pricing, capacity, or implementation details.
+- Do not perform write actions unless the user explicitly requests a write workflow.
+- Do not treat inferred labels or sentiment as facts.