fluxly Search skills… ⌘K 中文 Publish

llm-wiki-setup

AI Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
AI
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@daymade · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Permissions
  • Read-only
  • Shell exec
  • Write / modify
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview llm-wiki-setup.preview 
---
name: llm-wiki-setup
description: 帮用户搭一个金融投研专用 LLM Wiki（Karpathy 模式）：纯 markdown 文件 + [[wikilink]] 互联 + LLM 维护，知识随用复利。 两个投资者看同一家公司…
category: ai
runtime: Python
---

# llm-wiki-setup output preview

## PART A: Task fit
- Use case: 帮用户搭一个金融投研专用 LLM Wiki（Karpathy 模式）：纯 markdown 文件 + [[wikilink]] 互联 + LLM 维护，知识随用复利。 两个投资者看同一家公司，关注点可能完全不同——一个看「下季度订单能否超市场预期」，另一个看「管理层电话会上的语气和信心」。给他们同一份模板，就抹掉了让 wiki 有用的那个东西。 runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “★ 先读这一条（这个 skill 的灵魂） / 不碰的红线（Karpathy 原意，别 over-engineer） / 机制层 vs 规则层（贯穿全程的区分）” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “帮用户搭一个金融投研专用 LLM Wiki（Karpathy 模式）：纯 markdown 文件 + [[wikilink]] 互联 + LLM 维护，知识随用复利。 两个投资者看同一家公司，关注点可能完全不同——一个看「下季度订单能否超市场预期」，另一个看「管理层电话会上的语气和信心」。给他们同一份模板，就抹掉了让 wiki 有用的那个东西。 runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “★ 先读这一条（这个 skill 的灵魂） / 不碰的红线（Karpathy 原意，别 over-engineer） / 机制层 vs 规则层（贯穿全程的区分）” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 帮用户搭一个金融投研专用 LLM Wiki（Karpathy 模式）：纯 markdown 文件 + [[wikilink]] 互联 + LLM 维护，知识随用复利。 两个投资者看同一家公司，关注点可能完全不同——一个看「下季度订单能否超市场预期」，另一个…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “★ 先读这一条（这个 skill 的灵魂）”, “不碰的红线（Karpathy 原意，别 over-engineer）”, “机制层 vs 规则层（贯穿全程的区分）”, “工作流”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name llm-wiki-setup directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “★ 先读这一条（这个 skill 的灵魂） / 不碰的红线（Karpathy 原意，别 over-engineer） / 机制层 vs 规则层（贯穿全程的区分）” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / shell-exec / write; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.