[Feature Request] Feature your Workflow on FlowStacks: let coding agents use env schemas without exposing secrets

Open
  • Is something wrong?
#1,084 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
28/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
typescript
Domain
documentation

Research direction

Use the linked “Suggest a workflow” GitHub issue template in the Awesome AI Workflows repository. Describe a Varlock workflow that gives coding agents schema context without real secrets, and name deterministic checks such as validation and scans for leaked or malformed values. Done when the suggestion is submitted with the use case and checks; the issue provides no project files or tests to inspect.

Written by the indexing model from the issue text.

Description

enhancement
Description

Hey! We maintain Awesome AI Workflows / FlowStacks and came across Varlock.

The “schemas for agents, secrets for humans” model looks like an especially good fit for a workflow we're interested in: give a coding agent enough .env.schema context to configure an application correctly without exposing the real secrets, then run deterministic validation / varlock scan checks before accepting the agent's changes.

FlowStacks hosts reproducible AI workflows and machine-verifies their deterministic parts in CI. For this recipe, we could test the schema/config path and verify that deliberately leaked or malformed values are caught, without ever treating the model-generated code itself as inherently trustworthy.

Would you be up for suggesting a Varlock workflow along those lines or whichever AI-agent workflow you think best demonstrates the project?

You don't need to build the FlowStacks recipe or our CI. Just open our Suggest a workflow GitHub issue with the use case and the deterministic checks you think matter; we'll turn it into the recipe and wire up verification.

[Suggest a workflow — GitHub issue template]

If it passes, it gets a permanent FlowStacks page with setup, stack, limits and live verification results, plus an entry in Awesome AI Workflows.

We also occasionally feature standout workflows on r/WebAfterAI [14K members] when they fit what we're covering. That's editorial, separate from acceptance and not guaranteed.

Varlock feels almost purpose-built for this kind of verified agent workflow, so we'd be glad to have it represented.

Motivation

No response

Proposed Solution

No response

Alternatives

No response

Additional Information

No response

Dominant language
TypeScript
Stars
4.9k
Forks
140
Avg merge
2d 3h
Merged PRs (30d)
35

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dmno-dev/varlock

All issues in dmno-dev/varlock

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.