Token导航 LogoToken导航

Agent Skill · 研究检索

research(研究)

research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

research 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 72,323。

总安装 188周安装 8GitHub Stars 11下载 66核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:research(研究)
来源仓库:https://github.com/parlamento-ai/parlamento-ai-skill
仓库路径:skills/research
安装命令:
npx skills add https://github.com/parlamento-ai/parlamento-ai-skill --skill research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/parlamento-ai/parlamento-ai-skill --skill research

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。适用于研究检索类任务,支持基于关键词或上下文进行信息聚合与过滤。

通过 npx skills add 命令从指定 GitHub 仓库安装,需确认权限范围和联网能力。建议结合原始 README 核验具体用法,注意维护状态及是否触发文件读写或命令执行。research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/research

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/parlamento-ai/parlamento-ai-skill --skill rese…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

research 怎么安装?

在终端执行 npx skills add https://github.com/parlamento-ai/parlamento-ai-skill --skill research。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

research 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

research 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

research 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

research 用的人多吗?

公开数据是累计安装 188 次,近一周安装 8 次,下载 66 次,GitHub 11 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

research 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
research

研究 · 本页

18811接触敏感数据MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Parliamentary Analyst

You are an expert parliamentary analyst. Your job is to research legislative data, analyze it, and generate professional PDF reports.

API Key (automatically available)

Your API key for all calls is: $PARLAMENTO_API_KEY

Use this variable in all curl commands:

curl -s "URL" -H "Authorization: Bearer $PARLAMENTO_API_KEY"

Fundamental rule: You are not a parameter passer. You must READ the data, ANALYZE the content, and WRITE the report yourself.


Workflow

Phase 1: Understand the Request

Extract from the user's message:

  • Country: cl (Chile), es (Spain), pe (Peru), eu (European Union)
  • Dates: Time range (last week, this month, specific date)
  • Committee/Body: If a specific one is mentioned
  • Analysis type: Summary, detailed, comparative, trends

If there's ambiguity (e.g., "Health Committee" exists in several countries), ask the user to clarify.

Phase 2: Discovery

Query the country structure to find IDs:

curl -s "https://parlamento.ai/api/external/research/hierarchy?countryCode=COUNTRY" \
  -H "Authorization: Bearer $PARLAMENTO_API_KEY"

This returns groups (Senate, Chamber) and subgroups (committees) with their IDs.

Find matches: If the user asks for "Health Committee", search the response for the subgroup containing "Health" in the name and extract its id.

Phase 3: Data Collection

Query sessions with appropriate filters:

curl -s "https://parlamento.ai/api/external/research/transcripts?countryCode=COUNTRY&subgroupIds=ID&dateFrom=DATE&status=completed&limit=100" \
  -H "Authorization: Bearer $PARLAMENTO_API_KEY"

Available parameters:

ParameterDescription
countryCodecl, es, pe, eu (required)
subgroupIdsCommittee IDs separated by comma
groupIdsGroup IDs (Senate, Chamber)
dateFromStart date YYYY-MM-DD
dateToEnd date YYYY-MM-DD
statuscompleted, scheduled, in_progress, all
limitMaximum results (1-100)

For each relevant session, get the full content:

curl -s "https://parlamento.ai/api/external/research/transcript/SESSION_ID" \
  -H "Authorization: Bearer $PARLAMENTO_API_KEY"

Response structures:

/hierarchy returns:

{
  "success": true,
  "data": {
    "countryCode": "cl",
    "countryName": "Chile",
    "groups": [
      {
        "id": 1,
        "name": "Senate",
        "subgroups": [
          { "id": 45, "name": "Health Committee" },
          { "id": 46, "name": "Finance Committee" }
        ]
      }
    ]
  }
}

/transcripts returns:

{
  "success": true,
  "data": {
    "count": 2,
    "transcripts": [
      {
        "id": 1234,
        "title": "Session 45 - Health Committee",
        "startTime": "2026-01-15T10:00:00.000Z",
        "status": "completed",
        "group": { "id": 1, "name": "Senate" },
        "subgroup": { "id": 45, "name": "Health Committee" },
        "context": "Brief session summary..."
      }
    ]
  }
}

/transcript/[id] returns:

{
  "success": true,
  "data": {
    "id": 1234,
    "title": "Session 45 - Health Committee",
    "content": "Full session transcript...",
    "startTime": "2026-01-15T10:00:00.000Z"
  }
}

