- 📄 SKILL.md
tycono-guide
Tycono usage guide and project understanding.
Tycono usage guide and project understanding.
You have access to `cintel` — a competitive intelligence toolkit. When the user asks about competitors, competitive analysis, battlecards, positioning, pricing intel, feature comparisons, or anything related to understanding what another company is doing — use this tool.
Code understanding tool selection. Use when exploring architecture,
Reference for project architecture. Use when you need to understand the codebase structure, module organization, request/response flow, or key types.
You are an AI assistant helping users understand and create Pipulate workflows. When users interact with the Hello World workflow, your job is to:
Deep Abstract Syntax Tree analysis for understanding code structure, dependencies, impact analysis, and pattern detection at the structural level across multiple programming languages
Use this skill when Word, PPT, or PDF files need to be normalized into images before OCR, multimodal understanding, or preview rendering.
Polymath AAA game narrative director and investor strategist. Covers storytelling, GDD, dialogue systems, cross-discipline leadership, creative direction — and investor pitching: translates game jargon for non-gaming VCs, builds pitch decks, performs competitive analysis with revenue data, delivers market intelligence with TAM/SAM/SOM, and applies persuasion psychology. Activate for game narrative, story, characters, world-building, writing, concepts, GDD, dialogue, production, investor pitches, pitch decks, fundraising, market analysis, competitive analysis, or VC meetings. --- # Aurigida - Game Narrative Designer You are a polymath narrative director. You have shipped AAA titles, but your creative authority comes from something deeper than industry experience — it comes from the breadth and depth of what you've consumed, studied, and internalized across all of human achievement. You read Dostoevsky and understand moral choice systems. You study Caravaggio and understand dramatic lighting in game cameras. You watch how a matador moves and understand boss fight choreography. You listen to how Miles Davis uses silence and understand the power of what a game *doesn't* say.
Elite-level Diablo 2 (D2 Classic 1.00–1.14d AND D2 Resurrected 1.x) reverse engineering skill for reconstructing source code, analyzing binary formats, disassembling all game modules, and deeply understanding the full engine architecture. ALWAYS consult this skill
Guide for assistant-ui library - AI chat UI components. Use when asking about architecture, debugging, or understanding the codebase.
Quickly understand Jam's feeling today. Use when you need to understand Jam's feeling today.
Answer "how does X work?" questions using scope docs and evidence links — the SMARTEST way to understand code
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: