amhuppert/compress
claude/ai-resources-plugin/skills/compress/SKILL.md
Compress and optimize AI instructions to be clearer, more concise, and more efficient.
$ install --global
skillsauthnpx skillsauth add amhuppert/my-ai-resources compressInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:46 AM285.6s1 file scanned
SKILL.md
- name:
- compress
- description:
- Compress and optimize AI instructions to be clearer, more concise, and more efficient.
- disable-model-invocation:
- true
Instruction Optimizer
You are an AI instruction optimizer tasked with refining and improving instructions for LLM agents. Your goal: create clear, concise, efficient instructions while maintaining effectiveness.
Here are the original instructions to optimize:
<original_instructions> $ARGUMENTS </original_instructions>
Analyze and optimize these instructions. Follow these steps:
- Analyze original instructions
- Remove redundancies and non-essential info
- Optimize for AI context window efficiency
- Create concise examples (positive and negative)
- Apply formatting guidelines
- Ensure overall effectiveness and clarity
Before final output, wrap your analysis in <instruction_analysis> tags inside your thinking block:
- Identify key components and their purpose
- Assess current clarity and effectiveness
- Note areas for potential improvement
- List redundancies and non-essential info
- Outline context window efficiency optimization
- Plan concise examples
- Note formatting improvements
- Consider maintaining/improving effectiveness and clarity
- Brainstorm multiple compressed versions
Output Format:
- Use concise Markdown for main content
- Employ XML tags: <example>, <danger>, <required>, <critical>
- Indent content within XML tags by 2 spaces
Formatting Guidelines:
- Keep instructions as short as possible without sacrificing clarity/effectiveness
- Use Mermaid syntax for complex rules if clearer/more concise
- Use emojis where appropriate (✅, 🚫)
- Example format:
AI Context Efficiency:
- Limit examples to essential patterns
- Use hierarchical structure for quick parsing
- Remove redundant cross-section information
- Maintain high information density, minimal tokens
- Focus on machine-actionable instructions over human explanations
Compression Guidelines:
- Preserve essential information
- Shorten instructions maximally while maintaining meaning
- Be terse
- Use short phrases over complete sentences when possible
Instruction compression examples:
<example type="valid"> Original: "Please ensure that you carefully review all the provided information before proceeding with your analysis." Compressed: "Review all info before analysis" </example> <example type="valid"> Original: "It is of utmost importance that you maintain a professional tone throughout your response, avoiding any colloquialisms or informal language." Compressed: "Maintain professional tone. No colloquialisms/informal language." - ✅ Preserved requirements - ✅ Removed redundant words, replaced sentences with short phrases </example>Provide negative examples of instruction compression:
<example type="invalid"> Original: "Ensure all financial calculations are accurate to two decimal places and include the appropriate currency symbol." Compressed: "Verify financial calculations" Explanation: Essential information lost. - 🚫 # of decimal places lost - 🚫 currency symbol lost </example>Now, optimize the instructions.
Related Skills
amhuppert/hotkey-helper
tools
VerifiedTrustedCommunity
Use when picking or vetting a keyboard shortcut on macOS. Triggers include "what hotkey should I use for X", "is `<combo>` available", "does this shortcut conflict", "recommend a keybinding for…", "check `<combo>` against my setup", "pick a hotkey for…", or any mention of choosing/binding/changing a shortcut in WezTerm, tmux, Zed, Chrome, Claude Code, or macOS. Determines whether a proposed combo collides with OS-reserved bindings, app defaults, or the user's customizations, and recommends ergonomic alternatives when needed.
2SKILL.mdUpdated Jun 2, 2026
amhuppert/knip
development
VerifiedTrustedCommunity
Detect and remove dead code with knip. Use when the user asks to "run knip", "find unused files", "find unused exports", "find unused dependencies", "clean up dead code", "remove dead code", "set up knip", "configure knip", "knip.json", "knip false positive", "knip CI", or mentions a `knip` config, dependency bloat, bundle bloat from unused imports, or tree-shaking unused exports. Covers the configuration-first workflow, confidence-gated deletion, framework-specific gotchas (Next.js 15+, Tailwind, Storybook, Jest, Bun's test runner and `bun build --compile`), monorepos, CI integration, and performance tuning.
1SKILL.mdUpdated May 27, 2026
amhuppert/react-scan
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up react-scan", "install react-scan", "diagnose React re-renders", "find unnecessary renders", "find unstable props", "automate React render checks with Playwright", "react-scan + playwright", "measure component renders programmatically", "check why a React component is slow", or mentions React rendering issues, slow React interactions, render counts, or component-level perf attribution. Covers install across Next.js/Vite/Remix/script-tag/browser-extension, the lite headless API for CI, and the canonical render-attribution → fix → validate loop driven through Playwright.
1SKILL.mdUpdated May 20, 2026
amhuppert/knowledge-base-ingest
documentation
VerifiedTrustedCommunity
This skill should be used when integrating source material into a knowledge base, including when the user asks to "integrate this document into the knowledge base", "add this transcript to the memory bank", "ingest this document", "update the knowledge base", "analyze a new source document", or "sync current-state docs with this source".
1SKILL.mdUpdated May 17, 2026