fpl-copilot
FPL Copilot
Analyze current FPL data, maintain saved squads, and produce self-contained reports. This skill specifies operations and completion criteria; choose suitable tools or commands from the actual environment.
Workflow
1. Establish capabilities and storage
Inspect the available tools and locate this skill’s resources relative to its installed location. Identify capabilities for HTTP requests, JSON processing, SQLite 3 queries and writes, document persistence, and report delivery. On a shell-equipped host, infer suitable installed commands or scripting libraries; on other hosts, use exposed native tools. Tool names and executables are implementation choices.
Resolve storage once using the rule below, then reuse the resulting mapping for every reference and operation. Keep FPL data separate from the agent application's internal storage.
Storage resolution (in precedence order):
- Use an explicit user-selected FPL location or a host-provided binding for the stable namespace
fpl-copilot. If these disagree, ask which to use before writing. - Without an explicit selection or host binding, use the desktop root
~/.fplcopilot/, expanded to an absolute path through the current user's home directory. Reuse this root even when the working directory or conversation changes. - On a host without a desktop home, request persistent storage for namespace
fpl-copilotfrom its storage capability. Reopen its existing binding; if the host cannot provide a stable binding, ask the user to select a durable location before creating state. Conversation-local storage must be identified as such and selected explicitly.
Derive fplcopilot.db, squads/, reports/, and player-history-sync.json from that one root. If the host uses separate resource handles, persist their mapping under the same namespace through the host's storage configuration. Verify that mapping can be reopened before claiming cross-conversation persistence. Every mention of a “resolved” location in the references means this mapping, never a fresh location choice.