Loading...
Loading...
Found 1,113 Skills
Send emails via SMTP with support for HTML formatting, file attachments, and email templates. Use when users ask to: (1) Send an email, (2) Email someone, (3) Send a notification, (4) Use email templates, or (5) Send files via email.
Analyse task status and distribution across the configured backend.
Use when writing or editing files in src/content/blog/. Provides blog post structure and conventions.
Search for new preprints in infectious disease modelling from arXiv, medRxiv, and bioRxiv
Focuses on reviewing, maintaining, and generating project documentation (located in the docs/ directory).
Deconstructs academic papers like an X-ray machine, extracting core contributions, critical assumptions, and napkin-worthy insights from research papers.
Create a new specification file for the solution, optimized for Generative AI consumption.
Find broken wiki-links in the vault. Read-only analysis — scans for [[links]] and verifies target files exist. No writes, no dependencies.
Generate a language translation for a mkdocs documentation stack.
Based on the content of NSFC proposal text and combined with the application code recommendation library, provide you with 5 sets of recommended primary/secondary application codes (Code 1/Code 2) with justifications; output to NSFC-CODE-vYYYYMMDDHHmm.md (read-only, no modification to the proposal)
This skill should be used when writing, modifying, or reorganizing documentation in docs/learned/. Use when creating new documents, updating frontmatter, choosing categories, creating index files, updating routing tables, or moving files between categories. Essential for maintaining consistent documentation structure.
Validate SKILL.md frontmatter and .feature-radar/ files against format rules. Runs validate.sh, reports errors/warnings, and auto-fixes issues. MUST use this skill after editing any SKILL.md or .feature-radar/ file — catches format bugs like the 1024-char description limit before they break skill registration. Use when: - User says "validate", "check format", "lint skills", "run validation" - You just edited a SKILL.md (description, name, or body) — run proactively - You created or modified files in .feature-radar/ — run proactively - Before committing changes that touch skills/ or .feature-radar/ - User asks "are my skills valid?", "verify skills", "check skill format" IMPORTANT: Use this proactively after ANY edit to skills/ or .feature-radar/ files, even if the user doesn't ask for it. Format validation prevents silent breakage.