Explorar skills

Define the reader/customer avatar, painful current state, desired outcome, transformation bridge, objections, and proof needed before writing profile copy, posts, articles, landing pages, or visual concepts.

Rewrite titles, headlines, repository descriptions, homepage hero lines, LinkedIn headlines, article titles, and section openers so they lead with credible authority before explaining the content.

Use when drafting, saving, formatting, validating, or repairing LinkedIn profile and content assets in this repository, including headlines, About sections, Experience descriptions, project copy, posts, articles, and LinkedIn image specs.

Generate properly formatted Markdown from unstructured notes, scratch text, transcripts, or rough drafts. Use when the user wants content rewritten into cleaner Markdown without inventing new information.

Core principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.

Audit and remove stale, renamed, or duplicate skills across all installed agent platforms (Claude Code, Kiro, Codex, Windsurf, Gemini, Pi, and more). Handles symlink and copy installs, detects artifacts, and generates OS-correct removal commands. Use when skills list feels cluttered, after renaming a skill, after uninstalling a plugin, or when user says "clean up skills", "remove old skill", "prun

Parse and execute commands given in Cantonese. Use when user gives instructions or requests actions in Cantonese. Translates Cantonese commands to executable actions.

Translate between Cantonese and other languages (Mandarin, English, etc.). Use when user explicitly requests translation or when translation is needed for communication.

Parse and understand Cantonese user input. ALWAYS use this skill first when user writes in Cantonese or uses Cantonese vocabulary. This skill translates Cantonese to standard Chinese/English for LLM comprehension.

Trigger on "consult lint", "consistency pass", "diagram vs narrative", "broken promises across docs", "cross-artifact check", "scope drift lint". Read-only diff across frame, arc, gates, acceptance, commercial, architecture artifact. NOT rewriting copy (use consult-package), NOT drawing diagrams (use arch-diagrams).

Ingest the live documentation manual into the ontology as ground-truth Doc nodes, then enrich them with doc→ontology DESCRIBES links. Runs the mechanical doc extractor (docs-ingest → doc-nodes.jsonl, split by heading/anchor, prose referenced from ../documentation), rebuilds the graph (embeds the doc prose), spawns the doc-analyser subagent per un-enriched page (live-URL verification + DESCRIBES to

Deep-dive research and analysis of external reference materials (YouTube videos, articles, GitHub repos, documentation, code sources) against the current project. ONLY trigger this skill when the user explicitly uses one of these phrases: "research this against the project", "analyze this reference", or "compare to this project" (or close variations of those phrases). Do NOT trigger just because t