Website Content Strategy

What it does

When your agent uses it

• Writing page copy
• Structuring documentation sections
• Crafting messaging that targets both developers and technical leaders (CTOs)

Example prompts

• “/website-content-strategy”

Requirements

• Node.js

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1Security: Secret values stay out of the versioned map and source control.
2. 2Consistency: One envilder.json = single source of truth for all
3. 3Developer Experience: One command replaces manual secret copying with a

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Website Content Strategy loads about 1.1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 458 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~75

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:31

  me SDKs resolve in-process; CLI and GHA `.env` outputs must be protected

• NoteMentions a .env fileSKILL.md:53

  - Works with existing `.env` workflows through generated files

• NoteMentions a .env fileSKILL.md:90

  x envilder --map=envilder.json --envfile=.env` |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 458 words, ~1,061 tokens.

name

website-content-strategy

description

Content strategy and audience-aware guidelines for the Envilder website. Use when writing page copy, structuring documentation sections, or crafting messaging that targets both developers and technical leaders (CTOs). Provides product context and selling points per audience.

| Without Envilder | With Envilder |
|------------------|---------------|
| Copy secrets manually from a provider console | `npx envilder --map=envilder.json --envfile=.env` |
| Ad hoc onboarding checklist | One documented resolution command |
| Secret paths duplicated across tools | Paths versioned in `envilder.json`; values stay in the provider vault |

© macalbert, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/website-content-strategy of macalbert/envilder.

Open the folder on GitHubat commit b6a0327