remove-app
- Repo stars 4
- License NOASSERTION
- Author updated Live
- Author repo dotfiles
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @Hayao0819 · NOASSERTION
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Linux
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Env read
- 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，默认拥有全部工具权限。
---
name: remove-app
description: Removes an application from NixOS or Home Manager configuration. Locates all references, assesse…
category: other
runtime: no special runtime
---
# remove-app output preview
## PART A: Task fit
- Use case: Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared modules, and safely removes. Use Grep to find all references to the package across .nix files: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “1. Locate / 2. Assess Impact / 3. Remove” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared modules, and safely removes. Use Grep to find all references to the package across .nix files: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “1. Locate / 2. Assess Impact / 3. Remove” 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, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, read environment variables; 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. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “1. Locate / 2. Assess Impact / 3. Remove”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: remove-app
description: Removes an application from NixOS or Home Manager configuration. Locates all references, assesse…
category: other
source: Hayao0819/dotfiles
---
# remove-app
## When to use
- Removes an application from NixOS or Home Manager configuration. Locates all references, assesses impact on shared mod…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “1. Locate / 2. Assess Impact / 3. Remove” and keep inference separate from source facts.
- read files, write/modify files, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "remove-app" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 1. Locate / 2. Assess Impact / 3. Remove
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Remove Application: $ARGUMENTS
1. Locate
Use Grep to find all references to the package across .nix files:
nixos/*/configuration.nix— System packagesmodules/nixos/*/default.nix— NixOS modulesmodules/home-manager/*/default.nix— Home Manager modulesmodules/home-manager/pkgs/global.nix— Cross-platform CLImodules/home-manager/pkgs/linux.nix— Linux-only CLI
2. Assess Impact
- Single location: Safe to remove directly
- Shared module: Ask the user — the module may be used by multiple systems
- Dependency: Inform the user if removing it would break another package
3. Remove
- Remove the package/configuration
- If the app had its own module directory, delete it (auto-import handles the rest)
- Clean up related config (environment variables, services, etc.)
4. Validate
nix flake check --extra-experimental-features 'nix-command flakes pipe-operators'
Decide Fit First
Design Intent
How To Use It
Boundaries And Review