From grammarly-pack
Optimizes Grammarly API costs through tier selection, sampling, and usage monitoring. Use when analyzing Grammarly billing, reducing API costs, or implementing budget alerts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grammarly-pack:grammarly-cost-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Grammarly API pricing is enterprise/custom. Contact Grammarly for volume pricing.
Grammarly API pricing is enterprise/custom. Contact Grammarly for volume pricing.
Same text produces same scores — cache aggressively to avoid duplicate API calls.
function shouldScore(text: string): boolean {
const words = text.split(/\s+/).length;
if (words < 30) return false; // API will reject
if (words > 50000) return false; // Too expensive, chunk first
return true;
}
// For bulk content, score a sample instead of everything
function selectSample(documents: string[], sampleRate = 0.2): string[] {
return documents.filter(() => Math.random() < sampleRate);
}
let apiCalls = { score: 0, ai: 0, plagiarism: 0 };
// Increment on each call, report daily
For architecture, see grammarly-reference-architecture.
npx claudepluginhub ia23a-lachnita/claude-code-plugins-plus-fix-skills --plugin grammarly-pack2plugins reuse this skill
First indexed Jul 17, 2026
Optimize Grammarly costs through tier selection, sampling, and usage monitoring. Use when analyzing Grammarly billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "grammarly cost", "grammarly billing", "reduce grammarly costs", "grammarly pricing", "grammarly expensive", "grammarly budget".
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.