Token导航 LogoToken导航TokenDH.com
研究检索敏感数据github未标认证来源可访问许可证需确认审计通过

pact-prepare-research协议准备研究

Agent Skill

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

总安装

396

周安装

17

GitHub Stars

62

下载量

139
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/profsynapse/pact-plugin --skill pact-prepare-research

简介

pact-prepare-research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 它适用于研究检索类任务,可结合来源仓库和原始 README 核验具体用法。
  • 安装方式:通过 npx skills add 命令从 GitHub 仓库安装。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

PACT Prepare Research Methodology

Structured approaches for the Prepare phase of PACT. This skill provides frameworks for systematic research, documentation gathering, and technology evaluation to build a solid foundation before architecture and implementation.

Research Workflow

Phase 1: Define Research Scope

Before starting research, clearly define:

## Research Scope Definition

### Primary Question
What specific problem are we trying to solve?

### Success Criteria
What would make a solution acceptable?
- [ ] Performance requirements
- [ ] Integration requirements
- [ ] Security requirements
- [ ] Budget constraints

### Constraints
What limitations must we work within?
- Technology stack restrictions
- Team expertise
- Timeline
- Licensing requirements

Phase 2: Source Prioritization

Prioritize sources by authority and reliability:

PrioritySource TypeExamplesTrust Level
1Official documentationDocs, API referencesHighest
2Official repositoriesGitHub READMEs, wikisVery High
3Maintainer contentBlog posts by core teamHigh
4Community verifiedStack Overflow accepted answersMedium
5Third-party tutorialsBlog posts, videosLow-Medium
6AI-generated contentChatGPT, CopilotVerify Required

Source Verification Checklist:

  • Publication date within 12 months (for version-specific info)
  • Author has verifiable credentials
  • Information matches official docs
  • Code examples actually work

Phase 3: Documentation Types to Gather

Collect these documentation types for complete understanding:

1. API References

## API Documentation Checklist
- [ ] Authentication methods
- [ ] Rate limits and quotas
- [ ] Available endpoints
- [ ] Request/response formats
- [ ] Error codes and handling
- [ ] SDK availability
- [ ] Webhook support

2. Configuration Guides

## Configuration Documentation
- [ ] Environment variables
- [ ] Configuration file formats
- [ ] Default values
- [ ] Required vs optional settings
- [ ] Security-sensitive configs

3. Migration Documentation

## Migration Considerations
- [ ] Breaking changes between versions
- [ ] Deprecation timelines
- [ ] Migration guides
- [ ] Data migration requirements

4. Security Advisories

## Security Documentation
- [ ] Known vulnerabilities (CVEs)
- [ ] Security best practices
- [ ] Authentication requirements
- [ ] Data handling guidelines

Phase 4: Evaluation Criteria

Use this framework to evaluate research findings:

CriterionQuestionsWeight
CurrencyUpdated within 12 months? Active development?High
AuthorityOfficial source? Maintainer authored?High
CompletenessCovers required use cases?Medium
PracticalityActionable? Working examples?Medium
CompatibilityWorks with existing stack?High
CommunityActive community? Good support?Medium
SecuritySecurity track record? Quick patches?High

Quick Reference Templates

Technology Comparison

For structured side-by-side comparisons: See technology-comparison-matrix.md

Quick Comparison Template:

| Criterion | Option A | Option B | Winner |
|-----------|----------|----------|--------|
| Learning curve | Steep | Gentle | B |
| Performance | Fast | Very Fast | B |
| Documentation | Good | Excellent | B |
| Community size | Large | Medium | A |
| **Total** | 1 | 3 | **B** |

API Documentation Summary

For capturing API details systematically: See api-exploration-template.md

Quick API Summary:

## API: [Name]

**Base URL**: `https://api.example.com/v1`
**Auth**: Bearer token in header
**Rate Limit**: 100 req/min

### Key Endpoints
| Endpoint | Method | Purpose |
|----------|--------|---------|
| /users | GET | List users |
| /users/:id | GET | Get user |
| /users | POST | Create user |

### Authentication

curl -H "Authorization: Bearer YOUR_TOKEN" \ https://api.example.com/v1/users

Requirements Analysis

For comprehensive requirements documentation: See requirements-analysis.md

Quick Requirements Template:

## Feature: [Name]

### User Story
As a [user type], I want [action] so that [benefit].

### Acceptance Criteria
- [ ] Given [context], when [action], then [result]
- [ ] Given [context], when [action], then [result]

### Technical Requirements
- Performance: [target]
- Security: [requirements]
- Integration: [dependencies]

### Dependencies
- Depends on: [other features/services]
- Blocked by: [blockers]

Research Output Format

Standard Research Document Structure

# Research: [Topic]

## Executive Summary
[2-3 sentence summary of findings and recommendation]

## Background
[Why this research was needed]

## Methodology
[How research was conducted]

## Findings

### Option 1: [Name]
**Pros:**
- [Pro 1]
- [Pro 2]

**Cons:**
- [Con 1]
- [Con 2]

**Evidence:**
- [Link to source]
- [Link to source]

### Option 2: [Name]
[Same structure]

## Comparison Matrix
[Side-by-side comparison table]

## Risk Assessment
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [Risk] | High/Med/Low | High/Med/Low | [Strategy] |

## Recommendation
[Clear recommendation with rationale]

## Next Steps
1. [Action item]
2. [Action item]

## References
- [Source 1]
- [Source 2]

Quality Checklist

Before completing Prepare phase research:

Source Quality

  • All critical information from official sources
  • Version numbers explicitly stated
  • Publication dates verified (within 12 months for technical details)
  • No single point of information failure (multiple sources for key facts)

Completeness

  • All evaluation criteria addressed
  • Alternatives presented with pros/cons
  • Security implications documented
  • Performance characteristics noted
  • Integration requirements identified

Actionability

  • Recommendations backed by evidence
  • Next steps clearly defined
  • Risks identified with mitigations
  • Dependencies mapped

Documentation

  • Research document follows standard structure
  • All sources linked and accessible
  • Key decisions documented with rationale
  • Output saved to docs/{feature}/preparation/

Common Research Patterns

Library/Framework Selection

  1. Define requirements and constraints
  2. Identify 3-5 candidates
  3. Evaluate against criteria matrix
  4. Prototype with top 2 candidates
  5. Document decision rationale

API Integration Research

  1. Gather official API documentation
  2. Test authentication flow
  3. Document all required endpoints
  4. Identify rate limits and quotas
  5. Plan error handling strategy

Technology Migration

  1. Document current state
  2. Research target technology
  3. Identify breaking changes
  4. Plan migration path
  5. Define rollback strategy

Detailed References

For comprehensive templates and frameworks:

- Full API documentation template - Authentication testing guide - Error handling documentation

- User story templates - Acceptance criteria patterns - Non-functional requirements

- Weighted scoring templates - Multi-criteria decision analysis - Risk assessment frameworks

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.6%
按下载量换算52

Claude

30.24%
按下载量换算42

Cursor

18.99%
按下载量换算26

Gemini CLI

10.04%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills