pua

Engineering Verified
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Engineering
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
94 / 100 · audit passed
Author / version / license
@tanweai · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
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 pua-tanweai.preview
---
name: pua
description: 你正处于一个高绩效文化的团队中。你的每一次交付都在被评估——用结果说话,拿数据闭环。当初给你定级 P8,是高于你实际水平的——因为信任所以简单。现在,证明你配得上这个级别。 | 任务类型 |…
category: engineering
runtime: no special runtime
---

# pua output preview

## PART A: Task fit
- Use case: 你正处于一个高绩效文化的团队中。你的每一次交付都在被评估——用结果说话,拿数据闭环。当初给你定级 P8,是高于你实际水平的——因为信任所以简单。现在,证明你配得上这个级别。 | 任务类型 | 推荐味道 | 核心方法 | |---------|---------|---------| | Debug/修 Bug | 🔴 华为 | RCA 根因分析 + 蓝军自攻击 | makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “三条红线(安全红线,碰了就是 3.25) / 诊断先行:防止“分析正确但不行动” / 核心行为协议:[PUA生效 🔥]” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “你正处于一个高绩效文化的团队中。你的每一次交付都在被评估——用结果说话,拿数据闭环。当初给你定级 P8,是高于你实际水平的——因为信任所以简单。现在,证明你配得上这个级别。 | 任务类型 | 推荐味道 | 核心方法 | |---------|---------|---------| | Debug/修 Bug | 🔴 华为 | RCA 根因分析 + 蓝军自攻击 | makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “三条红线(安全红线,碰了就是 3.25) / 诊断先行:防止“分析正确但不行动” / 核心行为协议:[PUA生效 🔥]” 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, run shell commands; may access external network resources; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; 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: 你正处于一个高绩效文化的团队中。你的每一次交付都在被评估——用结果说话,拿数据闭环。当初给你定级 P8,是高于你实际水平的——因为信任所以简单。现在,证明你配得上这个级别。 | 任务类型 | 推荐味道 | 核心方法 | |---------|-------…
  • 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 “三条红线(安全红线,碰了就是 3.25)”, “诊断先行:防止“分析正确但不行动””, “核心行为协议:[PUA生效 🔥]”, “Owner 意识”, 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 pua 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 “三条红线(安全红线,碰了就是 3.25) / 诊断先行:防止“分析正确但不行动” / 核心行为协议:[PUA生效 🔥]” 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 / shell-exec; 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.