Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计通过

session-analysis会话分析

Agent Skill

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

总安装

285

周安装

12

GitHub Stars

26

下载量

230
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/outfitter-dev/agents --skill session-analysis

简介

session-analysis 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果时使用。
  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Conversation Analysis

Signal extraction → pattern detection → behavioral insights.

<when_to_use>

  • User requests conversation analysis
  • Identifying frustration, success, or workflow patterns
  • Extracting user preferences and requirements
  • Understanding task evolution and iterations

NOT for: real-time monitoring, content generation, single message analysis

</when_to_use>

<signal_taxonomy>

TypeSubtypeIndicators
SuccessExplicit Praise"Perfect!", "Exactly what I needed", exclamation marks
SuccessContinuation"Now do the same for...", building on prior work
SuccessAdoptionUser implements suggestion without modification
SuccessAcceptance"Looks good", "Ship it", "Merge this"
FrustrationCorrection"No, I meant...", "That's wrong", "Do X instead"
FrustrationReversionUser undoes agent changes, "Go back"
FrustrationRepetitionSame request 2+ times, escalating specificity
FrustrationExplicit"This isn't working", "Why did you...", accusatory tone
WorkflowSequence"First...", "Then...", "Finally...", numbered lists
WorkflowTransition"Now that X is done, let's Y", stage changes
WorkflowTool ChainRecurring tool usage patterns (Read → Edit → Bash)
WorkflowContext SwitchAbrupt topic changes, no transition language
RequestProhibition"Don't use X", "Never do Y", "Avoid Z"
RequestRequirement"Always check...", "Make sure to...", "You must..."
RequestPreference"I prefer...", "It's better to...", comparative language
RequestConditional"If X then Y", "When A, do B", situational rules

Confidence levels:

  • High (0.8–1.0): Explicit keywords match taxonomy, no ambiguity, strong context
  • Medium (0.5–0.79): Implicit signal, partial context, minor ambiguity
  • Low (0.2–0.49): Ambiguous language, weak context, borderline classification

</signal_taxonomy>

Load the maintain-tasks skill for stage tracking. Stages advance only, never regress.

StageTriggeractiveForm
Parse InputSession start"Parsing input"
Extract SignalsScope validated"Extracting signals"
Detect PatternsSignals extracted"Detecting patterns"
Synthesize ReportPatterns detected"Synthesizing report"

Task format:

- Parse Input { scope description }
- Extract Signals { from N messages }
- Detect Patterns { category focus }
- Synthesize Report { output format }

Edge cases:

  • Small scope (<5 messages): Skip Extract Signals, jump to Synthesize
  • Re-analysis: Resume at Detect Patterns
  • Narrow focus (single signal type): Skip Detect Patterns

Workflow:

  • Start: Create Parse Input in_progress
  • Transition: Mark current completed, add next in_progress
  • After delivery: Mark Synthesize Report completed
  1. Define Scope

- Message range (all, recent N, date range) - Actors (user only, agent only, both) - Exclusions (system messages, tool outputs, code blocks) - Mark Parse Input completed, create Extract Signals in_progress

  1. Extract Signals

- Scan messages for signal keywords - Match against taxonomy - Assign confidence (high/medium/low) - Record: type, subtype, message_id, timestamp, quote, context - Mark Extract Signals completed, create Detect Patterns in_progress

  1. Detect Patterns

- Group signals by type/subtype - Find clusters (3+ related signals) - Identify evolution (signal changes over time) - Track repetition (recurring themes) - Spot correlations (tool chains, workflows) - Mark Detect Patterns completed, create Synthesize Report in_progress

  1. Output

- Generate JSON with signals, patterns, summary - Include confidence, recommendations, action items - Append △ Caveats if gaps exist - Mark Synthesize Report completed

<pattern_detection>

Behavioral patterns from signal clusters:

PatternDetectionConfidence
RepetitionSame signal 3+ timesStrong: 5+ signals
EvolutionSignal type changes over timeModerate: 3-4 signals
PreferencesConsistent request signalsStrong: across sessions
Tool ChainsRecurring tool sequences (5+ times)High: frequent use
Problem AreasClustered frustration signalsStrong: 3+ in same topic

Temporal patterns:

  • Escalation: Increasing frustration/stronger requirements
  • De-escalation: Frustration → success transition
  • Cyclical: Same issue recurs across sessions

</pattern_detection>

<output_format>

JSON structure:

{
  "analysis": {
    "scope": {
      "message_count": N,
      "date_range": "YYYY-MM-DD to YYYY-MM-DD",
      "actors": ["user", "agent"]
    },
    "signals": [
      {
        "type": "success|frustration|workflow|request",
        "subtype": "specific_subtype",
        "message_id": "msg_123",
        "timestamp": "ISO8601",
        "quote": "exact text",
        "confidence": "high|medium|low",
        "context": "brief explanation"
      }
    ],
    "patterns": [
      {
        "pattern_type": "repetition|evolution|preference|tool_chain",
        "category": "success|frustration|workflow|request",
        "description": "pattern summary",
        "occurrences": N,
        "confidence": "strong|moderate|weak",
        "first_seen": "ISO8601",
        "last_seen": "ISO8601",
        "recommendation": "actionable next step"
      }
    ],
    "summary": {
      "total_signals": N,
      "by_type": { "success": N, "frustration": N, ... },
      "key_insights": ["insight 1", "insight 2"],
      "action_items": ["item 1", "item 2"]
    }
  }
}

</output_format>

ALWAYS:

  • Create Parse Input at session start
  • Update todos at stage transitions
  • Include confidence levels for all signals
  • Support patterns with 2+ signals minimum
  • Mark Synthesize Report completed after delivery
  • Apply recency weighting (recent overrides old)

NEVER:

  • Skip stage transitions
  • Extract low-confidence signals without marking them
  • Claim patterns from single occurrences
  • Regress stages
  • Deliver without marking final stage complete
  • Over-interpret neutral language

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

github-copilot

28.4%
按下载量换算65

kilo

23.59%
按下载量换算54

windsurf

18.52%
按下载量换算43

zencoder

13.51%
按下载量换算31

amp

8%
按下载量换算18

cline

3.77%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills