get-zeked

Token Efficient — Development skill for Claude Code

Development community

Reduces Perplexity Computer output verbosity and token waste.

How to install Token Efficient

This entry records only its repository, not the path inside it, so there is no exact command to give. Open get-zeked/token-efficient and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Token Efficient does

Reduces Perplexity Computer output verbosity and token waste. Adapted from drona23/claude-token-efficient for the Perplexity Computer environment. Drop-in SKILL.md, no setup.

Alternatives in Development

  • Claude Token Efficient — One CLAUDE.md file 3.8k ★
  • Doctor — Environment diagnostics with interactive fixes — providers, auth, RTK, hooks, token optimization 2.8k ★
  • Mem0 Chrome Extension — OpenMemory Chrome Extension: Long-term memory for ChatGPT, Claude, Perplexity, Grok etc 671 ★

README

token-efficient

Adapted from [drona23/claude-token-efficient](https://github.com/drona23/claude-token-efficient) for Perplexity Computer.

One SKILL.md file. Drop it in. Cuts the filler Perplexity Computer adds to every response — narrated tool calls, sycophantic openers, post-action summaries, redundant confirmations — without losing any useful signal.

The Problem

By default, Perplexity Computer:

  • Opens with "Great question!" / "Sure!" / "Happy to help!"
  • Narrates every tool call: "Let me search for that...", "Now I'll read the file..."
  • Summarizes what it just did after doing it: "I've successfully created the file at /path/..."
  • Restates your question before answering it
  • Adds "Let me know if you need anything else!" to everything
  • Creates todo lists for 2-step tasks
  • Delegates to subagents when one direct tool call would suffice
  • Over-qualifies simple answers with unnecessary caveats

All of this costs tokens. None of it adds value.

The Fix

Upload `SKILL.md` to your Perplexity Computer skills. It activates on every session automatically.

What It Fixes

# Problem Fix
1 Sycophantic openers/closers No filler phrases — just answer
2 Narrated tool usage Execute tools silently
3 Post-action summaries If the user can see the result, don't describe it
4 Restating the question Answer directly
5 Redundant file confirmations File is visible in UI — don't narrate the path
6 Unnecessary todo lists Just do the task if it's under 3 steps
7 Over-delegation to subagents Direct tool call when one call is enough
8 Decorative Unicode Plain hyphens and straight quotes only
9 Excessive caveats Save qualifications for genuine edge cases
10 Pre-action planning narration Do, don't announce

Profiles

Profile Best For
Universal Any Perplexity Computer session
Coding Dev work, code review, debugging in th