Loading...
Loading...
Found 305 Skills
Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
Generates a complete social media crisis response playbook covering severity classification, per-level response protocols, holding statement templates, platform-specific actions, and a post-crisis review process. Also outputs a one-page Crisis Quick Card for the client to print. Invoke this skill when onboarding any new client (proactive setup), when a client reports a crisis already in progress, or when reviewing crisis preparedness for an existing account.
Generates a tailored internal operations manual for a Uganda/East Africa social media consultancy or solo practitioner. Covers client onboarding, retainer structures (in UGX), project management, invoicing, quality control, and reporting rhythms. Invoke this skill when setting up a new consultancy, systematising an existing operation, onboarding a first employee, or when a consultant identifies pain points in client management, cash flow, or team coordination.
Help users improve retention and engagement metrics. Use when someone is dealing with churn, optimizing activation flows, building habit-forming products, or trying to increase user engagement and lifetime value.
Activated when users start a new novel project - Guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations
AI Native Camp Day 1 온보딩. Claude와 대화하면서 Claude Code를 익힌다. "1일차", "Day 1", "온보딩" 요청에 사용.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Help users design effective team rituals. Use when someone is building team culture, creating recurring team practices, trying to improve team communication, or establishing operational rhythms for their organization.
Learn how Nexus skills work. Load when user mentions: learn skills, how do skills work, what is a skill, skill tutorial, skill structure, understand skills, explain skills, when to create skill, skill vs project. 10-12 min.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Developer Experience specialist for tooling, setup, and workflow optimization. Use when setting up projects, reducing friction, improving development workflows, or automating repetitive tasks. Focuses on making development joyful and productive.
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a wiki, second brain, personal knowledge base, initialize a vault, or says "onboard", "set up", "new wiki", or "new vault".