argos-data-import
Skill3 starsChanged 2 months agoApache-2.0View on GitHub
Help developers build third-party tools that import, inspect, migrate, or analyze Argos data. Use when Codex needs to work with Argos provider configuration, model configuration, MCP/app settings, sessions, messages, legacy chat data, `agent.db`, `chat.db`, SQLCipher encrypted SQLite, Electron safeStorage wrapped passwords, Tauri importers, or native macOS/Windows/Linux data access.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- argos-releaseSkill
- argos-sddSkill
- awwwards-animationsSkill
- baseline-uiSkill
- bun-file-ioSkill
- design-taste-frontendSkill
- fork-syncSkill
- pi-updateSkill
- react-doctorSkill
- shadcnSkill
- tanstack-formSkill
- tanstack-pacerSkill
- tanstack-querySkill
- tanstack-rangerSkill
- tanstack-routerSkill
- tanstack-storeSkill
- tanstack-tableSkill
- tanstack-virtualSkill
- turborepoSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- vgpuSkill
- viteSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use this skill to design or implement importers for Argos local data.
- Very specific: line 18
Read references/data-locations.md to locate agent.db, sidecar files, encryption metadata, and backup paths.
- Distinctive: line 20
Read references/sqlite-access.md before opening SQLite.
- Distinctive: line 23
Read references/schema-reference.md for provider config, settings, session, message, and legacy table relationships.
- Very specific: line 25
Read references/import-recipes.md when writing extractor code, mapping Argos data to another app, or creating a compatibility import.
- Very specific: line 32
Never open the active agent.db read-write from a third-party tool.
- Very specific: line 34
If Argos is running, either ask the user to quit it or make a WAL-aware snapshot before import.
- Distinctive: line 35
Prefer parameterized key APIs for SQLCipher passwords.
- Very specific: line 37
When the schema has changed, inspect schema_versions, sqlite_master, and the table classes under src/main/presenter/sqlitePresenter/tables/ …
- Distinctive: line 42
Use these repository files as the current source of truth when updating the skill or answering version-sensitive questions:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Argos Data Import
Overview
Use this skill to design or implement importers for Argos local data. Treat Argos's SQLite schema as an internal but documentable contract: inspect the current schema when precision matters, prefer read-only snapshots, and avoid writing to a live profile.
Workflow
- Identify the source: live Argos profile, copied profile, sync backup, exported
agent.db, or legacychat.db. - Read references/data-locations.md to locate
agent.db, sidecar files, encryption metadata, and backup paths. - Read references/sqlite-access.md before opening SQLite. Decide whether the database is unencrypted, can be unlocked through Electron safeStorage, or must ask the user for the SQLite password.
- Read references/schema-reference.md for provider config, settings, session, message, and legacy table relationships.
- Read references/import-recipes.md when writing extractor code, mapping Argos data to another app, or creating a compatibility import.
Safety Rules
- Get explicit user consent before reading local Argos data. Provider keys, OAuth tokens, MCP env vars, prompt text, message traces, and chat content may be sensitive.
- Never open the active
agent.dbread-write from a third-party tool. Copyagent.db,agent.db-wal, andagent.db-shm, or use SQLite backup APIs through Argos itself. - If Argos is running, either ask the user to quit it or make a WAL-aware snapshot before import.
- Prefer parameterized key APIs for SQLCipher passwords. Do not interpolate passwords into SQL.
- Redact secrets by default in logs, telemetry, previews, and generated sample output.
- When the schema has changed, inspect
schema_versions,sqlite_master, and the table classes undersrc/main/presenter/sqlitePresenter/tables/before assuming column availability.
Source Files
Use these repository files as the current source of truth when updating the skill or answering version-sensitive questions:
src/main/presenter/sqlitePresenter/index.tssrc/main/presenter/sqlitePresenter/connectionConfig.tssrc/main/presenter/databaseSecurityPresenter/index.tssrc/main/presenter/sqlitePresenter/tables/*.tssrc/main/presenter/agentRuntimePresenter/messageStore.tssrc/main/presenter/agentRuntimePresenter/sessionStore.tssrc/main/presenter/configPresenter/**
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.