Намерете инструкция, прочетете оригиналния файл и подгответе команда за своя инструмент.
31 301 skills в каталога
Как подбирам и измервамДанните имат нужда от нова проверка.Последна успешна проверка: 23.09.2026 г.
Проверката на източника не означава, че всяка инструкция е изпробвана от Level8. Каталогът не обхваща непременно всички публични хранилища.
Търсене в целия индекс. Метаданните показват посоченото от източника; липсващите стойности остават означени.
Датата в GitHub е отделна от първата поява в моя индекс. Филтърът по дата изключва записите без посочено обновяване.
Страница 26: 24 записа в 8 групи по репозиторий. Всички записи от страницата са показани. Номерът пази позицията от избраната подредба.
2 skills от този източник на тази страница
Read the official Letta documentation (docs.letta.com) through its cached, ETag-checked fetch route. Load before ANY docs.letta.com retrieval — answering how Letta works, what Letta (or you) can do, and looking up Letta API, Agent SDK, or Letta Code reference.
Reference for writing a Workflow tool script (script API and gotchas, pipeline-vs-barrier rules, quality patterns, worked examples). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
4 skills от този източник на тази страница
Audit and rewrite a LinkedIn profile end-to-end for 2026: headline, About 7-step, Featured, banner, photo, Experience metrics, Skills, custom URL, recommendations. Triggers on \"review my profile\", \"rewrite my headline\", \"fix my About\", \"optimize banner\", \"profile audit\", \"LinkedIn bio\". Converts resume-style profiles to ones that convert 3-5x better. Not for writing feed content (use linkedin-post-writer).
Audit and rewrite a LinkedIn profile end-to-end for 2026: headline, About 7-step, Featured, banner, photo, Experience metrics, Skills, custom URL, recommendations. Triggers on \"review my profile\", \"rewrite my headline\", \"fix my About\", \"optimize banner\", \"profile audit\", \"LinkedIn bio\". Converts resume-style profiles to ones that convert 3-5x better. Not for writing feed content (use linkedin-post-writer).
Repurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).
Repurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).
2 skills от този източник на тази страница
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
Golang package and module lookup via `godig`, a pkg.go.dev API client (CLI + MCP server). Use for any Go/Golang library's documentation, API signatures, symbols, usage examples, which versions exist, licenses, whether a dependency has CVEs, or who imports a package — prefer this over Context7 for any Go package or module. Read-only, no auth. Not for upgrading dependencies (→ See `samber/cc-skills-golang@golang-dependency-management` skill), choosing a library (→ See `samber/cc-skills-golang@gola
1 skill от този източник на тази страница
Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.
11 skills от този източник на тази страница
Use before writing any paper - clarifies paper type, discipline, topic, methodology, and chapter structure through natural dialogue
Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims
Use when writing literature review sections - guides searching, organizing, and synthesizing academic sources
Use when a research-writing task spans multiple sections, medium-sized revisions, full-paper drafting, or repeated quality failures
Use when writing academic papers, theses, or research articles - supports brainstorming, chapter writing, literature review, and LaTeX output
Use when starting any research writing task - establishes workflow and routes to appropriate skills
Use when writing paper chapters - requires completed brainstorming, writes one chapter at a time with user confirmation
Use when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
Use when writing humanities or social science papers - provides discipline-specific writing guidance
Use when writing law papers - provides legal writing conventions, citation formats, and argumentation guidance
Use when writing medical, biological, or clinical research papers - provides IMRaD structure and reporting guidelines
1 skill от този източник на тази страница
Write the canonical engineering record of a fixed bug — root cause, mechanism, fix, validation, and how it slipped through. Engineer-audience, code identifiers welcome. Use after a debug session lands a fix, before closing the ticket. Trigger on /post-mortem, when the user says "write the post-mortem / postmortem / RCA / root cause analysis", "document this fix", "write up the root cause", "close out this bug with a writeup", or hands you a fixed-and-validated bug and asks for the writeup.
1 skill от този източник на тази страница
Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.
2 skills от този източник на тази страница
Turn a reported defect into an actionable bug report or issue draft. Use when the user asks to capture or document a bug; a request to fix broken behavior should proceed to diagnosis and repair.
Draft user-facing release notes from a verified release range. Use for release-note or changelog requests and /release-notes; writing notes alone does not imply publishing a release.
Пазя съществуващия каталог и добавям намерени SKILL.md файлове след прочит на метаданните. Наличният индекс остава използваем, когато проверката е частична.
Платформата и нивото описват записаното в източника. Те не са гаранция за съвместимост. Български текст се показва само когато в каталога има отделен превод; иначе виждате оригинала с означен език.
Общите звезди показват натрупана популярност. За „Набират интерес“ се сравнява измереният темп при достатъчен интервал. ≥ означава непълна извадка. Под един час не изчислявам дневен темп; методът и изминалият период се показват до записа.
Проверете файла, лиценза и нужния достъп преди употреба. Нито каталогът, нито четенето на SKILL.md изпълняват външни инструкции.
Темата Agent Skills в GitHub