Analyzer
iBigQiang/feedgrab
Content Analyzer — any content (URL, text, transcript) into structured analysis report with actionable insights.
This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…
MITAuto-check passed
Install Session Analyzer
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .claude/skills/session-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .claude/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .agents/skills/session-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .agents/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .cursor/skills/session-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .cursor/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/team-attention/plugins-for-claude-natives.git --path plugins/session-wrap/skills/session-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .gemini/skills/session-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .gemini/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .github/skills/session-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .github/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install team-attention/plugins-for-claude-natives session-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/session-wrap/skills/session-analyzer .opencode/skills/session-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "session-analyzer" agent skill from https://github.com/team-attention/plugins-for-claude-natives/tree/main/plugins/session-wrap/skills/session-analyzer into .opencode/skills/session-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "session-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
session-analyzer- GitHub stars
- 825
- Token cost
- ~1.8k tokens
- SKILL.md length
- 405 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- MIT
At a glance
This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…
- Works in 6 steps: Locate Session Files → Parse Target SKILL.md → Analyze Debug Log → …
- Asks to analyze session
- SKILL.md covers Purpose, Input Requirements, Phase 1: Locate Session Files and Phase 2: Parse Target SKILL.md, plus 7 more sections
- Runs Shell scripts from its folder
What it does
Session Analyzer is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/analysis-patterns.md`, `references/common-issues.md` and `scripts/extract-hook-events.sh`).
The repository describes itself as: Claude Code plugins for power users. The licence is MIT.
When your agent uses it
- Asks to analyze session
- Evaluate skill execution
- Check session logs
- Provides a session ID with a skill path
Example prompts
- “analyze session”
- “evaluate skill execution”
- “check session logs”
- “/session-analyzer”
Requirements
- A Bash shell
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit fd9c207. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Session Analyzer loads about 1.8k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 405 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from team-attention/plugins-for-claude-natives at commit fd9c207, republished under its MIT licence (© team-attention). 405 words, ~1,844 tokens.
Download SKILL.mdSave it as
.claude/skills/session-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- session-analyzer
- description
- This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.
- version
- 1.0.0
- user-invocable
- true
Session Analyzer Skill
Post-hoc analysis tool for validating Claude Code session behavior against SKILL.md specifications.
Purpose
Analyze completed sessions to verify:
- Expected vs Actual Behavior - Did the skill follow SKILL.md workflow?
- Component Invocations - Were SubAgents, Hooks, and Tools called correctly?
- Artifacts - Were expected files created/deleted?
- Bug Detection - Any unexpected errors or deviations?
Input Requirements
| Parameter | Required | Description |
|---|---|---|
sessionId | YES | UUID of the session to analyze |
targetSkill | YES | Path to SKILL.md to validate against |
additionalRequirements | NO | Extra validation criteria |
Phase 1: Locate Session Files
Step 1.1: Find Session Files
Session files are located in ~/.claude/:
# Main session log
~/.claude/projects/-{encoded-cwd}/{sessionId}.jsonl
# Debug log (detailed)
~/.claude/debug/{sessionId}.txt
# Agent transcripts (if subagents were used)
~/.claude/projects/-{encoded-cwd}/agent-{agentId}.jsonlUse script to locate files:
${baseDir}/scripts/find-session-files.sh {sessionId}Step 1.2: Verify Files Exist
Check all required files exist before proceeding. If debug log is missing, analysis will be limited.
Phase 2: Parse Target SKILL.md
Step 2.1: Extract Expected Components
Read the target SKILL.md and identify:
From YAML Frontmatter:
hooks.PreToolUse- Expected PreToolUse hooks and matchershooks.PostToolUse- Expected PostToolUse hookshooks.Stop- Expected Stop hookshooks.SubagentStop- Expected SubagentStop hooksallowed-tools- Tools the skill is allowed to use
From Markdown Body:
- SubAgents mentioned (
Task(subagent_type="...")) - Skills called (
Skill("...")) - Artifacts created (
.dev-flow/drafts/,.dev-flow/plans/, etc.) - Workflow steps and conditions
Step 2.2: Build Expected Behavior Checklist
Create checklist from SKILL.md analysis:
## Expected Behavior
### SubAgents
- [ ] Explore agent called (parallel, run_in_background)
- [ ] gap-analyzer called before plan generation
- [ ] reviewer called after plan creation
### Hooks
- [ ] PreToolUse[Edit|Write] triggers plan-guard.sh
- [ ] Stop hook validates reviewer approval
### Artifacts
- [ ] Draft file created at .dev-flow/drafts/{name}.md
- [ ] Plan file created at .dev-flow/plans/{name}.md
- [ ] Draft file deleted after OKAY
### Workflow
- [ ] Interview Mode before Plan Generation
- [ ] User explicit request triggers plan generation
- [ ] Reviewer REJECT causes revision loopPhase 3: Analyze Debug Log
The debug log (~/.claude/debug/{sessionId}.txt) contains detailed execution traces.
Step 3.1: Extract SubAgent Calls
Search patterns:
SubagentStart with query: {agent-name}
SubagentStop with query: {agent-id}Use script:
${baseDir}/scripts/extract-subagent-calls.sh {debug-log-path}Step 3.2: Extract Hook Events
Search patterns:
Getting matching hook commands for {HookEvent} with query: {tool-name}
Matched {N} unique hooks for query "{query}"
Hooks: Processing prompt hook with prompt: {prompt}
Hooks: Prompt hook condition was met/not met
permissionDecision: allow/denyUse script:
${baseDir}/scripts/extract-hook-events.sh {debug-log-path}Step 3.3: Extract Tool Calls
Search patterns:
executePreToolHooks called for tool: {tool-name}
File {path} written atomicallyStep 3.4: Extract Hook Results
For prompt-based hooks, find the model response:
Hooks: Model response: {
"ok": true/false,
"reason": "..."
}Show full SKILL.md (157 more words)Show less
Phase 4: Verify Artifacts
Step 4.1: Check File Creation
For each expected artifact:
- Search debug log for
FileHistory: Tracked file modification for {path} - Search for
File {path} written atomically - Verify current filesystem state
Step 4.2: Check File Deletion
For files that should be deleted:
- Search for
rmcommands in Bash calls - Verify file no longer exists on filesystem
Phase 5: Compare Expected vs Actual
Step 5.1: Build Comparison Table
| Component | Expected | Actual | Status |
|-----------|----------|--------|--------|
| Explore agent | 2 parallel calls | 2 calls at 09:39:26 | ✅ |
| gap-analyzer | Called before plan | Called at 09:43:08 | ✅ |
| reviewer | Called after plan | 2 calls (REJECT→OKAY) | ✅ |
| PreToolUse hook | Edit\|Write matcher | Triggered for Write | ✅ |
| Stop hook | Validates approval | Returned ok:true | ✅ |
| Draft file | Created then deleted | Created→Deleted | ✅ |
| Plan file | Created | Exists (10KB) | ✅ |Step 5.2: Identify Deviations
Flag any mismatches:
- Missing component calls
- Wrong order of operations
- Hook failures
- Missing artifacts
- Unexpected errors
Phase 6: Generate Report
Report Template
# Session Analysis Report
## Session Info
- **Session ID**: {sessionId}
- **Target Skill**: {skillPath}
- **Analysis Date**: {date}
---
## 1. Expected Behavior (from SKILL.md)
[Summary of expected workflow]
---
## 2. Skill/SubAgent/Hook Verification
### SubAgents
| SubAgent | Expected | Actual | Time | Result |
|----------|----------|--------|------|--------|
| ... | ... | ... | ... | ✅/❌ |
### Hooks
| Hook | Matcher | Triggered | Result |
|------|---------|-----------|--------|
| ... | ... | ... | ✅/❌ |
---
## 3. Artifacts Verification
| Artifact | Path | Expected State | Actual State |
|----------|------|----------------|--------------|
| ... | ... | ... | ✅/❌ |
---
## 4. Issues/Bugs
| Severity | Description | Location |
|----------|-------------|----------|
| ... | ... | ... |
---
## 5. Overall Result
**Verdict**: ✅ PASS / ❌ FAIL
**Summary**: [1-2 sentence summary]Scripts Reference
| Script | Purpose |
|---|---|
find-session-files.sh | Locate all files for a session ID |
extract-subagent-calls.sh | Parse subagent invocations from debug log |
extract-hook-events.sh | Parse hook events from debug log |
Usage Example
User: "Analyze session 3cc71c9f-d27a-4233-9dbc-c4f07ea6ec5b against .claude/skills/specify/SKILL.md"
1. Find session files
2. Parse SKILL.md → Expected: Explore, gap-analyzer, reviewer, hooks
3. Analyze debug log → Extract actual calls
4. Verify artifacts → Check .dev-flow/
5. Compare → Build verification table
6. Generate report → PASS/FAIL with detailsAdditional Resources
Reference Files
references/analysis-patterns.md- Detailed grep patterns for log analysisreferences/common-issues.md- Known issues and troubleshooting
Scripts
scripts/find-session-files.sh- Session file locatorscripts/extract-subagent-calls.sh- SubAgent call extractorscripts/extract-hook-events.sh- Hook event extractor
© team-attention, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in plugins/session-wrap/skills/session-analyzer of team-attention/plugins-for-claude-natives.
- SKILL.md
- references/analysis-patterns.md
- references/common-issues.md
- scripts/extract-hook-events.sh
- scripts/extract-subagent-calls.sh
- scripts/find-session-files.sh
Open the folder on GitHubat commit fd9c207
Compare with similar skills
Session Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Session Analyzer this skillteam-attention/plugins-for-claude-natives | 825 | — | ~1.8k | Automated safety check: Pass | MIT | |
| AnalyzeriBigQiang/feedgrab | 613 | — | ~1k | Automated safety check: Pass | MIT | |
| Agent Code Analyzerruvnet/ruflo | 74k | 3 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Agent Pagerank Analyzerruvnet/ruflo | 74k | 3 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Agent Performance Analyzerruvnet/ruflo | 74k | 2 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Diff Analyzeruvnet/ruflo | 74k | — | ~450 | Automated safety check: Notes | MIT |
Similar skills
Agent Code Analyzer
ruvnet/ruflo
Agent skill for code-analyzer - invoke with $agent-code-analyzer
Agent Pagerank Analyzer
ruvnet/ruflo
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer
Agent Performance Analyzer
ruvnet/ruflo
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer
Diff Analyze
ruvnet/ruflo
Analyze git diffs for risk scoring, reviewer recommendations, and change classification.
Agent Analyze Code Quality
ruvnet/ruflo
Agent skill for analyze-code-quality - invoke with $agent-analyze-code-quality
More from team-attention/plugins-for-claude-natives
All 16 skills in this repoGmail
team-attention/plugins-for-claude-natives
This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail.
History Insight
team-attention/plugins-for-claude-natives
This skill should be used when user wants to access, capture, or reference Claude Code session history.
Tech Decision
team-attention/plugins-for-claude-natives
This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical…
Youtube Digest
team-attention/plugins-for-claude-natives
This skill should be used when the user asks to "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈", or provides a YouTube URL for analysis.
Fetch Tweet
team-attention/plugins-for-claude-natives
This skill should be used when the user asks to "트윗 가져와", "트윗 번역", "X 게시글 읽어줘", "tweet fetch", "트윗 내용", "트윗 원문", or provides an X/Twitter URL (x.com, twitter.com) and wants to read, translate, or…
Podcast
team-attention/plugins-for-claude-natives
Generate Korean podcast episodes from any source (URLs, tweets, articles, PDFs) — analyzes content, writes a script, generates audio via OpenAI TTS, converts to MP4, and auto-uploads to YouTube.
Questions about Session Analyzer
What does Session Analyzer do?
This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…. Session Analyzer is an agent skill from team-attention/plugins-for-claude-natives. This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session.
When should I use Session Analyzer?
Session Analyzer fits situations like: asks to analyze session; evaluate skill execution; check session logs; provides a session ID with a skill path.
How do I install Session Analyzer in Claude Code?
Run `npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a claude-code`. Or copy the skill folder (plugins/session-wrap/skills/session-analyzer in team-attention/plugins-for-claude-natives) into .claude/skills/session-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Session Analyzer in Codex?
Run `npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a codex`. Or copy the skill folder (plugins/session-wrap/skills/session-analyzer in team-attention/plugins-for-claude-natives) into .agents/skills/session-analyzer in your project. Codex loads it when a task matches its description.
Can I use Session Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add team-attention/plugins-for-claude-natives --skill session-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-analyzer, .gemini/skills/session-analyzer, .github/skills/session-analyzer and .opencode/skills/session-analyzer in your project.
What does Session Analyzer need to run?
Going by SKILL.md and its folder, Session Analyzer needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Session Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Session Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Session Analyzer use?
Session Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Session Analyzer use?
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
What are the alternatives to Session Analyzer?
Skills that share tags, products or a category with Session Analyzer: Analyzer (iBigQiang/feedgrab, 613 stars), Agent Code Analyzer (ruvnet/ruflo, 74k stars), Agent Pagerank Analyzer (ruvnet/ruflo, 74k stars) and Agent Performance Analyzer (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Session Analyzer?
team-attention (a GitHub organization) maintains it in team-attention/plugins-for-claude-natives, which has 825 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 20, 2026.
Source: team-attention/plugins-for-claude-natives on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.