zyte-api-automation
Automate Zyte API tasks via Rube MCP (Composio). Always search tools first for current schemas.
Намерете инструкция, прочетете оригиналния файл и подгответе команда за своя инструмент.
31 301 skills в каталога
Как подбирам и измервамДанните имат нужда от нова проверка.Последна успешна проверка: 23.09.2026 г.
Проверката на източника не означава, че всяка инструкция е изпробвана от Level8. Каталогът не обхваща непременно всички публични хранилища.
Търсене в целия индекс. Метаданните показват посоченото от източника; липсващите стойности остават означени.
Датата в GitHub е отделна от първата поява в моя индекс. Филтърът по дата изключва записите без посочено обновяване.
Страница 8: 24 записа в 2 групи по репозиторий. Всички записи от страницата са показани. Номерът пази позицията от избраната подредба.
1 skill от този източник на тази страница
Automate Zyte API tasks via Rube MCP (Composio). Always search tools first for current schemas.
23 skills от този източник на тази страница
Use when reviewing navigation performance, browser lifecycle events, or resume-from-memory behavior. Check the actual browser lifecycle and restore path, not only static code patterns.
Use when reviewing HTML source and JavaScript for links or resource URLs pointing to domains listed in common adblocker filter lists.
Use when auditing slow page loads, heavy assets, or rendering delays related to Perform browser-based performance audits. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when reviewing templates, rendered HTML, or shared components related to Remove comments and debug code in production. Validate the final browser-facing markup, not just the source framework abstraction.
Use when reviewing large SPA bundles, new dependency additions, or routes that feel slow to hydrate. Focus on code that is not required for the initial view and can move behind route transitions, user interaction, or viewport-based loading.
Use when reviewing utility functions, component props, or template strings that format numbers, prices, or dates to check whether Intl APIs are used correctly.
Use when reviewing form components, API payloads, or client-side storage to identify fields that are collected but not consumed by a stated feature.
Use when applies to all HTML documents. Always check the very first line of the raw HTML source (view-source: or DevTools > Network > Response). In SSR frameworks, check the root HTML template (e.g., _document.tsx in Next.js, index.html in Vite/Vue, application.html.erb in Rails). The doctype is not a tag — it is a declaration and does not need a closing tag.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Minimize costly DOM read/write operations. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug. In React, repeated requestAnimationFrame-driven state updates across multiple mounted components are a valid performance smell when visible in the source.
Use when auditing slow page loads, heavy assets, or rendering delays related to Remove duplicate JavaScript libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Use when reviewing templates, rendered HTML, or shared components related to Validate forms accessibly. Validate the final browser-facing markup, not just the source framework abstraction. Distinguish between browser-posted forms and client-handled React forms so you do not over-report missing `method` or `action` as accessibility defects.
Use when reviewing stylesheets or components that use JavaScript to toggle classes on parent elements based on child state, form input values, or content presence — :has() may replace the JavaScript entirely.
Use when reviewing long pages, dashboards, or content feeds with expensive offscreen modules. Balance early enough loading for smooth scrolling against keeping the initial route light.
Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use `<a href>` tags, or checking that dynamically generated links have valid href values.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Avoid inline JavaScript. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Lint JavaScript code. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Use when reviewing scripts, client components, bundles, or runtime behavior related to Minify all JavaScript files. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.
Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize JavaScript bundle size. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when auditing slow page loads, heavy assets, or rendering delays related to Avoid JavaScript-based redirects. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when reviewing client-side JavaScript, HTML source, or git history for exposed credentials, API keys, or tokens.
Use when auditing slow page loads, heavy assets, or rendering delays related to Avoid serving legacy JavaScript to modern browsers. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when auditing public documentation portals, API references, help centers, SDK docs, or large knowledge bases. Check the final file served at `/llms.txt` and verify that the linked pages are stable, high-value, and accessible without relying on a JavaScript-only interface.
Пазя съществуващия каталог и добавям намерени SKILL.md файлове след прочит на метаданните. Наличният индекс остава използваем, когато проверката е частична.
Платформата и нивото описват записаното в източника. Те не са гаранция за съвместимост. Български текст се показва само когато в каталога има отделен превод; иначе виждате оригинала с означен език.
Общите звезди показват натрупана популярност. За „Набират интерес“ се сравнява измереният темп при достатъчен интервал. ≥ означава непълна извадка. Под един час не изчислявам дневен темп; методът и изминалият период се показват до записа.
Проверете файла, лиценза и нужния достъп преди употреба. Нито каталогът, нито четенето на SKILL.md изпълняват външни инструкции.
Темата Agent Skills в GitHub