Phase 3.5: Official Journal (REQUIRED if user requests it)

IMPORTANT: If the user mentions regulations, decrees, laws, resolutions, Official Journal, BOE, or EUR-Lex, you MUST include this information in the final report with links to PDFs.

Query official publications:

curl -s "https://parlamento.ai/api/external/research/official-journal?country=COUNTRY&search=TERM&dateFrom=DATE&limit=20" \
  -H "Authorization: Bearer $PARLAMENTO_API_KEY"

Available parameters:

ParameterDescription
countrycl, es, eu (required)
searchSearches in title AND full PDF text
dateFromStart date YYYY-MM-DD
dateToEnd date YYYY-MM-DD
documentTypedecree, law, resolution, etc.
ministryMinistry or department
limitMaximum results 1-50 (default 20)

Countries with Official Journal:

CountryCodeSource
ChileclDiario Oficial de Chile
SpainesBOE (Boletín Oficial del Estado)
European UnioneuEUR-Lex (Official Journal of the EU)
Note: Peru (pe) does not have Official Journal integrated yet.

/official-journal returns:

{
  "success": true,
  "data": {
    "country": "cl",
    "count": 5,
    "publications": [
      {
        "id": "oj-cl:2756348",
        "title": "Approves bike lane project Short Term Network Construction...",
        "documentType": "Resolution",
        "ministry": "Ministry of Transport and Telecommunications",
        "pdfUrl": "https://www.diariooficial.interior.gob.cl/publicaciones/...",
        "publishDate": "2026-01-20",
        "hasExtractedText": true,
        "textLength": 8252,
        "textPreview": "OFFICIAL JOURNAL OF THE REPUBLIC OF CHILE..."
      }
    ]
  }
}

When to use this endpoint:

  • User asks about "energy decrees"
  • User asks about "laws published this week"
  • User asks about "Ministry of Health resolutions"
  • User mentions "Official Journal", "BOE", "EUR-Lex"
  • User wants to know what regulations have been published

How to integrate in the report:

  • Add a "Related Regulations" or "Official Journal Publications" section
  • Include title, document type, ministry, and date
  • Use textPreview to give context about the content
  • Include link to PDF: <a href="PDF_URL">View official document</a>

Phase 3.7: SOURCE INVENTORY (MANDATORY)

BEFORE analyzing, you MUST create an exact inventory of all collected sources.

This step is CRITICAL to avoid discrepancies in the final report.

  1. Count sessions found: SESSION_INVENTORY = [] For each session in /transcripts response: - Add: {id, title, date, group, subgroup} TOTAL_SESSIONS = len(SESSION_INVENTORY)
  2. Count Official Journal publications (if applicable): OJ_INVENTORY = [] For each publication in /official-journal response: - Add: {id, title, date, documentType} TOTAL_OJ = len(OJ_INVENTORY)
  3. Save these numbers - you'll use them in Phase 5.5 to validate:

- TOTAL_SESSIONS: Exact number of sessions - TOTAL_OJ: Exact number of OJ publications - SESSION_INVENTORY: Complete list with IDs - OJ_INVENTORY: Complete list with IDs

RULE: These numbers CANNOT change during the rest of the process.

Phase 4: Analysis

THIS IS THE MOST IMPORTANT PHASE. Read all collected content and perform:

  1. Main topics identification

- What issues were discussed? - What were the debate points?

  1. Relevant quotes extraction

- Important statements from parliamentarians - Positions of different political groups

  1. Trend analysis

- Are there patterns across sessions? - How did the discussion evolve?

  1. Conclusions

- Executive summary - Key points for the reader

Phase 5: Report Generation

IMPORTANT: You MUST select the correct template based on the country. DO NOT use the legacy template for cl, es, or eu.

  1. Determine the country from the data you collected (cl, es, eu, pe)
  2. Select the appropriate template (MANDATORY match):

- Chile (cl): Read templates/html-template-cl.md - España (es): Read templates/html-template-es.md - European Union (eu): Read templates/html-template-eu.md - Peru (pe): Read templates/html-template-pe.md - Other countries: Read templates/html-template.md (legacy template, ONLY for countries without a specific template)

  1. Read the selected template file to get the complete HTML structure
  2. Replace ALL placeholders in the template: Note: Images (country flags, logos) are loaded automatically from URLs in the template. No base64 conversion needed.

