Agent skill

Perf Investigation Logger

by composio-community in composio-community/awesome-claude-plugins

A skill your agent uses when appending structured perf investigation notes and evidence.

No licenceAuto-check passed

Install Perf Investigation Logger

skills CLI
$ npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install composio-community/awesome-claude-plugins perf-investigation-logger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/composio-community/awesome-claude-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/perf/skills/investigation-logger .claude/skills/perf-investigation-logger && rm -rf skills-src

Use ~/.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/

Facts

Skill name
perf-investigation-logger
GitHub stars
1.9k
Token cost
~188 tokens
SKILL.md length
48 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when appending structured perf investigation notes and evidence.

  • Works in 4 steps: Exact user quotes (verbatim) → Phase summary → Decisions and rationale → …
  • Appending structured perf investigation notes and evidence
  • SKILL.md covers Required Content, Output Format and Constraints
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Perf Investigation Logger is an agent skill from composio-community/awesome-claude-plugins. Use when appending structured perf investigation notes and evidence.

Its SKILL.md is about 190 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A curated list of Plugins that let you extend Claude Code with custom commands, agents, hooks, and MCP servers through the plugin system.

When your agent uses it

  • Appending structured perf investigation notes and evidence

Example prompts

  • “/perf-investigation-logger”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Exact user quotes (verbatim)
  2. Phase summary
  3. Decisions and rationale
  4. Evidence pointers (files, metrics, commands)

What it can do on your machine

Read from SKILL.md and the folder at commit e521f7a. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Perf Investigation Logger loads about 188 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 48 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~188

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); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 48 words (~188 tokens).

“Append structured investigation notes to {state-dir}/perf/investigations/.md.”

— opening of SKILL.md by composio-community
name
perf-investigation-logger
version
1.0.0

Read the full SKILL.md on GitHub

Files

Just SKILL.md in perf/skills/investigation-logger of composio-community/awesome-claude-plugins.

Open the folder on GitHubat commit e521f7a

Compare with similar skills

Perf Investigation Logger 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.

Perf Investigation Logger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Perf Investigation Logger this skillcomposio-community/awesome-claude-plugins1.9k—~188Automated safety check: PassNone
Root Cause Investigationgarrytan/gstack136k—~13kAutomated safety check: NotesMIT
Osint Investigationaffaan-m/ECC276k—~5.7kAutomated safety check: PassCC-BY-SA-4.0
Investigate CIClickHouse/ClickHouse50k—~11kAutomated safety check: NotesApache-2.0
Perf ComparisonClickHouse/ClickHouse50k—~3.9kAutomated safety check: NotesApache-2.0
Investigate Issuevideojs/video.js40k—~318Automated safety check: PassCustom licence

Similar skills

  • Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~13k tokensUpdated today
    DevelopmentAuto-check: notes
  • Sparse-clue OSINT investigation methodology for extracting overlooked leads, connecting fragmented evidence, and testing explanations across sources.

    276k GitHub stars~5.7k tokensUpdated yesterday
    SecurityAuto-check passed
  • Investigate CI

    ClickHouse/ClickHouse

    Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL.

    50k GitHub stars~11k tokensUpdated today
    DatabasesAuto-check: notes
  • Perf Comparison

    ClickHouse/ClickHouse

    Evaluate ClickHouse performance test results from existing CI/dashboard data or local perf.py runs.

    50k GitHub stars~3.9k tokensUpdated today
    DatabasesAuto-check: notes
  • Investigate Issue

    videojs/video.js

    Investigate GitHub issues without changing code. An agent skill from videojs/video.js.

    40k GitHub stars~318 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Investigating Replay

    PostHog/posthog

    Official

    Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass.

    40k GitHub stars~2.4k tokensUpdated yesterday
    DatabasesAuto-check passed

More from composio-community/awesome-claude-plugins

All 12 skills in this repo
  • Reflecting On Sessions

    composio-community/awesome-claude-plugins

    A skill your agent uses when completing a plan, finishing a development branch, wrapping up a session, or at any natural transition between work phases — reviews skill-bus telemetry to identify…

    1.9k GitHub stars~570 tokensUpdated 2 mo ago
    Auto-check passed
  • Perf Analyzer

    composio-community/awesome-claude-plugins

    A skill your agent uses when synthesizing perf findings into evidence-backed recommendations and decisions.

    1.9k GitHub stars~195 tokensUpdated 2 mo ago
    Auto-check passed
  • Perf Benchmarker

    composio-community/awesome-claude-plugins

    A skill your agent uses when running performance benchmarks, establishing baselines, or validating regressions with sequential runs.

    1.9k GitHub stars~269 tokensUpdated 2 mo ago
    Auto-check passed
  • Perf Code Paths

    composio-community/awesome-claude-plugins

    A skill your agent uses when mapping code paths, entrypoints, and likely hot files before profiling.

    1.9k GitHub stars~195 tokensUpdated 2 mo ago
    Auto-check passed
  • Perf Theory Gatherer

    composio-community/awesome-claude-plugins

    A skill your agent uses when generating performance hypotheses backed by git history and code evidence.

    1.9k GitHub stars~208 tokensUpdated 2 mo ago
    Auto-check passed
  • Pause Subs

    composio-community/awesome-claude-plugins

    Temporarily disable the skill bus. An agent skill from composio-community/awesome-claude-plugins.

    1.9k GitHub stars~222 tokensUpdated 2 mo ago
    Auto-check passed

Questions about Perf Investigation Logger

What does Perf Investigation Logger do?

A skill your agent uses when appending structured perf investigation notes and evidence. Perf Investigation Logger is an agent skill from composio-community/awesome-claude-plugins. Use when appending structured perf investigation notes and evidence.

When should I use Perf Investigation Logger?

Perf Investigation Logger fits situations like: appending structured perf investigation notes and evidence.

How do I install Perf Investigation Logger in Claude Code?

Run `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -a claude-code`. Or copy the skill folder (perf/skills/investigation-logger in composio-community/awesome-claude-plugins) into .claude/skills/perf-investigation-logger in your project. Claude Code loads it when a task matches its description.

How do I install Perf Investigation Logger in Codex?

Run `npx skills add composio-community/awesome-claude-plugins --skill perf-investigation-logger -a codex`. Or copy the skill folder (perf/skills/investigation-logger in composio-community/awesome-claude-plugins) into .agents/skills/perf-investigation-logger in your project. Codex loads it when a task matches its description.

Can I use Perf Investigation Logger 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 composio-community/awesome-claude-plugins --skill perf-investigation-logger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/perf-investigation-logger, .gemini/skills/perf-investigation-logger, .github/skills/perf-investigation-logger and .opencode/skills/perf-investigation-logger in your project.

What does Perf Investigation Logger need to run?

SKILL.md names no scripts, command-line tools or credentials: Perf Investigation Logger is instructions for the agent only.

Does Perf Investigation Logger 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 Perf Investigation Logger 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. Review the folder before installing.

What licence does Perf Investigation Logger use?

No licence was found for Perf Investigation Logger or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Perf Investigation Logger use?

About 188 tokens (SKILL.md is roughly 752 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Perf Investigation Logger?

Skills that share tags, products or a category with Perf Investigation Logger: Root Cause Investigation (garrytan/gstack, 136k stars), Osint Investigation (affaan-m/ECC, 276k stars), Investigate CI (ClickHouse/ClickHouse, 50k stars) and Perf Comparison (ClickHouse/ClickHouse, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Perf Investigation Logger?

composio-community (a GitHub organization) maintains it in composio-community/awesome-claude-plugins, which has 1,936 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 26, 2026.

Source: composio-community/awesome-claude-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.