evernote-performance-tuning
Optimize Evernote integration performance. Use when improving response times, reducing API calls, or scaling Evernote integrations. Trigger with phrases like "evernote performance", "optimize evernote", "evernote speed", "evernote caching".
What this skill does
# Evernote Performance Tuning
## Overview
Optimize Evernote API integration performance through response caching, efficient data retrieval, request batching, connection management, and performance monitoring.
## Prerequisites
- Working Evernote integration
- Understanding of API rate limits
- Caching infrastructure (Redis recommended, in-memory for simpler setups)
## Instructions
### Step 1: Response Caching
Cache frequently accessed data (notebook lists, tag lists, note metadata) with TTL-based expiration. Notebook and tag lists change rarely -- cache for 5-15 minutes. Note metadata can be cached for 1-5 minutes.
```javascript
class EvernoteCache {
constructor(redis) {
this.redis = redis;
}
async getOrFetch(key, fetcher, ttlSeconds = 300) {
const cached = await this.redis.get(key);
if (cached) return JSON.parse(cached);
const data = await fetcher();
await this.redis.setex(key, ttlSeconds, JSON.stringify(data));
return data;
}
async listNotebooks(noteStore) {
return this.getOrFetch('notebooks', () => noteStore.listNotebooks(), 600);
}
async listTags(noteStore) {
return this.getOrFetch('tags', () => noteStore.listTags(), 600);
}
}
```
### Step 2: Efficient Data Retrieval
Use `findNotesMetadata()` instead of `findNotes()` to avoid transferring full note content. Only request needed fields in `NotesMetadataResultSpec`. Fetch full content only when the user explicitly opens a note.
```javascript
// BAD: Fetches full content for all notes
const notes = await noteStore.findNotes(filter, 0, 100);
// GOOD: Fetches only metadata (title, dates, tags)
const metadata = await noteStore.findNotesMetadata(filter, 0, 100, spec);
// Fetch content only for the specific note user opens
const fullNote = await noteStore.getNote(guid, true, false, false, false);
```
### Step 3: Request Batching
Batch multiple operations using sync chunks instead of individual API calls. Use `getSyncChunk()` to fetch up to 100 changed notes in a single call instead of 100 `getNote()` calls.
### Step 4: Connection Optimization
Reuse the Evernote client instance across requests. The NoteStore maintains an HTTP connection that benefits from keep-alive. Create one client per user session, not per request.
### Step 5: Performance Monitoring
Track API call counts, response times (p50, p95, p99), cache hit rates, and rate limit occurrences. Alert on degradation.
For the complete caching layer, batching strategies, monitoring setup, and benchmark examples, see [Implementation Guide](references/implementation-guide.md).
## Output
- Redis-based response caching with TTL management
- Metadata-only query patterns (avoid unnecessary content transfer)
- Sync chunk batching for bulk operations
- Client instance reuse for connection optimization
- Performance monitoring with latency percentiles and cache hit rates
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `RATE_LIMIT_REACHED` | Too many API calls | Increase cache TTL, batch operations |
| Stale cache data | Cache not invalidated on update | Invalidate cache on webhook notification |
| Redis connection failure | Cache infrastructure down | Fall through to direct API call |
| Slow responses | Large note content in response | Use `findNotesMetadata()` for listings |
## Resources
- [Rate Limits](https://dev.evernote.com/doc/articles/rate_limits.php)
- [Synchronization (bulk fetch)](https://dev.evernote.com/doc/articles/synchronization.php)
- [API Reference](https://dev.evernote.com/doc/reference/)
- [Redis Documentation](https://redis.io/documentation)
## Next Steps
For cost optimization, see `evernote-cost-tuning`.
## Examples
**Cache notebook lookups**: Cache `listNotebooks()` for 10 minutes. On 100 requests/minute, this reduces API calls from 100 to 1 per 10-minute window (99% reduction).
**Lazy content loading**: Show note titles from cached metadata. Fetch full ENML content only when user clicks to read. Reduces average response time from 500ms to 50ms for list views.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.