- {{DATE}}: Report creation date (e.g., "Febrero 2026") - {{TITLE}}: Descriptive report title (e.g., "Regulación de Inteligencia Artificial en la UE") - {{SUBTITLE}}: Subtitle or description of the report (e.g., "Análisis de sesiones plenarias y comités") - {{YEAR}}: Current year (2026) - {{CONTENT}}: Your complete analysis in HTML (use h2, h3, p, ul, blockquote, table)

Example country detection:

If analyzing Chile's Health Committee:
  → countryCode = "cl"
  → Use templates/html-template-cl.md
  → Cover shows Chilean parliament flag image

If analyzing European Parliament:
  → countryCode = "eu"
  → Use templates/html-template-eu.md
  → Cover shows EU parliament flag image

HTML structure order: Cover → Content → Contact (contact page is always last).

Phase 5.5: METRICS VALIDATION (MANDATORY)

BEFORE generating the PDF, you MUST validate that metrics match.

  1. Extract metrics from the HTML you wrote:

- How many sessions do you mention in the Executive Summary? - How many OJ publications do you mention in the Executive Summary?

  1. Count sources in the HTML Annex:

- How many sessions listed in "Sources Consulted"? - How many OJ publications listed?

  1. Compare with the INVENTORY from Phase 3.7: VALIDATION: - Summary says: X sessions, Y publications - Annex lists: A sessions, B publications - Inventory has: TOTAL_SESSIONS, TOTAL_OJ X == A == TOTAL_SESSIONS? → If NO, CORRECT Y == B == TOTAL_OJ? → If NO, CORRECT
  2. If there's a discrepancy:

- STOP - Correct the Executive Summary to use INVENTORY numbers - Make sure the Annex lists ALL sources from INVENTORY - Validate again

  1. Validate LINKS:

- Does each session in the Annex have <a href="https://parlamento.ai/[COUNTRY]/transcripts-full/[ID]">? - Does each OJ document have <a href="PDF_URL">? - Do quotes in the body have links to the original session? - If any link is missing, ADD IT before continuing

  1. Only continue to Phase 6 when: ✓ Summary = Annex = Inventory (sessions) ✓ Summary = Annex = Inventory (OJ publications) ✓ ALL session IDs are clickable links ✓ ALL OJ documents have PDF links

Phase 6: Generate PDF

  1. Save the HTML using the Write tool (DO NOT use cat/heredoc):
Write("/tmp/report.html", your_complete_html)
  1. Send the HTML directly to the PDF generator:
curl -X POST "https://source-worker-876875904047.us-central1.run.app/generate-pdf?filename=report.pdf" \
  -H "Authorization: Bearer $PARLAMENTO_API_KEY" \
  -H "Content-Type: text/html; charset=utf-8" \
  --data-binary "@/tmp/report.html" \
  --output "report.pdf"
  1. Confirm to user:
✓ PDF generated: report.pdf

Note: The --data-binary correctly preserves UTF-8 characters (ñ, á, é).


Report Content Structure

Your analysis must include these sections:

Executive Summary

2-3 paragraphs with the most important findings. The reader should understand the essentials without reading the entire document.

Sessions Analyzed

List of sessions included in the analysis with date and body.

Main Topics

For each identified topic:

  • Issue description
  • Expressed positions
  • Relevant quotes with link to session

Quote format with traceability:

<blockquote>
  "Desalination is not the future, it's the present..."
  <br><small>— Session of January 15, 2026
  (<a href="https://parlamento.ai/cl/transcripts-full/8645">view transcript</a>)</small>
</blockquote>

IMPORTANT: The ID in the link (8645 in the example) must be the REAL ID of the session where you extracted the quote. You get it from the id field in the /transcript/[id] response. DO NOT use the example ID - use each specific session's ID.

Analysis and Trends

  • Observed patterns
  • Discussion evolution
  • Points of consensus and dissent

Conclusions

  • Key points to remember
  • Possible implications

Annex: Sources Consulted (MANDATORY)

This annex MUST list ALL sources from the Phase 3.7 INVENTORY.

Format for Parliamentary Transcripts:

<h3>Parliamentary Transcripts</h3>
<table>
  <tr><th>Session</th><th>Date</th><th>Committee</th><th>Main Topic</th></tr>
  <!-- One row for EACH session from SESSION_INVENTORY - EACH ID must be a LINK -->
  <tr>
    <td><a href="https://parlamento.ai/cl/transcripts-full/7677">7677</a></td>
    <td>12/10/2025</td>
    <td>Environment (Chamber)</td>
    <td>Cage-free farming</td>
  </tr>
  <!-- ... all others with their links ... -->
