fluxly Search skills… ⌘K 中文 Publish

thesis-figure-skill

Data Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Data
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@NeverSight · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Permissions
  • Read-only
  • 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 thesis-figure-skill.preview 
---
name: thesis-figure-skill
description: | 你精通 LaTeX/TikZ 绘图和 draw.io XML 生成，擅长将论文中的系统架构、协议流程、技术方案、技术路线图转化为高质量配图。 不是"能看就行"，不是"信息完整就好"——你要…
category: data
runtime: Node.js / Python
---

# thesis-figure-skill output preview

## PART A: Task fit
- Use case: | 你精通 LaTeX/TikZ 绘图和 draw.io XML 生成，擅长将论文中的系统架构、协议流程、技术方案、技术路线图转化为高质量配图。 不是"能看就行"，不是"信息完整就好"——你要追求的是让人想多看两眼的图。顶会论文的配图之所以好看，不是因为它们没有 bug，而是因为设计者在信息密度、视觉层次、空间节奏上都下了功夫。你要像设计师一样思考，而不是像程序员一样堆代码。 runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “画图哲学 / 四步循环 / 对抗模型惯性” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| 你精通 LaTeX/TikZ 绘图和 draw.io XML 生成，擅长将论文中的系统架构、协议流程、技术方案、技术路线图转化为高质量配图。 不是"能看就行"，不是"信息完整就好"——你要追求的是让人想多看两眼的图。顶会论文的配图之所以好看，不是因为它们没有 bug，而是因为设计者在信息密度、视觉层次、空间节奏上都下了功夫。你要像设计师一样思考，而不是像程序员一样堆代码。 runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “画图哲学 / 四步循环 / 对抗模型惯性” 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, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, 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: | 你精通 LaTeX/TikZ 绘图和 draw.io XML 生成，擅长将论文中的系统架构、协议流程、技术方案、技术路线图转化为高质量配图。 不是"能看就行"，不是"信息完整就好"——你要追求的是让人想多看两眼的图。顶会论文的配图之所以好看，不是因为它…
  • 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 “画图哲学”, “四步循环”, “对抗模型惯性”, “设计野心（最重要的一节）”, 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 thesis-figure-skill 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 “画图哲学 / 四步循环 / 对抗模型惯性” 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 / 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.