output-dev-credentials
Store and reference encrypted secrets in Output SDK workflows using @outputai/credentials.
Connecting the steps of a workflow
What it does
The @outputai/credentials package provides encrypted secrets management for Output SDK workflows. It replaces process.env patterns with a structured, encrypted YAML-based system that supports scoped credentials with deep merging.
Use when integrating API keys, database passwords, or third-party tokens
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the one file in the skill’s folder on GitHub; none is a script or program.
Asks for an API key or token
You will need an account with the service it talks to, and your own key. Keep keys in your settings or environment, never in a chat.
How we know
The SKILL.md names API_KEY, SERVICE_API_KEY.
Mentions an outside service
The instructions point your AI at these sites or APIs. Anything it sends there leaves your computer.
How we know
Web addresses in the SKILL.md, excluding GitHub and documentation sites: api.service.com.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
Lets your AI run any terminal command without asking, while the skill is in use
While the skill is working, Claude Code will not stop to ask before each terminal command. The permission ends when you send your next message.
How we know
SKILL.md line 1: “allowed-tools: [Read, Write, Edit, Bash, Glob]”. Read 2026-10-05, commit 46e7530.
SKILL.md, line 1 ↗No serious risk pattern found
Launch7’s automated check read all 1 text files in this skill and matched none of its serious risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 46e7530 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to growthxai/output: 2026-10-02 (3 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from growthxai
All from this publisher →- output-build-workflow
Implement an Output SDK workflow from a plan document.
- output-debug-workflow
Debug Output SDK workflow issues.
- output-dev-agent-class
Use the Agent class for multi-step tool loops, conversation history, streaming progress, and reusable LLM agents.
- output-dev-code-style
Code style conventions for Output SDK workflow projects.
- output-dev-create-skeleton
Generate workflow skeleton files using the Output SDK CLI.
