Technical Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Design and operate back-office account opening pipelines from application intake through custodian submission and activation.
$ npx skills add JoelLewis/finance_skills --skill account-opening-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JoelLewis/finance_skills account-opening-workflow --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/JoelLewis/finance_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .claude/skills/account-opening-workflow && 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 "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .claude/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflowType 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 JoelLewis/finance_skills --skill account-opening-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JoelLewis/finance_skills account-opening-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .agents/skills/account-opening-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .agents/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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 JoelLewis/finance_skills --skill account-opening-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JoelLewis/finance_skills account-opening-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .cursor/skills/account-opening-workflow && 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 "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .cursor/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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/JoelLewis/finance_skills.git --path plugins/client-operations/skills/account-opening-workflow--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 JoelLewis/finance_skills --skill account-opening-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JoelLewis/finance_skills account-opening-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .gemini/skills/account-opening-workflow && 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 "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .gemini/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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 JoelLewis/finance_skills account-opening-workflowInstalls 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 JoelLewis/finance_skills --skill account-opening-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .github/skills/account-opening-workflow && 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 "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .github/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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 JoelLewis/finance_skills --skill account-opening-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JoelLewis/finance_skills account-opening-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/client-operations/skills/account-opening-workflow .opencode/skills/account-opening-workflow && 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 "account-opening-workflow" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/account-opening-workflow into .opencode/skills/account-opening-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "account-opening-workflow", 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.
account-opening-workflowDesign and operate back-office account opening pipelines from application intake through custodian submission and activation.
Account Opening Workflow is an agent skill from JoelLewis/finance_skills. Design and operate back-office account opening pipelines from application intake through custodian submission and activation. Use when building account opening automation, reducing NIGO rejection rates from custodians or clearing firms, defining document requirements for trusts, entities, IRAs, or estate accounts, setting up multi-custodian account opening across Schwab, Fidelity, or Pershing, troubleshooting account opening failures or processing delays, or benchmarking cycle times and first-submission…
Its SKILL.md is about 10k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Business, Finance & HR. The repository describes itself as: Claude Code skill plugins for financial services — 81 skills across 7 domain plugins covering investment management, compliance, advisory practice, trading, and operations. The licence is MIT.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 5c498ea. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Account Opening Workflow loads about 10k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 163 tokens; SKILL.md has 5,213 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.
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.
The full file from JoelLewis/finance_skills at commit 5c498ea, republished under its MIT licence (© JoelLewis). 5,213 words, ~10,175 tokens.
.claude/skills/account-opening-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Account type determination is the foundational decision in the account opening workflow. The registration type dictates the document requirements, approval gates, tax treatment, titling rules, and custodian submission path. Operations teams must maintain a comprehensive account type matrix that maps each registration type to its downstream processing requirements.
Individual and joint registration types:
Trust registration types:
Entity registration types:
Retirement account types:
Custodial and estate accounts:
Account numbering and classification:
The document requirements matrix is the operational backbone of account opening. It defines exactly which documents are required for each combination of account type, account features, and custodian. A well-maintained matrix prevents NIGO rejections, ensures regulatory compliance, and enables automation.
Universal documents (required for all account types):
Type-specific documents:
Feature-specific documents:
Custodian-specific variations: Each custodian maintains its own form library, field requirements, and validation rules. The operations team must maintain custodian-specific document matrices and update them when custodians revise their requirements. Common variations include: different account application forms, different signature requirements (e.g., one custodian requires a separate signature page while another accepts signatures on the application), different beneficial ownership forms, and different trust certification formats. Failure to track custodian-specific variations is a major source of NIGO rejections.
The application processing workflow is the sequence of steps from initial receipt of account opening request through account number assignment and confirmation. A well-designed workflow manages state transitions, enforces required gates, and provides visibility to all stakeholders.
Workflow stages:
Receipt and intake — the account opening request arrives from the advisor (via onboarding platform, CRM, email, or paper). The operations team logs the request, assigns it a tracking number, and records the timestamp. For firms with service-level agreements, the clock starts here.
Initial review and triage — an operations analyst reviews the request for completeness at a high level: is the account type clear, are the basic client details present, are the required documents attached. Requests are triaged by complexity: standard accounts (individual, joint, IRA) go to the automated or streamlined path; complex accounts (trusts, entities, estates) go to a specialized review queue.
Data entry or import — client data is entered into the firm's account opening system or imported from the onboarding platform. For API-integrated onboarding, this step is automated. For manual submissions, operations staff key in client information from the application forms. Data entry is a significant source of errors; validation rules should flag inconsistencies in real time.
Document completeness check — the operations analyst verifies that all required documents are present based on the document requirements matrix. This is a systematic, checklist-driven review: for the given account type plus features plus custodian, are all required documents attached, signed, and complete. Missing or incomplete documents trigger a NIGO hold and a request back to the advisor or client.
Data validation — automated and manual checks verify data consistency across all documents: name matches between application, W-9, and advisory agreement; SSN/EIN matches across forms; account type coding is consistent; address is complete and formatted correctly; beneficiary designations are complete for retirement accounts. Validation rules should be codified and automated wherever possible.
Supervisory review — certain account types and configurations require supervisory or compliance review before custodian submission. Triggers include: discretionary accounts, options trading approval, margin requests, accounts for senior investors (age 65+), PEP or EDD-flagged clients, high-net-worth thresholds, accounts with complex ownership structures. The supervisor reviews the application package, suitability documentation, and any compliance flags, then approves, rejects, or requests additional information.
Custodian submission — the validated and approved application package is submitted to the custodian via API, custodian portal, or manual upload. API submission is the target for standard account types; complex accounts often require portal or manual submission. The operations team records the submission timestamp and method.
Custodian processing and account number assignment — the custodian reviews the submission, runs its own validation, and either creates the account (returning an account number) or rejects it (NIGO). Processing time varies: API submissions for standard accounts may return an account number within minutes; manual submissions for complex accounts may take days to weeks. The operations team monitors submission status and follows up on aging submissions.
Confirmation and notification — upon receiving the account number, the operations team updates internal systems (CRM, PMS, billing), notifies the advisor and client, and triggers post-opening activities (funding, model assignment, welcome kit). The confirmation should include the account number, registration details, and any next steps required from the advisor or client.
Workflow state management: Each account opening request should have a defined state at all times: received, in-review, pending-documents, pending-supervisory-review, pending-compliance, submitted-to-custodian, NIGO-hold, approved, activated, or closed/withdrawn. State transitions should be logged with timestamps, responsible party, and any notes. A dashboard showing the distribution of requests across states enables operations management to identify bottlenecks, aging items, and capacity issues.
NIGO (Not In Good Order) rejections are the single largest source of delay, cost, and client dissatisfaction in account opening operations. A systematic approach to NIGO management includes prevention, categorization, remediation, tracking, and root cause analysis.
Common NIGO causes and prevention strategies:
NIGO categorization: NIGOs should be categorized by: (1) custodian — to identify custodian-specific patterns, (2) rejection reason — using a standardized taxonomy of NIGO codes, (3) account type — to identify which account types have the highest rejection rates, (4) originating advisor or office — to identify training needs, (5) severity — distinguishing between minor corrections (e.g., missing initials) and substantive deficiencies (e.g., missing trust agreement). This categorization enables targeted remediation and process improvement.
Remediation workflows: When a NIGO is received: (1) the operations team logs the rejection, categorizes it, and assigns it to an analyst; (2) the analyst determines the specific corrective action required; (3) if the correction can be made by operations (e.g., re-keying a data field), it is corrected and resubmitted; (4) if the correction requires the advisor or client (e.g., a missing signature, an additional document), the analyst contacts the advisor with a clear, specific request describing exactly what is needed; (5) a follow-up schedule is established (e.g., 2-day follow-up, 5-day escalation to the advisor's manager, 10-day escalation to operations management); (6) once the correction is received, the application is revalidated and resubmitted; (7) the NIGO is closed and the resolution is recorded.
NIGO tracking and reporting:
Regulatory holds and approval gates are control points in the account opening workflow where processing pauses until a specific review or approval is completed. These gates enforce compliance requirements, manage risk, and ensure appropriate oversight of complex or high-risk account openings.
Supervisory approval requirements:
Compliance review triggers:
Hold management and aging: Accounts in regulatory hold must be tracked with: the date the hold was placed, the reason for the hold, the assigned reviewer, and the expected resolution date. Hold aging reports should highlight items approaching or exceeding the firm's service-level targets. Typical targets: supervisory review within 2 business days, compliance review within 5 business days, escalation at 10 business days.
Escalation procedures: When a hold exceeds its target resolution time, the workflow should automatically escalate: first to the assigned reviewer's manager, then to the chief compliance officer or operations director, and finally to senior management. Escalation notifications should include the account details, the hold reason, the elapsed time, and any prior communications.
Straight-through processing (STP) is the goal of account opening automation: the application flows from submission through account creation without manual intervention. Achieving high STP rates requires investment in technology, data quality, and process standardization.
STP architecture:
OCR and data extraction: For firms that still receive paper applications or scanned documents, optical character recognition (OCR) and intelligent document processing (IDP) can extract data from forms and documents. Modern IDP platforms use machine learning to identify document types, extract field values, and flag low-confidence extractions for human review. OCR accuracy varies by document quality; validation against the client's profile data helps catch extraction errors.
Automated validation rules: The validation engine should enforce rules including: all required fields populated and formatted correctly, SSN/EIN passes check-digit validation, name matches across all documents (fuzzy matching to handle minor variations), address is valid and complete (USPS address validation), account type code maps correctly to the custodian's type codes, all required documents are present per the document requirements matrix, all signature fields are completed, beneficiary percentages sum to 100% for retirement accounts, trust certification includes all required elements (trust name, date, trustees, powers), and beneficial ownership certification is complete for entity accounts.
STP rate measurement:
Firms that custody client assets across multiple custodians (commonly Schwab, Fidelity, Pershing, and others) face additional complexity in account opening. Each custodian has its own forms, validation rules, API specifications, processing timelines, and NIGO patterns.
Managing custodian-specific requirements:
Custodian-specific form requirements (representative examples):
Parallel vs sequential submission: When a client is opening accounts at multiple custodians simultaneously (e.g., a trust account at Schwab and an IRA at Fidelity), the operations team must decide whether to submit in parallel or sequentially. Parallel submission is faster but requires the operations team to manage multiple concurrent workflows. Sequential submission is simpler to manage but extends the total processing time. Best practice: submit in parallel when the operations team has capacity and the account types are independent; submit sequentially when the accounts have dependencies (e.g., the IRA rollover depends on the trust account being established first).
Cross-custodian reconciliation: After accounts are opened, the operations team must reconcile the firm's internal records with each custodian's records to ensure: account numbers are correctly mapped, registration details match, account features (margin, options) are correctly reflected, and beneficiary designations are consistent. Discrepancies discovered during reconciliation must be resolved promptly before the account is activated.
Account activation is the transition from "account created at custodian" to "account fully operational and ready for trading." Post-opening activities ensure the account is properly funded, configured, and integrated into the firm's systems.
Funding verification:
Model portfolio assignment:
Initial trading enablement:
Welcome kit delivery:
30-day review:
Account maintenance handoff:
Three worked examples (multi-custodian RIA workflow design, NIGO reduction through automated pre-submission validation, and tiered approval workflows for complex account types) are in references/examples.md — load it when designing or benchmarking a concrete account opening process.
© JoelLewis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/client-operations/skills/account-opening-workflow of JoelLewis/finance_skills.
Open the folder on GitHubat commit 5c498ea
Account Opening Workflow 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 |
|---|---|---|---|---|---|---|
| Account Opening Workflow this skillJoelLewis/finance_skills | 206 | — | ~10k | Automated safety check: Pass | MIT | |
| Technical Analysttradermonty/claude-trading-skills | 3k | 4 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Theme Detectortradermonty/claude-trading-skills | 3k | 2 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Creating Financial ModelsChen-zexi/open-ptc-agent | 729 | 3 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Stock APIzhangxiangliang/stock-api | 2k | — | ~507 | Automated safety check: Pass | MIT | |
| Itr Walakaranb192/itr-wala | 871 | — | ~3.6k | Automated safety check: Pass | MIT |
tradermonty/claude-trading-skills
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
tradermonty/claude-trading-skills
Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.
Chen-zexi/open-ptc-agent
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
zhangxiangliang/stock-api
Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.
karanb192/itr-wala
File Indian income tax returns (ITR) for FY 2025-26 / AY 2026-27.
zillionare/zillionare
面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求,转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。
JoelLewis/finance_skills
Determine how to distribute capital across asset classes using strategic and tactical allocation frameworks.
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
JoelLewis/finance_skills
Analyze commodity markets including futures curve dynamics, roll yield, and supply/demand fundamentals.
JoelLewis/finance_skills
Analyze currency markets, exchange rate mechanics, and FX risk management for international portfolios.
JoelLewis/finance_skills
Provide frameworks for managing and paying off personal debt effectively.
JoelLewis/finance_skills
Build diversified portfolios using correlation analysis, efficient frontier construction, and factor-based diversification.
Categories
Design and operate back-office account opening pipelines from application intake through custodian submission and activation. Account Opening Workflow is an agent skill from JoelLewis/finance_skills. Design and operate back-office account opening pipelines from application intake through custodian submission and activation.
Account Opening Workflow fits situations like: building account opening automation; reducing NIGO rejection rates from custodians; defining document requirements for trusts; estate accounts.
Run `npx skills add JoelLewis/finance_skills --skill account-opening-workflow -a claude-code`. Or copy the skill folder (plugins/client-operations/skills/account-opening-workflow in JoelLewis/finance_skills) into .claude/skills/account-opening-workflow in your project. Claude Code loads it when a task matches its description.
Run `npx skills add JoelLewis/finance_skills --skill account-opening-workflow -a codex`. Or copy the skill folder (plugins/client-operations/skills/account-opening-workflow in JoelLewis/finance_skills) into .agents/skills/account-opening-workflow in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JoelLewis/finance_skills --skill account-opening-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/account-opening-workflow, .gemini/skills/account-opening-workflow, .github/skills/account-opening-workflow and .opencode/skills/account-opening-workflow in your project.
SKILL.md names no scripts, command-line tools or credentials: Account Opening Workflow is instructions for the agent only.
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.
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.
Account Opening Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 10k tokens (SKILL.md is roughly 41k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Account Opening Workflow: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Theme Detector (tradermonty/claude-trading-skills, 3k stars), Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars) and Stock API (zhangxiangliang/stock-api, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
JoelLewis (a GitHub user) maintains it in JoelLewis/finance_skills, which has 206 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on July 18, 2026.
Source: JoelLewis/finance_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.