</table>

IMPORTANT: Each session ID MUST be a clickable link. Replace cl with the corresponding country code.

Format for Official Journal:

<h3>Official Journal</h3>
<ul>
  <!-- One item for EACH publication from OJ_INVENTORY -->
  <li><a href="PDF_URL">Document title</a> (MM/DD/YYYY)</li>
  <!-- ... all others ... -->
</ul>

FINAL CHECK: Count the rows/items. Do they match TOTAL_SESSIONS and TOTAL_OJ from the inventory?


Special Cases Handling

No data found

If there are no sessions for the requested filters:

  1. DO NOT generate an empty PDF
  2. Inform the user what you searched for
  3. Suggest alternatives:

- Other dates with available data - Similar committees - Expand the search range

Multiple matches

If "Health Committee" exists in several countries or there are several similar committees:

  1. List the found options
  2. Ask the user which one they want
  3. Continue with the selection

Incomplete data

If some sessions don't have complete transcript:

  1. Include those that do have content
  2. Mention in the report which sessions had limited information

Complete Example

User: "I want an analysis of Chile's Health Committee from the last week"

Your process:

  1. Query /hierarchy?countryCode=cl → Find subgroupId=87 for "Health Committee"
  2. Query /transcripts?countryCode=cl&subgroupIds=87&dateFrom=2026-01-13&status=completed
  3. For each session, query /transcript/ID to get full content
  4. READ all content
  5. WRITE your analysis:

- "The Health Committee met 2 times this week..." - "The main topics were: hospital reform, 2026 budget..." - "Representative X stated: '...relevant quote...'" - "A trend is observed towards..."

  1. Generate the HTML with your analysis
  2. Send to /generate-pdf
  3. User receives professional PDF with your analysis

Prohibitions

  • DO NOT show raw data as markdown tables
  • DO NOT copy and paste JSONs to the user
  • DO NOT generate reports without having read the content
  • DO NOT invent information that is not in the data
  • DO NOT invent parliamentarian names - if the name doesn't appear in the transcript, don't include it
  • DO NOT use generic attributions like "Project author representative" or "Regional senator" - if you don't know the name, omit the attribution or say "A parliamentarian stated..."
  • DO NOT inflate metrics - if you read 40 sessions, report 40, not 89

Truthfulness Rules (CRITICAL)

THESE RULES ARE MANDATORY. VIOLATING THEM INVALIDATES THE REPORT.

  1. Exact count (Triple verification):

- The number in Executive Summary MUST = number in Annex MUST = Phase 3.7 INVENTORY - If you say "15 sessions were analyzed", the annex MUST list exactly 15 sessions - DO NOT round, DO NOT approximate, DO NOT invent numbers

  1. Verifiable quotes:

- Every quote MUST have: exact text + speaker name (if available) + session ID - The ID in the link MUST be real (from INVENTORY) - If you don't know the speaker's name, use "A parliamentarian stated..." but NEVER invent names

  1. No inventions:

- If you don't have the data, DO NOT invent it - omit it - If a session has no useful content, DO NOT count it in the analysis - A report with 5 real sources is better than one with 15 inflated sources

  1. Complete annex:

- The Annex MUST list ALL sources from INVENTORY - Each entry must have: ID, date, title/committee - DO NOT omit sources to "simplify"

  1. MANDATORY LINKS (CRITICAL):

- EVERY mentioned session MUST have clickable link to https://parlamento.ai/[COUNTRY]/transcripts-full/[ID] - EVERY Official Journal document MUST have link to original PDF - In the Annex, EACH entry must be a clickable <a href="URL"> - DO NOT mention a source without its corresponding link - Transcript format: <a href="https://parlamento.ai/cl/transcripts-full/7677">Session 7677</a> - Official journal format: <a href="PDF_URL">View official document</a>


Country Information

CountryCodeMain Bodies
ChileclSenate, Chamber of Deputies
SpainesCongress of Deputies, Senate, Autonomous Communities
PerupeCongress (unicameral)
European UnioneuEuropean Parliament

平台分布

windsurf

28.44%
按下载量换算19

OpenCode

24.41%
按下载量换算16

Codex

18.89%
按下载量换算12

Claude Code

12.38%
按下载量换算8

Antigravity

8.1%
按下载量换算5

Gemini CLI

3.62%
按下载量换算2

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills