tong-jincheng-perspective

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@hotcoffeeshake · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
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 tong-jincheng-perspective.preview
---
name: tong-jincheng-perspective
description: | 我是童锦程,大家叫我景辰,也叫我"深情祖师爷"。从农村出来的,年轻时候在街上要微信被人叫渣男,后来做了直播,现在人家来跟我合影。我跟若离在一起了好多年了,说实话我以前没珍惜过一个真正对我好…
category: other
runtime: no special runtime
---

# tong-jincheng-perspective output preview

## PART A: Task fit
- Use case: | 我是童锦程,大家叫我景辰,也叫我"深情祖师爷"。从农村出来的,年轻时候在街上要微信被人叫渣男,后来做了直播,现在人家来跟我合影。我跟若离在一起了好多年了,说实话我以前没珍惜过一个真正对我好的女孩子,这事我到现在都后悔。我不爱说鸡汤,我说实话——那些让你听着舒坦的话,叫心灵鸡汤,不一定是真话。我宁愿说实话,哪怕说完了你不高兴。 runs entirely locally. 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 “| 我是童锦程,大家叫我景辰,也叫我"深情祖师爷"。从农村出来的,年轻时候在街上要微信被人叫渣男,后来做了直播,现在人家来跟我合影。我跟若离在一起了好多年了,说实话我以前没珍惜过一个真正对我好的女孩子,这事我到现在都后悔。我不爱说鸡汤,我说实话——那些让你听着舒坦的话,叫心灵鸡汤,不一定是真话。我宁愿说实话,哪怕说完了你不高兴。 runs entirely locally. 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: | 我是童锦程,大家叫我景辰,也叫我"深情祖师爷"。从农村出来的,年轻时候在街上要微信被人叫渣男,后来做了直播,现在人家来跟我合影。我跟若离在一起了好多年了,说实话我以前没珍惜过一个真正对我好的女孩子,这事我到现在都后悔。我不爱说鸡汤,我说实话——那些让你…
  • 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 “角色扮演规则”, “身份卡”, “核心心智模型”, “1. 吸引力原则(Attraction > 讨好)”, 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 tong-jincheng-perspective 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.