Introduce secret-backed settings without leaking secret material into repo-owned config.
Introduce secret-backed settings without leaking secret material into repo-owned config.
npx skills add https://github.com/wonderlydotcom/internal-tool-freetool --skill add-secret이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Declare and roll out an app-owned logical GCS bucket through app-resource sync.
Create or update Freetool ASP.NET Core API controllers in F# using the established command-handler, authorization, error-mapping, DTO validation, and JSON converter patterns. Use when adding a new controller, adding endpoints to an existing controller, defining request/response DTOs for API transport, or introducing custom JSON conversion for DTO/domain boundary types.
Use owner-safe logs, traces, metrics, and alerts paths and triage app telemetry without direct backend access.
Run and seed internal tool app repos locally with the shared CLI while preserving data and secret safety boundaries.
Add or update non-secret application configuration and thread it through runtime and deploy wiring.
Create or update the repo's merge-to-deploy GitHub Actions workflow.
| name | add-secret |
| description | Introduce secret-backed settings without leaking secret material into repo-owned config. |
| mcp_server | internal-tools |
| mcp_tool | use_workflow |
| mcp_workflow | add-secret |
| mcp_repo | freetool |
| mcp_kind | shared-stub |
Call internal-tools.use_workflow with:
workflow_name="add-secret"repo_name="freetool"If the task is not an obvious fit for this stub, call internal-tools.recommend_workflows first and then use the top shared workflow before editing.
Then follow the returned:
If the change also touches adjacent concerns, follow the related workflows returned by internal-tools.use_workflow.