store

Store and update Alfred agent config, secrets, overlays, and KEDA scaling settings.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Kord96/kordinate --skill store-kord96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: store
Source: https://github.com/Kord96/kordinate/tree/main/agents/alfred/skills/store
Command: npx skills add https://github.com/Kord96/kordinate --skill store-kord96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a controlled, auditable way for Alfred to persist personal and runtime configuration data, secrets, overlays, and scaling parameters so callers can request changes without manual file edits or unsafe plaintext handling.

Core Features & Use Cases

  • Pass store writes: insert or update secret entries via the pass tool and verify existence without exposing values.
  • Config and profile edits: update YAML config fields and model profile entries with validation and projection refresh.
  • Overlay and platform publishing: write namespace overlays and environment scaling settings, validate kustomize and scaling constraints, then publish runtime projections.
  • Operational guarantees: direct writes when target is explicit, required validations after write, runtime projection publishing, and terse bullet response format for confirmations.
  • Use Case: Update KEDA scaling for an agent, persist the change to overlays/platform/<env>/scaling.yaml, validate numeric bounds, and publish the profile projection.

Quick Start

Ask Alfred to store a secret by saying: store key my/service/credential supersecret-value

Frequently Asked Questions about store

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I store and validate secrets using pass without exposing plaintext values?

Pass store writes allow you to insert or update secret entries via the pass tool and verify their existence without exposing plaintext values. Direct writes are applied when targets are explicit, followed by required validation checks.

How do I update KEDA scaling settings and validate numeric bounds for namespace overlays?

Updating KEDA scaling settings involves persisting changes to kustomize overlays and validating numeric bounds. After writing the scaling parameters, runtime projections are refreshed and published to reflect the updated configuration state.

Can I update YAML config fields and model profile entries with automatic validation?

YAML config fields and model profile entries can be updated with automatic validation and projection refresh. Direct writes are executed when the target is explicit, ensuring the source-of-truth files remain auditable and correctly structured.

What is the best way to persist runtime configuration and platform scaling parameters without manual file edits?

Persisting runtime configuration and platform scaling parameters without manual file edits is achieved through controlled, auditable direct writes. The process applies validations after writing and refreshes runtime projections to confirm the operational state.

Why does writing to the pass store require validation checks and projection publishing?

Writing to the pass store requires validation checks and projection publishing to maintain an auditable source-of-truth. This controlled approach ensures operational guarantees are met and confirms the secret entry exists without exposing its value.

Do I need explicit targets to perform direct writes to Alfred's stored data?

Explicit targets are required to perform direct writes to Alfred's stored data. When targets are explicit, the Skill executes the write, runs validation checks, and refreshes runtime projections to report results safely.