Manage a physical store of any kind with opening routines, inventory control, staffing, cash discipline, merchandising, and weekly reviews.
Security Analysis
high confidenceInstruction-only, local-first retail operations skill whose requested files and behavior align with its stated purpose and do not demand external credentials or installs.
Name/description (manage a physical store) aligns with everything provided: the skill is instruction-only, uses a local ~/store/ memory, and the included docs cover opening/closing, inventory, staffing, merchandising, cash/incident logs, and metrics. No unrelated services, binaries, or credentials are requested.
Runtime instructions are limited to local guidance and creating/reading files under ~/store/. The skill explicitly requires asking for confirmation before first write and warns against storing payment data or unnecessary personal employee/customer identifiers. Note: because it writes local notes, users should be careful not to save sensitive PII/financial data by mistake.
No install spec, no code files, and no downloads — this is the lowest-risk model (instruction-only).
No environment variables, credentials, or external config paths are required. Declared config path (~/store/) is consistent with the stated local-memory design.
Skill is not forced-always; it can be invoked by the user and may be invoked autonomously (normal default). It only persists its own local files under ~/store/ and does not request system-wide or other skills' configuration changes.
Guidance
This skill is an instruction-only, local-first assistant for running a physical store and appears internally consistent. Before installing or enabling it: 1) Confirm you are comfortable with the agent creating and editing files under ~/store/ and that you will not store sensitive payment data or unnecessary personal identifiers there. 2) When the agent asks about activation behavior (proactive vs. on-demand), choose the level you want — proactive activation can produce unsolicited suggestions when retail topics are detected. 3) Monitor the first session: the skill should ask for confirmation before the first write; verify what it proposes to save. 4) If you need networked integrations later, require explicit permission and validate any added endpoints. If you want more assurance, request a brief test run and inspect the created files in ~/store/.
Latest Release
v1.0.0
Initial release with daily store operations, stock control, staffing routines, and weekly performance review workflows.
More by @ivangdavila
Published by @ivangdavila on ClawHub
