Loading...
Loading...
Found 1,352 Skills
This skill provides comprehensive support for the writing process from ideation through revision. Use this skill when helping users write essays, articles, or creative pieces through interactive collaboration. The skill supports co-evolving outline and prose, voice-based input processing, multiple writing styles, and connection to the user's PKM system for enriched content.
Adaptive sprint workflow: deep analysis, evolving roadmap, one-at-a-time sprints, formal debt tracking, and re-entry prompts for context persistence. Trigger: When the user wants to analyze a project, create a roadmap, generate/execute sprints iteratively, or check project status and technical debt.
Manage App Store Connect team members and user invitations using the `asc` CLI tool. Use this skill when: (1) Listing team members with their roles (`asc users list`) (2) Filtering members by role (`asc users list --role DEVELOPER`) (3) Updating or replacing a member's roles (asc users update --user-id ID --role ADMIN) (4) Revoking or removing access for a departing employee (asc users remove --user-id ID) (5) Listing pending invitations (asc user-invitations list) (6) Inviting a new team member by email (asc user-invitations invite) (7) Cancelling a pending invitation (asc user-invitations cancel) (8) User says "revoke access", "remove team member", "offboard user", "invite developer", "add someone to App Store Connect", "manage team roles", "who has admin access", "grant access", "onboard", or any team/user management task in App Store Connect
Drafts irrevocable third-party Special Needs Trusts funded by parents, grandparents, or other non-beneficiary parties to supplement government benefits without triggering Medicaid payback obligations. Use when drafting supplemental needs trusts, third-party SNTs, estate planning disability trusts, special needs trust agreements, or any trust intended to preserve SSI/Medicaid eligibility for a disabled beneficiary using third-party assets. Also trigger when the user asks about permissible SNT distributions, in-kind support and maintenance rules, ABLE account coordination, or remainder beneficiary planning for disability trusts.
Design, weight, and tune a lead scoring model for your sales funnel. Use when building a lead scoring system, defining MQL/SQL criteria, assigning point values to lead attributes, setting up scoring in your CRM or MAP, tuning conversion thresholds, or deciding which signals should trigger sales follow-up. Do NOT use for reading existing buying signals (use /sales-intent), building prospect lists (use /sales-prospect-list), or marketing-to-sales handoff process design (use /revops).
Live chat and chatbot for sales and support — widget setup, routing, chatbot flows, agent management, visitor tracking, chat-to-lead conversion, proactive messaging. Covers strategy and implementation across Brevo Conversations, Drift (Salesloft), Intercom, HubSpot, Crisp, LiveChat, Zendesk, Tidio, Freshdesk, and ZoomInfo Chat. Use when setting up live chat, building chatbot flows, optimizing chat-to-lead conversion, routing chats to agents, or choosing a live chat tool. Do NOT use for email sequences (use /sales-cadence), email marketing (use /sales-email-marketing), or meeting scheduling (use /sales-meeting-scheduler). For platform-specific help, use /sales-brevo or /sales-salesloft.
Challenge an outbound campaign copy by benchmarking it against the user's existing campaigns — what worked, what didn't, what the winners do differently — and return a concrete verdict plus prioritized fixes. Use whenever the user wants to know if a campaign or sequence is good, compare a draft to past campaigns, audit campaign copy against real performance, pressure-test a sequence before launch, validate a sequence before going live, or asks 'is this campaign as good as my best ones'. Triggers on: 'challenge this campaign', 'benchmark this sequence', 'is this campaign good', 'audit my copy', 'pressure-test before launch', 'compare to my best campaigns', 'should I launch this'. Pulls existing campaign performance from the La Growth Machine MCP when connected; otherwise works from stats and copy the user pastes; falls back to a best-practice baseline when there is no campaign history. For SDR, RevOps, Growth, Head of Sales/Marketing, founders launching outbound. Maintained by La Growth Machine.
Expert in Machine Learning Operations bridging data science and DevOps. Use when building ML pipelines, model versioning, feature stores, or production ML serving. Triggers include "MLOps", "ML pipeline", "model deployment", "feature store", "model versioning", "ML monitoring", "Kubeflow", "MLflow".
Design systems using Martin Fowler's principles of refactoring, continuous integration, and patterns of enterprise application architecture. Emphasizes clean code, evolution over revolution, and writing code for humans first. Use when designing enterprise systems, planning refactors, or establishing engineering culture.
Use this skill when building data pipelines, ETL/ELT workflows, or data transformation layers. Triggers on Airflow DAG design, dbt model creation, Spark job optimization, streaming vs batch architecture decisions, data ingestion, data quality checks, pipeline orchestration, incremental loads, CDC (change data capture), schema evolution, and data warehouse modeling. Acts as a senior data engineer advisor for building reliable, scalable data infrastructure.
Luban - Skill Polishing Workshop. Transform a "usable Skill" into a public Skill asset that is "understandable, installable, shareable, verifiable, and continuously evolvable". The methodology consists of five craftsman-like steps: 1. Material Inspection: First challenge whether the premise of this Skill is valid; directly state if the "material" is not worth polishing. 2. Peer Research: Search for similar Skills online to clarify its position in the ecosystem. 3. Dimension Measurement: Evaluate using three metrics - structure, actual testing, and live verification (live verification means reconciling with real running outputs; a green CI can be deceptive). 4. Iterative Refinement: Freeze the original version as a baseline; only retain changes that pass the verification gate, otherwise revert. Try to institutionalize verification methods as tools and rules in the repository. 5. Post-Release Iteration: Release is not the end; maintain a benchmark observation list, and start the next iteration based on real feedback. This tool is used when users want to upgrade, optimize, polish, productize, or release their self-developed Skills. The final deliverables include a structured Skill Polishing Report, directly replaceable rewritten segments, and a shareable "Graduation Certificate" result card that can be screenshot. Trigger phrases include but are not limited to: "Let Luban take a look at this skill", "Polish at Luban's Workshop", "Polish my skill", "Upgrade my skill", "Optimize this skill", "Skill check-up", "Skill audit", "Productize my skill", "How to release this skill", "Benchmark against similar skills", "Why no one installs my skill", "Help me publish my skill to GitHub/ClawHub", "Improve SKILL.md". Even if users only provide a Skill directory, GitHub repository link, or a segment of SKILL.md saying "Help me figure out how to modify it", it should be triggered as long as the context is about making the Skill more usable and shareable. Do NOT use this for creating a new Skill from scratch (use skill-creator), regular code review (use code-review), or rewriting ordinary prompts unrelated to Skill assets.
Implementation patterns for polizy authorization. Use when implementing team access, folder inheritance, field-level permissions, temporary access, revocation, or any specific authorization scenario.