Growth Log
affaan-m/ECC
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…
A skill your agent uses when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.
Apache-2.0Auto-check passed
Install Logging Tradeoffs
$ npx skills add ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins logging-tradeoffs --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/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .claude/skills/logging-tradeoffs && 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 "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .claude/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffsType 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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins logging-tradeoffs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .agents/skills/logging-tradeoffs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .agents/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins logging-tradeoffs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .cursor/skills/logging-tradeoffs && 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 "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .cursor/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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/ccplugins/awesome-claude-code-plugins.git --path plugins/craftsman/skills/logging-tradeoffs--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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins logging-tradeoffs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .gemini/skills/logging-tradeoffs && 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 "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .gemini/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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 ccplugins/awesome-claude-code-plugins logging-tradeoffsInstalls 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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .github/skills/logging-tradeoffs && 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 "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .github/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins logging-tradeoffs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/craftsman/skills/logging-tradeoffs .opencode/skills/logging-tradeoffs && 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 "logging-tradeoffs" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/craftsman/skills/logging-tradeoffs into .opencode/skills/logging-tradeoffs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "logging-tradeoffs", 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
logging-tradeoffs- GitHub stars
- 968
- Token cost
- ~631 tokens
- SKILL.md length
- 324 words
- Files
- 1
- Skills in repo
- 66
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.
- Works in 3 steps: Check whether KNOWN_ISSUES.md already… → If the project has… → Ask before creating the file if it…
- A deliberate shortcut is taken during a fix
- SKILL.md covers Overview, Before creating a new entry, Entry format and When touching a file with an…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Logging Tradeoffs is an agent skill from ccplugins/awesome-claude-code-plugins. Use when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.
Its SKILL.md is about 630 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: Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code. The licence is Apache-2.0.
When your agent uses it
- A deliberate shortcut is taken during a fix
- Investigating a bug that might already be logged
- Closing out an entry after a proper fix lands
Example prompts
- “/logging-tradeoffs”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Check whether KNOWN_ISSUES.md already exists at the project root. If an equivalent file
- If the project has graphify-out/graph.json, use the graphify-recurring-bugs skill's dedup
- Ask before creating the file if it doesn't exist yet. This is a new file the user didn't
What it can do on your machine
Read from SKILL.md and the folder at commit 5bd4f16. 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
Logging Tradeoffs loads about 631 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 324 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from ccplugins/awesome-claude-code-plugins at commit 5bd4f16, republished under its Apache-2.0 licence (© ccplugins). 324 words, ~631 tokens.
Download SKILL.mdSave it as
.claude/skills/logging-tradeoffs/SKILL.md (or your agent's skills folder).- name
- logging-tradeoffs
- description
- Use when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.
Logging Tradeoffs
Overview
A shortcut without a record is a landmine for whoever touches the code next — often future-you.
This skill defines one convention, KNOWN_ISSUES.md, kept at the root of each project, so
deliberate tradeoffs are findable instead of rediscovered the hard way.
Core principle: if you knowingly ship something imperfect, write down what, why, and when to revisit it — in the same motion as writing the code, not as a follow-up you'll forget.
Before creating a new entry
- Check whether
KNOWN_ISSUES.mdalready exists at the project root. If an equivalent file exists under a different name (TODO.md,ISSUES.md,BACKLOG.md), don't create a duplicate — ask the user whether to adopt the existing file for this convention instead. - If the project has
graphify-out/graph.json, use thegraphify-recurring-bugsskill's dedup check first — a new bug may be the same root cause as an existing open entry, not a new one. - Ask before creating the file if it doesn't exist yet. This is a new file the user didn't explicitly request — surface the proposed content, get a yes, then write it.
Entry format
Append one block per issue, most recent first:
## <date> — <short title>
- What changed / what shortcut was taken:
- Ceiling (when this breaks):
- Upgrade trigger (what to do when it's hit):
- Status: open | resolved (<date>, <how>)- What changed: the concrete simplification, with a
file:linereference where relevant. - Ceiling: the specific condition under which this stops being good enough — not vague, a testable fact ("more than 10k rows", "concurrent writers", "amounts with fractional cents").
- Upgrade trigger: what to actually do when the ceiling is hit — a real next step, not "fix it properly later."
- Status: flip to
resolvedwith a date and one line on how, when addressed. Don't delete resolved entries — they're evidence the log is actually maintained, not decoration.
When touching a file with an open entry
If reviewer or coder touches a file referenced by an open KNOWN_ISSUES.md entry, say
explicitly whether the current change resolves that entry, is unrelated to it, or makes it worse.
Silence here is how the same shortcut gets shipped around three times.
© ccplugins, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/craftsman/skills/logging-tradeoffs of ccplugins/awesome-claude-code-plugins.
Open the folder on GitHubat commit 5bd4f16
Compare with similar skills
Logging Tradeoffs 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 |
|---|---|---|---|---|---|---|
| Logging Tradeoffs this skillccplugins/awesome-claude-code-plugins | 968 | — | ~631 | Automated safety check: Pass | Apache-2.0 | |
| Growth Logaffaan-m/ECC | 275k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Studio Shortcutssupabase/supabase | 111k | — | ~919 | Automated safety check: Pass | Apache-2.0 | |
| Investigating LogsPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Logging and Error Reporting for Warpwarpdotdev/warp | 65k | 1 repos | ~5.6k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
- Official
Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
- Official
Studio Shortcuts
supabase/supabase
Keyboard shortcut conventions for Supabase Studio. An agent skill from supabase/supabase.
- Official
Investigating Logs
PostHog/posthog
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
Logging and Error Reporting for Warp
warpdotdev/warp
Guides log level choices and when to raise a structured Sentry event instead of a plain log line in the Warp Rust codebase, keeping secrets out of logs.
Analyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
More from ccplugins/awesome-claude-code-plugins
All 66 skills in this repoAI Meeting
ccplugins/awesome-claude-code-plugins
Run structured AI meetings for plans, product ideas, technical designs, business decisions, feature proposals, and strategy choices.
Fastapi App
ccplugins/awesome-claude-code-plugins
Bootstrap a new FastAPI backend with async SQLAlchemy 2.0, asyncpg, Alembic, Pydantic v2, and no deprecated APIs.
Flutter App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs.
Nextjs App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Next.js (App Router, TypeScript) web app with current packages and no deprecated APIs.
Dev Report
ccplugins/awesome-claude-code-plugins
Write up a coding session for a non-technical stakeholder — the context, what was built, and the engineering reasoning behind it — the way a senior engineer briefs a product manager who does not…
Difesa Attacchi
ccplugins/awesome-claude-code-plugins
Aggiunge a un sito/app un agente di difesa che rileva e blocca richieste malevole (SQL injection, XSS, path traversal, brute force, bot) con rate limiting, blocklist IP e modalità lockdown che…
Questions about Logging Tradeoffs
What does Logging Tradeoffs do?
A skill your agent uses when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands. Logging Tradeoffs is an agent skill from ccplugins/awesome-claude-code-plugins. Use when a deliberate shortcut is taken during a fix or feature, when investigating a bug that might already be logged, or when closing out an entry after a proper fix lands.
When should I use Logging Tradeoffs?
Logging Tradeoffs fits situations like: A deliberate shortcut is taken during a fix; investigating a bug that might already be logged; closing out an entry after a proper fix lands.
How do I install Logging Tradeoffs in Claude Code?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a claude-code`. Or copy the skill folder (plugins/craftsman/skills/logging-tradeoffs in ccplugins/awesome-claude-code-plugins) into .claude/skills/logging-tradeoffs in your project. Claude Code loads it when a task matches its description.
How do I install Logging Tradeoffs in Codex?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a codex`. Or copy the skill folder (plugins/craftsman/skills/logging-tradeoffs in ccplugins/awesome-claude-code-plugins) into .agents/skills/logging-tradeoffs in your project. Codex loads it when a task matches its description.
Can I use Logging Tradeoffs 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 ccplugins/awesome-claude-code-plugins --skill logging-tradeoffs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/logging-tradeoffs, .gemini/skills/logging-tradeoffs, .github/skills/logging-tradeoffs and .opencode/skills/logging-tradeoffs in your project.
What does Logging Tradeoffs need to run?
SKILL.md names no scripts, command-line tools or credentials: Logging Tradeoffs is instructions for the agent only.
Does Logging Tradeoffs 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 Logging Tradeoffs 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 Logging Tradeoffs use?
Logging Tradeoffs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Logging Tradeoffs use?
About 631 tokens (SKILL.md is roughly 2.5k 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 Logging Tradeoffs?
Skills that share tags, products or a category with Logging Tradeoffs: Growth Log (affaan-m/ECC, 275k stars), Clickhouse Logs Queries (supabase/supabase, 111k stars), Studio Shortcuts (supabase/supabase, 111k stars) and Investigating Logs (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Logging Tradeoffs?
ccplugins (a GitHub organization) maintains it in ccplugins/awesome-claude-code-plugins, which has 968 GitHub stars. The repository holds 66 skills in this directory. The repository was last updated on August 12, 2026.
Source: ccplugins/awesome-claude-code-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.