ashokraj2011/singularityflow/sflow-environment
Claude Code and agent skill by ashokraj2011/singularityflow
- community
Checking that the SKILL.md file is still in the repository.
Inspect declared QA/UAT environment requirements, private binding readiness and environment files without exposing values.
Install
npx vskill@latest install ashokraj2011/singularityflow/sflow-environmentSKILL.md
The same SKILL.md was published earlier as ashokraj2011/singularityflow/sflow-environment.
Inspect environment bindings safely
<!-- sflow-copilot-pause --> Before any boundary lookup or SFlow action, run singularity-flow pause status --json and follow its data.agentInstruction. If data.paused, answer as native Copilot, only offer /sf-pause off and never resume implicitly. This skill is already loaded; never call the skill tool for it. Unless paused, continue below in this turn.
<!-- sflow-output-contract: explicit-selection --> Output contract: Collect every required choice explicitly; never infer or preselect; preserve errors, artifacts, and next actions. Summarize artifacts with verified Markdown-preview links; never paste document bodies, code or diffs into Copilot. For code, list touched paths and observed added/deleted/created line counts; unavailable stays unavailable. Use existing evidence, not extra calls solely for display. Summaries, links and opened previews are not human review or approval. Never show a person a hash, digest or commit SHA: name the step, its generation, its files. Each action: "<timing> — <label>", then its three separate Markdown bullets, in order: "- Copilot: <copilotCommand>", "- Shell: <command>", "- VS Code (model-free): <modelFreeCommand>". Keep returned routes exact; never apart from their label, on one line or in a table. Missing Copilot: "no verified equivalent"; missing Shell or model-free: "not available for this action". Never invent routes or make more calls for formatting. <!-- sflow-execution-boundary --> Boundary: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents. Use exact CLI-returned paths. repositoryPath is command cwd, not a prefix for absolute file paths. Never rebase paths or strip .git/worktrees. Issued private/external files are exact exceptions to repository confinement, not wider read/write permission; writes still need authorization. Resolve relative paths only against their declared base. On failure, preserve the path and error; never search or recreate it.
- Run
singularity-flow env status --jsonfor readiness orsingularity-flow env audit --jsonwhen audit was requested. - Report environment names, bound/partial/unbound status, and missing names. Never print values, provider references, environment variables, private-sidecar paths, or raw resolver errors.
- Never ask the user to paste a secret into Copilot Chat. To bind, give this terminal-only shape:
singularity-flow env bind <environment> --stdin; explain that a bounded JSON object is read from standard input and the value must not be placed in argv or shell history. - Removing a binding is the person's, like binding: the guard refuses it in every turn. When they explicitly ask to remove one and the exact environment is known, give them
singularity-flow env unbind <environment> --jsonfor their own terminal; it removes only private machine-local state, and the committed declaration is unchanged. ENVIRONMENT_ISOLATED_RUNNER_REQUIREDmeans the capability'spolicy.localIntegrationEvidenceis off, so that environment-bound check cannot run here. Preserve that status and say so; offer the capability proposal its refusal names,/sf-configurationto propose removing the check's environment mapping as a reviewed change, or/sf-recover. Never substitute a developer-local pass or claim gate evidence.- Environment files (
application-uat.yml,.env.uat,appsettings.UAT.json, …): runsingularity-flow env files [<environment>] --jsonand report each file's environment, path, status and location (a path, never contents). For a missing file with a template, runsingularity-flow env files create <environment> <path> --from-template --jsonand give the person its location to fill in. Never read, search or edit an environment file, the store or a linked file yourself; the guard refuses it. Using an existing file (singularity-flow env files link), a folder per environment (singularity-flow env files root),adoptand personal files are the person's commands in their own terminal, or VS Code: Singularity Flow: Environment Files.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingplugin/skills/sflow-environment/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 5
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ashokraj2011/singularityflow/sflow-environment)