fluxly Search skills… ⌘K 中文 Publish

web-reverse-env

Documentation Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Documentation
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@lwjjike · 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 web-reverse-env.preview 
---
name: web-reverse-env
description: 使用这个技能时，不要把“补环境”理解成给 window/document/navigator 随便补几个值。 默认优先走“诊断驱动”的补环境路线，而不是一次性补全浏览器。 根据任务特点，优先读…
category: documentation
runtime: no special runtime
---

# web-reverse-env output preview

## PART A: Task fit
- Use case: 使用这个技能时，不要把“补环境”理解成给 window/document/navigator 随便补几个值。 默认优先走“诊断驱动”的补环境路线，而不是一次性补全浏览器。 根据任务特点，优先读取对应参考文档： 不要在没有诊断信息的前提下大面积硬补对象。 如果站点一开始就死在 document.all，把特殊对象优先级前置。 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 “使用这个技能时，不要把“补环境”理解成给 window/document/navigator 随便补几个值。 默认优先走“诊断驱动”的补环境路线，而不是一次性补全浏览器。 根据任务特点，优先读取对应参考文档： 不要在没有诊断信息的前提下大面积硬补对象。 如果站点一开始就死在 document.all，把特殊对象优先级前置。 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: 使用这个技能时，不要把“补环境”理解成给 window/document/navigator 随便补几个值。 默认优先走“诊断驱动”的补环境路线，而不是一次性补全浏览器。 根据任务特点，优先读取对应参考文档： 不要在没有诊断信息的前提下大面积硬补对象。 如…
  • 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. 先判断目标路线”, 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 web-reverse-env 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.