Search
Backend & APIs · Notion · By jeremylongshore
Skills
Sort:BestMost starsTrending todayTrending this weekTrending this monthNewestRecently updatedName
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | Choose a Notion integration architecture from explicit consistency, latency, security, and recovery requirements. | jeremylongshore/ | 2.8k | — | ~1k | Automated safety check: Pass | MIT | yesterday |
| 2 | Classify Notion API failures and choose a bounded recovery path from the observed status and error code. | jeremylongshore/ | 2.8k | — | ~979 | Automated safety check: Pass | MIT | yesterday |
| 3 | Reduce Notion integration waste across requests, workers, storage, and downstream processing without inventing API pricing. | jeremylongshore/ | 2.8k | — | ~957 | Automated safety check: Pass | MIT | yesterday |
| 4 | Define data classification, minimization, retention, and deletion controls for a Notion integration. | jeremylongshore/ | 2.8k | — | ~977 | Automated safety check: Pass | MIT | yesterday |
| 5 | Map Notion connection capabilities, content access, user context, and application roles into an auditable authorization model. | jeremylongshore/ | 2.8k | — | ~1k | Automated safety check: Pass | MIT | yesterday |
| 6 | Establish a least-privilege Notion connection and tested API contract without leaking credentials. | jeremylongshore/ | 2.8k | — | ~993 | Automated safety check: Pass | MIT | yesterday |
| 7 | Audit a Notion integration for recurring identity, access, version, pagination, webhook, and mutation mistakes. | jeremylongshore/ | 2.8k | — | ~964 | Automated safety check: Pass | MIT | yesterday |
| 8 | Create a repeatable local Notion development loop using fixtures, mocks, and an explicitly shared sandbox. | jeremylongshore/ | 2.8k | — | ~949 | Automated safety check: Pass | MIT | yesterday |
| 9 | Define isolated development, staging, and production Notion connections, secrets, content roots, and promotion rules. | jeremylongshore/ | 2.8k | — | ~963 | Automated safety check: Pass | MIT | yesterday |
| 10 | Improve Notion integration latency and throughput while preserving completeness, fairness, and limit compliance. | jeremylongshore/ | 2.8k | — | ~975 | Automated safety check: Pass | MIT | yesterday |
| 11 | Decide whether a Notion integration is ready for production from evidence across access, contracts, correctness, safety, and operations. | jeremylongshore/ | 2.8k | — | ~973 | Automated safety check: Pass | MIT | yesterday |
| 12 | Implement adaptive Notion request throttling and bounded retry behavior from observed responses. | jeremylongshore/ | 2.8k | — | ~926 | Automated safety check: Pass | MIT | yesterday |
| 13 | Establish a security baseline for Notion credentials, capabilities, content access, webhooks, writes, logs, and tenant isolation. | jeremylongshore/ | 2.8k | — | ~1k | Automated safety check: Pass | MIT | yesterday |
| 14 | Upgrade a Notion integration across SDK or API contracts with inventory, compatibility tests, staged rollout, and rollback. | jeremylongshore/ | 2.8k | — | ~1k | Automated safety check: Pass | MIT | yesterday |
| 15 | Implement verified Notion connection-webhook intake with deduplication, bounded processing, and fetch-current reconciliation. | jeremylongshore/ | 2.8k | — | ~1k | Automated safety check: Pass | MIT | yesterday |
| 16 | Implement event-driven Glean indexing triggered by source system webhooks from GitHub, Confluence, Notion, and other content platforms. | jeremylongshore/ | 2.8k | — | ~1.4k | Automated safety check: Pass | MIT | yesterday |