Loading...
Loading...
Found 19 Skills
Determine the best Anthropic architecture for your project by analyzing requirements and recommending the optimal combination of Skills, Agents, Prompts, and SDK primitives.
Trae-optimized PUA high-agency governance skill for npx skills installation. Only activate it in scenarios such as explicit PUA requests, repeated task failures, user frustration, giving-up/passive behavior, or unverified task completion. Do not trigger it for normal first-attempt tasks.
This skill should be activated when the user requests to "deepen a topic", "analyze a topic", "help me write an outline", "will this topic go viral", "help me diagnose a topic", "is this topic worth pursuing", or "how to improve this topic". Even if the user only shares a topic and asks for opinions, you should proactively initiate the diagnosis process instead of providing a simple response. Driven by the cognitive hijacking theory, it features four modules: Perspective Collision (challenging the topic's premise), Topic Diagnosis (graded using 🛵🚗✈️), Outline Design (emotional peak planning), and Style Validation (alignment with li-writer style). It generates a comprehensive deepening report and saves it as a file. Do NOT trigger this skill for: merely recording topics (use li-recorder), directly writing scripts (use li-writer). Use when the user wants to "develop a topic", "analyze topic potential", "write an outline", "will this topic go viral", or needs full topic diagnosis + outline design. Trigger even if the user just shares a topic and asks for opinions.
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.
The soul of MOOLLM — self-explanation, help, navigation, philosophy
Audit recent work in a folder and produce a forward-looking self-improvement report. Reviews files modified in the past week, git activity, file-type distribution, and recurring task patterns; writes a 5-section weekly-setup-improvements.md with concrete updates for context files, ideas for new skills, workflow gaps to close, files to clean up, and what's working well enough to leave alone. Cross-platform; safe to schedule weekly via /schedule. Use when: 'weekly review', 'weekly self audit', 'improve my setup', 'what should I clean up', 'suggest new skills', 'self improvement loop', 'weekly setup improvements', or before a planning week.
Brainstorms ideas and researches projects.