// Add a new blog post or article to the documentation collection. Use when user provides a URL to a blog post, article, or tweet linking to one.
Fetch a non-accessible paper PDF via Sci-Hub. Use when a paper is behind a paywall or not freely available. Accepts a DOI, paper URL, or arXiv ID.
Add a new research paper to the documentation collection. Use when user provides a URL to a paper or tweet linking to one.
Add a new code repository to the documentation collection. Use when user provides a URL to a GitHub, GitLab, Bitbucket, source repository, or a discussion linking to one.
Add a new book to the documentation collection. Use when user provides a URL to a book page or tweet linking to one.
Pick a random item from the trading content collection and compose a tweet about it on X.
| name | add-post |
| description | Add a new blog post or article to the documentation collection. Use when user provides a URL to a blog post, article, or tweet linking to one. |
| argument-hint | ["url"] |
Add a new blog post or article to the documentation collection.
Check browser is activated:
tabs_context_mcp to verify browser connectionclaude --chrome or type /chromeFind the canonical blog post page: If the input URL is:
Important: For Twitter/X, Medium, Substack, and sites requiring JavaScript, use browser automation instead of WebFetch.
Extract blog post information:
For pages requiring browser: Use navigate to open the page, then use javascript_tool to extract content. See CLAUDE.md > JavaScript DOM Extraction Patterns for selectors and examples.
If CAPTCHA appears, ask the user to complete it manually.
Determine category: Based on the extracted content, automatically determine the category:
source/learn/blog-posts.rst) - for posts about algorithmic trading, quantitative finance, market analysis, portfolio management, risk management, backtesting, etc.source/learn/ai-and-machine-learning.rst) - for posts primarily about machine learning, deep learning, neural networks, or AI techniques applied to trading
Not trading related: Don't add this post. If the user specifically asked to add this post, ask user for confrimation.Only ask the user if the content is ambiguous (e.g., equally about ML techniques AND trading strategies). If clearly one category, proceed without asking.
Add to the appropriate .rst file: Use this exact format (matching existing entries):
Title of the Blog Post
----------------------
Description paragraph(s) here. Keep it informative but concise.
Two paragraph summary of the post here.
`Read the blog post <https://url-here>`__.
Or with author attribution:
Title of the Blog Post
----------------------
Description paragraph(s) here.
Two paragraph summary of the post here.
By Author Name.
`Read the blog post <https://url-here>`__.
Important formatting notes:
__If the source of the link is a discussion like a tweet, then include a paragraph with a link to that tweet with the comment "Mentioned by XXX in this discussion" and include what they say about it.
Commit and push:
Save as PDF: Follow the procedure in README-browser.md > Saving PDFs > How it works using:
<slugified-title>.pdfarticles/ directory