데이터·AI 스킬

This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluates market bubble risk through quantitative data-driven analysis using the revised Minsky/Kindleberger framework v2.1. Prioritizes objective metrics (Put/Call, VIX, margin debt, breadth, IPO data) over subjective impressions. Features strict qualitative adjustment criteria with confirmation bias prevention. Supports practical investment decisions with mandatory data collection and mechanical scoring. Use when user asks about bubble risk, valuation concerns, or profit-taking timing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and record evidence-backed LLM and AI-search citation checks across approved assistant/search surfaces with timestamped queries, locales, modes, cited URLs, snippets, screenshots or transcripts, and caveats. Use this skill when the user asks whether ChatGPT, Perplexity, Claude, Gemini, Copilot, or another assistant cites a target site, but do not claim citation without direct evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build evidence-labeled semantic cores for SEO, LLM-readable architecture, and site information design. Use this skill when the user asks for semantic core, query clusters, search intents, audience segments, entity/topic maps, language or locale priorities, competitor/source evidence, pillar-topic planning, or a structured handoff before URL architecture and internal linking. It must mark unknown search volume, difficulty, and ranking data as unknown instead of inventing metrics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Draft, expand, revise, structure, and maintain a full Islamic University of Technology BSc thesis from source documents using the local iutbscthesis LaTeX template. Use when writing or editing thesis metadata, front matter, abstract, chapters, related works, methodology, results, discussion, conclusion, citations, appendices, figures, tables, code listings, or compile guidance for main.tex. Also use when the user expects an AI agent to turn papers, notes, PDFs, LaTeX sources, bib files, data tables, and assets into a substantial thesis manuscript chapter by chapter without requiring repeated babysitting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tested output format specifications for Claude prompts. Use when the user wants a specific deliverable structure — retrieving, reviewing, customizing, or building output formatting. Trigger on: "give me the Executive Brief format," "show me the output template for," "I need the Decision Matrix structure," "show me available output formats," "build a custom output format for." Provides 10 ready-to-use structures (executive briefs, technical designs, research summaries, implementation plans, decision matrices, competitive analyses, post-mortems, stakeholder updates, strategic memos, process documentation) plus a custom template, with per-section length guidance and format constraints tested against Claude formatting defaults. If unsure which format fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or choosing reasoning/identity approaches (use rootnode-block-selection if available).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Eight tested identity approaches for Claude prompts, each shaping depth, vocabulary, reasoning style, and what Claude treats as obvious vs. requiring explanation. Use when the user wants a specific identity template — retrieving, reviewing, customizing, or building a role definition. Trigger on: "give me the Strategic Advisor identity," "show me the identity template for," "I need a Technical Architect role," "build a custom role for," "show me all available identities." Also use when reviewing a prompt's identity layer or when output lacks domain-appropriate depth. Provides 8 tested approaches across strategy, technical, research, communications, and operations domains plus a template for building custom identities. If the user is unsure which identity fits their task, use rootnode-block-selection first if available. Do NOT use for evaluating complete prompts — use rootnode-prompt-validation if available. Do NOT use for full prompt assembly — use rootnode-prompt-compilation if available.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides selection of identity, reasoning, and output approaches for Claude prompts based on task characteristics. Trigger on: "help me choose an approach," "which approach fits this task," "recommend a prompt pattern," "compare reasoning methods," "map this task to the right approach," "what combination of approaches," "which identity fits," "which reasoning method." Also trigger on symptom-phrased: "my prompt feels generic," "I don't know which approach to use," "my output lacks domain depth." Covers decision-tree logic across 8 identity approaches, 18 reasoning variants, and 10 output formats. After selection, use the relevant catalog skill if available to retrieve full templates. Activate whenever approach-selection across multiple categories is the primary decision. Do NOT use when the user already names a specific approach to retrieve (use the relevant catalog skill directly if available) or for evaluating existing prompts (use rootnode-prompt-validation if available).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Specialized agentic and context engineering prompt methodology for Claude. Use when designing AI agents — system prompts, tool definitions, context window architectures, failure mode planning, multi-agent coordination, agent evaluation. Trigger on: "design an agent," "build a system prompt for an agent," "architect an agent's context," "design tool definitions," "agent system prompt," "context window architecture," "tool interface design," "evaluate agent behavior," "multi-agent coordination," "context engineering for agents," "ACI design." Provides 12 tested approaches for agent architecture (designing agents, not using them). Do NOT use for evaluating or scoring individual non-agent prompts (use rootnode-prompt-validation if available). Do NOT use for general software architecture that hosts agents (use standard technical reasoning for that).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds complete, optimized Claude prompts and Project scaffolds from task descriptions. Use when building, designing, creating, or structuring a Claude prompt or system prompt. Trigger on: "build me a prompt," "compile a prompt for," "create a system prompt," "write a Claude prompt," "design a prompt for," "help me write a prompt," "scaffold a Claude Project," "design a Project for." Uses a four-stage methodology (Parse, Select, Construct, Validate) and a tested 5-layer architecture (Identity, Objective, Context, Reasoning, Output + Quality Control). In Project Mode, the Compiler is global-layer-aware — checks User Preferences, installed Skills, and MCP Connectors to avoid redundancy and flag gaps. Do NOT use for auditing existing prompts (use rootnode-prompt-validation if available) or diagnosing existing Projects (use rootnode-project-audit if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Evaluates and scores Claude prompts and system prompts using a six-dimension Scorecard with anchored 1-5 rubrics. Trigger on: "review my prompt," "score this prompt," "rate my prompt," "evaluate this prompt," "improve my prompt," "what's wrong with my prompt." Also trigger on: "why isn't my prompt working," "my prompt produces bad output," "help me fix this prompt," "is this prompt any good." Scorecard covers Objective Clarity, Context Specificity, Reasoning Fit, Output Precision, Behavioral Calibration, and Architectural Efficiency, plus a five-question Output Evaluation Rubric for assessing actual output. Also use when the user pastes a system prompt and asks for feedback. Activate whenever structured quality assessment of a single prompt is the primary need. Do NOT use for project-level audits involving Custom Instructions architecture, knowledge file organization, or multi-file Project structure (use rootnode-project-audit if available).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze and tune a running llama.cpp server for local coding agents: propose config (ctx, prompt cache, MTP), benchmark before/after, report deltas. Use to optimize llama-server for Claude Code or Aider. Don't use for vLLM, ollama, or non-llama.cpp.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Transform research papers into professional visual schemas. Analyzes paper logic, selects optimal layout patterns, and generates detailed prompts for AI image generation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Image generation skill using Gemini Web. Generates images from text prompts via Google Gemini. Also supports text generation. Use as the image generation backend for other skills like cover-image, xhs-images, article-illustrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Execute queries on the Postgres database. Use this skill DIRECTLY whenever the user asks anything about database contents, counts, or data — do NOT read compose.yml or SQL migration files first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generalised autonomous optimisation loop — soft RLVR for any artifact a user can measure. Web runtime package: uses memory in this order: connector-backed, project-pack, none. Never assumes subprocess access or unrestricted local files. Use this skill whenever a user wants to iteratively improve an artifact — code, prompts, documents, configs, designs, content — by running structured experiments, evaluating results against a multi-dimensional rubric, and learning from each attempt. Triggers include: "optimise this", "keep improving until it's good", "run experiments on", "autoresearch", "iterate on this overnight", "try different approaches and pick the best", or any request implying repeated evaluate-and-improve cycles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Boot and drive the tbh-meter app + reader locally to see a change working — what runs on macOS (UI only; the reader is win32-only) and how to feed the overlay/list fake data. Use when asked to run/start the meter, verify a change in the running app, screenshot the overlay, or reproduce a bug locally.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

当用户想快速判断一项任务是否能被当前AI技术自动化时使用。 用户在问"这个AI能做吗"、"技术上可行吗"、"能不能用AI自动完成X"时激活。 不适用于: 需要深度可行性分析的项目评估、涉及情感共鸣或复杂推理的创意任务、LLM时代的长文本生成场景。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

应用从 AI for Everyone 蒸馏出的「统计化验收标准 — 不追求100%准确」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to statistical-acceptance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

应用从 AI for Everyone 蒸馏出的「统一数据仓库 — AI的数据基础设施」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to unified-data-warehouse.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

应用从 AI for Everyone 蒸馏出的「数据飞轮 — AI产品自我强化的增长引擎」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to data-flywheel.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

应用从 AI for Everyone 蒸馏出的「不为数据而收购 — 数据投资的价值验证原则」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to dont-acquire-for-data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

应用从 AI for Everyone 蒸馏出的「不等完美数据 — 先用起来再迭代」方法论。Use when the user needs practical guidance, diagnosis, workflow design, decision support, or an action plan related to dont-wait-perfect-data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.