From evernote-pack
Optimizes Evernote API costs by monitoring upload quotas, compressing images, estimating note sizes, and enabling cleanup/alerts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/evernote-pack:evernote-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
Optimize resource usage and manage costs in Evernote integrations, focusing on monthly upload quotas, storage efficiency, image compression, and account limit monitoring.
Optimize resource usage and manage costs in Evernote integrations, focusing on monthly upload quotas, storage efficiency, image compression, and account limit monitoring.
user.accountingQuery userStore.getUser() to access user.accounting which contains uploadLimit, uploaded, and uploadLimitEnd. Calculate remaining quota and percentage used.
async function getQuotaStatus(userStore) {
const user = await userStore.getUser();
const { uploadLimit, uploaded, uploadLimitEnd } = user.accounting;
return {
totalMB: Math.round(uploadLimit / 1024 / 1024),
usedMB: Math.round(uploaded / 1024 / 1024),
remainingMB: Math.round((uploadLimit - uploaded) / 1024 / 1024),
percentUsed: Math.round((uploaded / uploadLimit) * 100),
resetsAt: new Date(uploadLimitEnd)
};
}
Compress images before attaching to notes. Resize large images to a maximum dimension (e.g., 1920px). Convert PNG screenshots to JPEG for smaller file sizes. Skip attaching files that exceed the single-note size limit (25MB for Basic, 200MB for Premium).
function estimateNoteSize(content, resources = []) {
const contentBytes = Buffer.byteLength(content, 'utf8');
const resourceBytes = resources.reduce((sum, r) => sum + r.data.size, 0);
return contentBytes + resourceBytes;
}
function canUpload(noteSize, remainingQuota) {
return noteSize < remainingQuota;
}
Check quota before creating notes with large attachments. Use findNotesMetadata() for read operations (zero upload cost). Batch small notes into single notes where appropriate.
Find large notes consuming quota. List notes sorted by content length to identify optimization candidates. Remove unused resources and delete notes in trash to reclaim space.
Send alerts when upload usage exceeds thresholds (e.g., 75%, 90%, 95%). Log quota status after each upload operation for trend analysis.
For the complete quota monitor, image optimizer, cleanup utilities, and alert system, see Implementation Guide.
| Limit | Basic | Premium | Business |
|---|---|---|---|
| Monthly upload | 60 MB | 10 GB | 20 GB/user |
| Single note size | 25 MB | 200 MB | 200 MB |
| Notebooks | 250 | 250 | 10,000 |
| Tags | 100,000 | 100,000 | 100,000 |
| Notes | 100,000 | 100,000 | 500,000 |
| Error | Cause | Solution |
|---|---|---|
QUOTA_REACHED | Monthly upload limit exceeded | Wait for quota reset at uploadLimitEnd |
LIMIT_REACHED | Too many notebooks or tags | Delete unused notebooks, merge duplicate tags |
DATA_REQUIRED | Empty note after optimization | Ensure note still has content after compression |
BAD_DATA_FORMAT | Attachment hash mismatch | Recompute MD5 hash after image compression |
For architecture patterns, see evernote-reference-architecture.
Quota dashboard: Build a dashboard showing current upload usage (MB used / total), days until reset, largest notes by size, and projected usage based on recent trends.
Image pipeline: Before attaching images, resize to max 1920px width, convert PNG to JPEG at 80% quality, check resulting size against remaining quota, and skip if insufficient.
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin evernote-pack5plugins reuse this skill
First indexed Jul 10, 2026
Optimize Evernote integration costs by monitoring API quotas, compressing images, and managing upload limits.
Optimize costs and API usage for OneNote Graph API integrations with caching and batching strategies. Use when reducing API call volume, planning capacity, or evaluating OneNote integration costs. Trigger with "onenote costs", "onenote api usage", "onenote optimization", "graph api billing onenote".
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.