Journal
kazukinagata/shinkoku
This skill should be used when the user wants to record bookkeeping entries (仕訳), import transaction data from CSV files, receipts, or invoices, or manage their general ledger.
How to query a Well workspace correctly — discover the schema first, then query the right root.
Install Querying Well Data
$ npx skills add WellApp-ai/Well --skill querying-well-data -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WellApp-ai/Well querying-well-data --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/well/skills/querying-well-data .claude/skills/querying-well-data && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .claude/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-dataType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WellApp-ai/Well --skill querying-well-data -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WellApp-ai/Well querying-well-data --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/well/skills/querying-well-data .agents/skills/querying-well-data && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .agents/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WellApp-ai/Well --skill querying-well-data -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WellApp-ai/Well querying-well-data --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/well/skills/querying-well-data .cursor/skills/querying-well-data && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .cursor/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WellApp-ai/Well.git --path plugins/well/skills/querying-well-data--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WellApp-ai/Well --skill querying-well-data -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WellApp-ai/Well querying-well-data --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/well/skills/querying-well-data .gemini/skills/querying-well-data && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .gemini/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WellApp-ai/Well querying-well-dataInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WellApp-ai/Well --skill querying-well-data -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/well/skills/querying-well-data .github/skills/querying-well-data && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .github/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WellApp-ai/Well --skill querying-well-data -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WellApp-ai/Well querying-well-data --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/well/skills/querying-well-data .opencode/skills/querying-well-data && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "querying-well-data" agent skill from https://github.com/WellApp-ai/Well/tree/main/plugins/well/skills/querying-well-data into .opencode/skills/querying-well-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "querying-well-data", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
querying-well-data- GitHub stars
- 345
- Token cost
- ~703 tokens
- SKILL.md length
- 299 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
How to query a Well workspace correctly — discover the schema first, then query the right root.
- The user asks about their invoices
- SKILL.md covers The one rule: discover before…, The roots you can read, Filtering and Gotchas
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Bank transactions
What it does
Querying Well Data is an agent skill from WellApp-ai/Well. How to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any wellqueryrecords call.
Its SKILL.md is about 700 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Forms and invoices and Accounting and bookkeeping. The repository describes itself as: No more Sundays on Finance. We build the infrastructure that retrieves, processes, and routes your financial and business data to your FinOps stack, so founders can ship, not… The licence is MIT.
When your agent uses it
- The user asks about their invoices
- Bank transactions
- Accounting ledger in Well
- Before writing any wellqueryrecords call
Example prompts
- “/querying-well-data”
What it can do on your machine
Read from SKILL.md and the folder at commit c740217. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Querying Well Data loads about 703 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 299 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from WellApp-ai/Well at commit c740217, republished under its MIT licence (© WellApp-ai). 299 words, ~703 tokens.
Download SKILL.mdSave it as
.claude/skills/querying-well-data/SKILL.md (or your agent's skills folder).- name
- querying-well-data
- description
- How to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any well_query_records call.
Querying Well data
Well exposes a workspace's financial graph through three MCP tools:
well_get_schema()— list every available root (entity type).well_get_schema({ root })— list the fields available on one root, with types and semantic context.well_query_records({ root, fields, whereClause?, orderBy?, limit? })— read rows.well_get_entity({ root, id })— fetch one record by id.
The one rule: discover before you query
Always call well_get_schema(root) first, pick the fields you need from what it returns, then call well_query_records. Field paths are arrays: "invoices.issuer.name" → ["invoices", "issuer", "name"]. Do not guess field names — they vary by root and are documented in the schema response (each field carries a type and often a context explaining what it means).
The roots you can read
Calling well_get_schema() with no argument returns the full set. It includes far more than invoices and companies — in particular the accounting graph:
- Commercial documents:
invoices,invoice_items,invoice_transactions - Parties:
companies,people,payment_means - Banking:
accounts,transactions,account_balances - Accounting graph (read-only, posted by Well's pipelines):
ledger_accounts,journals,journal_entries - Reference:
tax_rates,exchange_rates,categories,connectors - Workspace:
memberships,tasks,workspace_connectors
If you are about to answer a financial question by reconstructing it from raw invoices, stop and check well_get_schema() first — the posted ledger (journal_entries, ledger_accounts) is almost always the correct, more accurate source. See the well:compte-de-resultat and well:balance-sheet skills.
Filtering
whereClause is a Hasura-style boolean expression. Use the operator the field's type allows (from the schema):
numeric/date→_eq,_gt,_lt,_gte,_lteenum→_eq,_neq,_in,_nin,_is_nulltext→_eq,_like,_ilike- relations → nest:
{ "issuer": { "name": { "_ilike": "%acme%" } } }
Gotchas
- Reads are scoped to the authenticated workspace automatically — you never pass a workspace id.
- Select the specific fields you need (5–15), not everything — it is faster and cheaper.
- Amounts on commercial documents are in the document currency; check the schema
contextfor currency fields before summing across currencies (seeexchange_rates).
© WellApp-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/well/skills/querying-well-data of WellApp-ai/Well.
Open the folder on GitHubat commit c740217
Compare with similar skills
Querying Well Data next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Querying Well Data this skillWellApp-ai/Well | 345 | — | ~703 | Automated safety check: Pass | MIT | |
| Journalkazukinagata/shinkoku | 365 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Invoice Organizerdavila7/claude-code-templates | 32k | 12 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Invoice Po Reconciliationpnp/sharepoint-skills | 132 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Financial ParserOneWave-AI/claude-skills | 328 | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Invoice Organizerborghei/Claude-Skills | 886 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Invoice Organizer
davila7/claude-code-templates
Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders.
Invoice Po Reconciliation
pnp/sharepoint-skills
Reconciles one or more user-selected invoice files against matching purchase orders in the Purchase Order library.
Financial Parser
OneWave-AI/claude-skills
Extract and analyze data from invoices, receipts, bank statements, and financial documents.
Invoice Organizer
borghei/Claude-Skills
Categorize invoices and receipts by vendor, expense, and tax bucket, detect duplicates, and produce a tax-ready monthly summary.
Lexware Office
HybridAIOne/hybridclaw
Work with Lexware Office contacts, products, invoices, quotations, bookkeeping vouchers, receipts, payment status, and guarded invoice, quotation, or expense writes through the Public API.
More from WellApp-ai/Well
All 36 skills in this repoTech Divergence
WellApp-ai/Well
Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions
Ar Aging
WellApp-ai/Well
Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace.
Autonomous Loop
WellApp-ai/Well
Iterate until success or limit, composing existing skills with Jidoka integration
Balance Sheet
WellApp-ai/Well
Build a balance sheet (bilan) from a Well workspace. An agent skill from WellApp-ai/Well.
Bpmn Workflow
WellApp-ai/Well
Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios
Cash Flow Forecast
WellApp-ai/Well
Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions.
Related
Categories
Questions about Querying Well Data
What does Querying Well Data do?
How to query a Well workspace correctly — discover the schema first, then query the right root. Querying Well Data is an agent skill from WellApp-ai/Well. How to query a Well workspace correctly — discover the schema first, then query the right root.
When should I use Querying Well Data?
Querying Well Data fits situations like: the user asks about their invoices; bank transactions; accounting ledger in Well; before writing any wellqueryrecords call.
How do I install Querying Well Data in Claude Code?
Run `npx skills add WellApp-ai/Well --skill querying-well-data -a claude-code`. Or copy the skill folder (plugins/well/skills/querying-well-data in WellApp-ai/Well) into .claude/skills/querying-well-data in your project. Claude Code loads it when a task matches its description.
How do I install Querying Well Data in Codex?
Run `npx skills add WellApp-ai/Well --skill querying-well-data -a codex`. Or copy the skill folder (plugins/well/skills/querying-well-data in WellApp-ai/Well) into .agents/skills/querying-well-data in your project. Codex loads it when a task matches its description.
Can I use Querying Well Data in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WellApp-ai/Well --skill querying-well-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/querying-well-data, .gemini/skills/querying-well-data, .github/skills/querying-well-data and .opencode/skills/querying-well-data in your project.
What does Querying Well Data need to run?
SKILL.md names no scripts, command-line tools or credentials: Querying Well Data is instructions for the agent only.
Does Querying Well Data access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Querying Well Data safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Querying Well Data use?
Querying Well Data is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Querying Well Data use?
About 703 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Querying Well Data?
Skills that share tags, products or a category with Querying Well Data: Journal (kazukinagata/shinkoku, 365 stars), Invoice Organizer (davila7/claude-code-templates, 32k stars), Invoice Po Reconciliation (pnp/sharepoint-skills, 132 stars) and Financial Parser (OneWave-AI/claude-skills, 328 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Querying Well Data?
WellApp-ai (a GitHub organization) maintains it in WellApp-ai/Well, which has 345 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.
Source: WellApp-ai/Well on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.