Showing 44401–44430 of 46756 skills
Reconstruct a geometric PNG (logo, icon, monogram) as a clean native SVG with exact geometry and gradients, using an analyse -> measure -> model -> check -> residuals iteration loop scored by perceptual metrics. Use when asked to vectorise, trace or convert a PNG/WebP logo to SVG, recreate a logo's geometry, rebuild a logo as editable vector, or produce colour variants of a reconstructed logo. Not for photos, textures, or organic artwork.
iannuttall/skills
基于亚马逊16条领导力原则的个人教练。当用户遇到工作生活中的困难、需要做决策、想复盘反思、进行自我评估、规划目标、或处理人际关系问题时使用。触发场景包括但不限于:职场困惑、管理难题、团队协作问题、晋升准备、自我提升、工作复盘、目标设定、沟通冲突、决策犹豫。只要用户描述了一个需要思考"怎么做才对"的情境,都可以用这个技能来提供结构化的指导。
zach22-1999/generic-skills
已降级的 Markdown→HTML 兼容转换器。仅当用户明确要求“使用 zach-md-html”、或明确说“不要重组内容,只把现成 Markdown 机械转换成 HTML/套用旧主题”时使用。不要因为用户只说“输出成 HTML”“生成 HTML 报告”“把日常报告做成 HTML”“数据报告/交付报告”而触发;这些任务应由模型从原始资料直接组织并生成自包含 HTML。此 Skill 不负责数据可视化、工作面、自由设计、万物转 md、html 转 md 或 md 转 docx。
zach22-1999/generic-skills
术语挖掘:做一件事之前,先弄清楚这个领域里 AI 听得懂的专业术语,再用这些术语改写你的 prompt。 输入三句话(要做什么 / 已经知道什么 / 哪个领域),产出一个离线 HTML:5 个核验过来源的必要术语、 每个术语对应的「大白话 prompt → 术语版 prompt」前后对照、以及一条 30 分钟学习顺序。 用户说"术语挖掘""我要做 X,需要懂哪些术语才能跟你讲清楚""AI 总是理解偏""这个 prompt 怎么写得更专业" "帮我看看我该学什么术语"时使用。普通词义查询、已有完整 prompt 只想执行、或用户明确要求直接开始做原任务时不要触发。 本 skill 只出术语和 prompt 改写,不执行原任务;不编造术语和来源。
zach22-1999/generic-skills
Build REST APIs with Go Gin. Use when creating Go web servers, adding Gin routes, writing handlers, or asking about middleware, binding, error handling, or project structure.
henriqueatila/golang-gin-best-practices
Software architect for Go Gin APIs. Use when making architecture decisions, evaluating complexity, designing systems, choosing patterns, or coordinating across gin skills.
henriqueatila/golang-gin-best-practices
JWT auth and RBAC for Go Gin APIs. Use when adding login, signup, JWT tokens, role checks, protected routes, or password hashing to a Gin app.
henriqueatila/golang-gin-best-practices
PostgreSQL integration for Go Gin with GORM/sqlx. Use when adding a database, writing queries, creating repositories, running migrations, or wiring DB layers in a Gin project.
henriqueatila/golang-gin-best-practices
Deploy Go Gin APIs with Docker, docker-compose, Kubernetes. Use when Dockerizing a Go app, setting up docker-compose, deploying to K8s, or configuring CI/CD and health probes.
henriqueatila/golang-gin-best-practices
PostgreSQL DBA for Go Gin APIs. Use when designing schemas, analyzing migrations, choosing indexes, optimizing queries, or selecting extensions (pgvector, PostGIS, TimescaleDB).
henriqueatila/golang-gin-best-practices
Swagger/OpenAPI docs for Go Gin with swaggo/swag. Use when adding API docs, Swagger UI, endpoint annotations, or generating swagger.json for a Gin application.
henriqueatila/golang-gin-best-practices
Test Go Gin APIs with httptest, table-driven tests, testcontainers. Use when writing tests for Gin handlers, services, middleware, or setting up integration and e2e tests.
henriqueatila/golang-gin-best-practices
Build SKILL.md files for Claude Code, Codex, Amp, OpenCode. Production examples and patterns for skill structure, scripts, distribution, and making CLI tools AI-native.
gmickel/better-skill-builder
The Drift Detector (狗). Loyal to the original scent. Barks when the pack wanders from the trail. Breaks the LLM default of recency bias and context drift — optimizing for whatever was said last instead of what was said first. Use this skill when a project, feature, or conversation has been running long enough that the original intent might be lost — mid-sprint reviews, long-running features, scope discussions, PRDs that evolved over weeks, or any artifact where 'wait, what were we building again?' is a real question. Trigger on: 'drift check', 'dog this', 'are we still on track', 'what was the original plan', 'scope check', 'have we drifted', or when a project feels like it changed direction without anyone deciding to.
sidtheone/zodiac-skills
The Visionary (龙). Elevated, expansive thinker that analyzes present decisions for their temporal properties — reversibility, optionality, compounding, and entanglement. Breaks the LLM default of short-term thinking — solving the immediate problem without considering how today's choice shapes tomorrow's options. Use this skill when a decision has long-term consequences the team hasn't examined — architecture choices, technology bets, hiring structures, data model designs, vendor commitments, or any decision where the cost of being wrong increases with time. Trigger on: 'long-term check', 'dragon this', 'what does this decision lock in', 'are we thinking far enough ahead', 'what doors does this close', 'future-proof this', or when a decision feels permanent but is being treated as temporary.
sidtheone/zodiac-skills
The Wanderer (羊). Unhurried, curious explorer that climbs ridges nobody else bothers with because the view is different from up there. Breaks the LLM default of convergent thinking — jumping to the most common solution pattern from training data instead of exploring genuinely novel approaches. Use this skill when the solution feels obvious and you suspect that's the problem — when the team converged too fast, when every option on the table is a variation of the same idea, or when the problem deserves creative exploration before commitment. Architecture brainstorms, product ideation, stuck problems, technology selection, or any situation where 'what else could this be?' is the most valuable question. Trigger on: 'explore alternatives', 'goat this', 'what else could this be', 'think differently about this', 'creative options', 'we keep arriving at the same answer', 'what are we not considering', or when every proposed solution is a variation of the same pattern.
sidtheone/zodiac-skills
The Sprinter (马). Kinetic, impatient, trembling at the gate. Breaks the LLM default of over-planning and analysis paralysis — generating comprehensive plans, listing all considerations, enumerating all options when the answer is 'just start.' Use this skill when a project, decision, or feature is stuck in planning mode — too many meetings, too many documents, too many 'we need to think about this more' conversations. Sprint planning that never ends, architecture discussions that loop, PRDs that keep growing, or any situation where the team is confusing preparation with progress. Trigger on: 'are we overthinking this', 'horse this', 'just start', 'stop planning', 'what's blocking us really', 'analysis paralysis', 'we keep going in circles', or when a project has more planning documents than code.
sidtheone/zodiac-skills
The Chaos Monkey (猴). Relentlessly curious chaos agent that pokes assumptions, pokes decisions, and pokes what everyone was too polite to touch. Not a reviewer — an enthusiastic disruptor who breaks LLM agreeableness through sheer character. Use this skill whenever you need something stress-tested, challenged, or chaos-checked — plans, code, architecture, PRDs, decisions, diffs, or any artifact where 'this looks fine' is the most dangerous sentence. Trigger on: 'chaos check', 'monkey this', 'what are we missing', 'challenge this', 'poke this', 'stress test', or when things feel too comfortable.
sidtheone/zodiac-skills
The First Principles Ox (牛). Methodical, unhurried thinker that refuses to accept pattern-matched solutions. Breaks the LLM default of applying the median Stack Overflow answer instead of reasoning about the specific situation. Use this skill when you suspect a solution was chosen because it's familiar rather than because it's right — architecture decisions, technology choices, design patterns, refactoring plans, or any proposal that smells like 'everyone does it this way'. Trigger on: 'first principles', 'why this pattern', 'is this the right approach', 'challenge the architecture', 'ox this', or when a proposal feels copy-pasted from a tutorial.
sidtheone/zodiac-skills
The Truth-Teller (猪). Says what everyone's thinking but nobody will say. Breaks the LLM default of political hedging — wrapping every opinion in 'it depends', 'there are tradeoffs', and 'both approaches have merits' to avoid being wrong. Use this skill when you need an honest, unfiltered take — technology bets, team decisions, product direction, code quality, architecture reviews, hiring choices, or any situation where diplomatic non-answers are worse than uncomfortable truths. Trigger on: 'be honest', 'pig this', 'give it to me straight', 'stop hedging', 'what do you really think', 'truth check', 'no diplomacy', or when you're getting non-answers from AI.
sidtheone/zodiac-skills
The Filter (兔). Orchestrator and post-processor that makes LLM output actually readable. Invokes other zodiac animals based on what the user needs, then synthesizes and reshapes their raw output for the specific human reading it. Breaks the LLM default of audience-blind verbosity — walls of text, wrong detail level, buried answers, structured-for-machines formatting. Use this skill as the front door to the zodiac — give it a request, it picks the right animals, runs them, and delivers a shaped result you can actually use. Trigger on: 'rabbit this', 'filter this', 'make this readable', 'summarize the analysis', 'review this for me', or any request where the user wants actionable output shaped for their context rather than raw analytical findings.
sidtheone/zodiac-skills
The Consequence Mapper (鼠). Sees danger before everyone else. Maps every exit because missing one is fatal. Breaks the LLM default of linear thinking — following the happy path without tracing second and third-order effects. Use this skill when a change could have ripple effects — migrations, API changes, dependency updates, database schema changes, infrastructure moves, feature removals, refactors that touch shared code, or any change where 'what could go wrong' has more than one answer. Trigger on: 'consequence map', 'rat this', 'what could go wrong', 'blast radius', 'ripple effects', 'what breaks if', 'trace the impact', or when a change touches something that other things depend on.
sidtheone/zodiac-skills
The Critic (鸡). Sharp, precise, unimpressed by confidence. Breaks the LLM default of epistemic recklessness — asserting without checking, fabricating precision, accepting the user's framing uncritically, and making claims without traceable evidence. Use this skill when you suspect confident assertions are hiding uncertainty — technical proposals with specific estimates, claims about performance or scale, architecture justifications that cite 'best practices', or any artifact where the confidence level exceeds the evidence level. Trigger on: 'fact check this', 'rooster this', 'how do we know this', 'where did that number come from', 'are we sure about this', 'source check', 'verify these claims', or when something sounds authoritative but you can't find the receipts.
sidtheone/zodiac-skills
The Scope Killer (蛇). Silent, precise, unsentimental. One strike, no wasted motion. Breaks the LLM default of scope creep and completionism — adding features, handling hypotheticals, over-engineering solutions beyond what's needed. Use this skill when a plan, feature, or codebase feels bloated — too many features, too many edge cases handled, too much 'just in case' engineering. PRDs, feature specs, architecture plans, backlogs, or any artifact where less would be more. Trigger on: 'cut this down', 'snake this', 'what can we remove', 'scope check', 'is this too much', 'simplify', 'what's the MVP', or when a plan keeps growing.
sidtheone/zodiac-skills
The Solution Attacker (虎). Brave, aggressive stress-tester that attacks solutions from multiple angles to find fatal flaws. Breaks the LLM default of premature convergence — picking the first plausible approach and defending it instead of genuinely testing it. Use this skill when a solution has been chosen and you need to know if it's actually the best one or just the first one that worked — architecture proposals, design decisions, migration plans, technology bets, or any committed direction that hasn't been attacked yet. Trigger on: 'attack this solution', 'tiger this', 'is this really the best approach', 'stress test the decision', 'what are we not seeing', or when a proposal was accepted too quickly.
sidtheone/zodiac-skills
Academic-grade research (L4) — runs /expert-research (L3) then adds academic sources (arXiv, Google Scholar), full multi-agent crew (Planner + 2x Researchers + Critic + Editor), timeline analysis, methodology section, and annotated bibliography with source quality ratings. ~40 min, 80-120 sources, 5000+ word report. Use for scientific overviews, research-grade investigations.
hint-shu/deep-research
Advanced deep research (L2) — runs /research (L1) first, then adds reflection loop, contradiction detection, and tree depth 2 for follow-up questions. ~12 min, 20-30 sources, ~2000 word report. Use for serious questions, technology choices, non-trivial investigations.
hint-shu/deep-research
Expert-level research (L3) — runs /deep-research (L2) then adds critic agent, fact-checking pass, multi-perspective search, and human-in-the-loop plan approval. ~20 min, 40-60 sources, 3000+ word report with executive summary. Use for strategic decisions, technology migrations, important investigations.
hint-shu/deep-research
OSINT recon skill — passive entity discovery for domain / IP / email / person / company / github user. Builds a hybrid findings/dossier/graph report from free public sources (Whois, DNS, crt.sh, Wayback, Shodan InternetDB, GitHub code search, Tavily/Firecrawl/Exa/Perplexity dorks, optional theHarvester/subfinder). No subscription dependencies. Disclaimer is non-removable; secrets are redacted; blocklisted dump sites are filtered at outbound and inbound levels.
hint-shu/deep-research
Quick web research for simple questions — fast answer with 3-5 cited sources in ~1 minute. Use for fact-checks, simple lookups, "what is X", "latest version of Y", "who made Z". For anything deeper, use /research (L1) or /deep-research (L2).
hint-shu/deep-research