dwlf

What This Skill Does

The DWLF skill provides a powerful interface for the DWLF (dwlf.co.uk) market analysis platform, enabling OpenClaw to retrieve sophisticated financial data for both crypto and traditional stocks. It covers the entire trading lifecycle, from initial research and technical analysis—including EMA, RSI, DSS, S/R levels, and trendlines—to strategy management, portfolio tracking, and trade journaling. By integrating directly with the DWLF v2 API, this skill allows users to maintain a data-driven edge by fetching real-time market data, viewing indicator-based signals, and even triggering asynchronous backtesting of visual strategies.

Installation

To integrate this tool into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/andywilliams/dwlf Ensure you have configured your API keys by referencing the TOOLS.md file in your repository, as authentication requires a bearer token formatted as ApiKey dwlf_sk_... in the request header.

Use Cases

This skill is ideal for quantitative traders, day traders, and investors looking to automate their technical analysis workflows. Use it to:

• Analyze specific assets like BTC-USD or NVDA by fetching OHLCV data or custom indicator reports.
• Monitor active trade signals to stay ahead of market volatility.
• Build and backtest custom trading strategies to validate hypotheses before executing live trades.
• Manage watchlists and log trade entries for better performance tracking and retrospective review.

Example Prompts

1. "What is the current RSI and EMA status for BTC-USD, and are there any active support/resistance levels?"
2. "Run a backtest for my 'Golden Cross' strategy on ETH-USD for the last 30 days and summarize the results."
3. "Add SOL-USD to my watchlist and show me the most recent trade signals for the crypto market."

Tips & Limitations

• Symbol Formatting: Always ensure crypto assets use the -USD suffix (e.g., BTC-USD), while stocks use their standard ticker symbols.
• Async Operations: Backtests are asynchronous. If you trigger a backtest, the API returns a status, so you will need to poll the results endpoint using the ID provided until the process is marked as complete.
• Data Scope: Always check the API documentation for specific interval limitations (e.g., 1d) to ensure you are receiving the granular data required for your analysis.