yearly_insights_parser
Overview
A new package that analyzes user-provided text summaries of yearly breakdowns (e.g., financial reports, project post-mortems, or performance reviews) and extracts structured insights. It uses an LLM to identify key themes, recurring issues, successes, and recommendations, then formats the output into a consistent, machine-readable structure. This helps users quickly digest and act on summarized yearly data without manual parsing.
Installation
pip install yearly_insights_parser
Usage
from yearly_insights_parser import yearly_insights_parser
response = yearly_insights_parser(
user_input="...", # user-provided text input
api_key="your_api_key", # optional, use LLM7 API key for higher rate limits
llm=your_llm_instance, # optional, use a custom LLM instance
)
The yearly_insights_parser function takes three parameters:
user_input: the text input to process (string)api_key: optional, use an LLM7 API key for higher rate limits (string)llm: optional, use a custom LLM instance (BaseChatModel instance)
By default, it uses the ChatLLM7 from langchain_llm7 <https://pypi.org/project/langchain-llm7/>_. If you want to use another LLM, you can pass your own instance:
from langchain_openai import ChatOpenAI
from yearly_insights_parser import yearly_insights_parser
llm = ChatOpenAI()
response = yearly_insights_parser(user_input="...", llm=llm)
Similarly, you can use ChatAnthropic or ChatGoogleGenerativeAI from langchain_anthropic <https://pypi.org/project/langchain-anthropic/>_ or langchain_google_genai <https://pypi.org/project/langchain-google-genai/>_ respectively.
Note that the default rate limits for LLM7 free tier should be sufficient for most use cases. If you need higher rate limits, you can provide your own API key using one of the above methods.
API Key for LLM7
The default rate limits for the LLM7 free tier are generally sufficient for most use cases. If you require higher rate limits for LLM7, you can provide your own API key:
- Via the
LLM7_API_KEYenvironment variable. - Directly by passing the
api_keyargument to the function:yearly_insights_parser(user_input="...", api_key="your_api_key")You can obtain a free API key by registering athttps://token.llm7.io/
Contributing
Please report any issues or suggestions on the GitHub issues page: https://github.com/chigwell/yearly-insights-parser/
Author
- Eugene Evstafev (hi@eugene.plus)
License
[MIT License] - see the LICENSE.md file for details.
Release files for yearly-insights-parser 2025.12.21101922
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| yearly_insights_parser-2025.12.21101922.tar.gz | 5.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yearly_insights_parser-2025.12.21101922-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.6 kB
Release files / yearly_insights_parser-2025.12.21101922.tar.gz
| Download URL | yearly_insights_parser-2025.12.21101922.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f29d8d6be782f8c3b36651c48b015a1a051e4c33ba74de0d867a696457ed5d3
|
|
BLAKE2b-256 checksum How to use checksums |
df59dba429f4848c402fd44cb2269b62ced38878827fcfb7f8c96a09f3351df9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|
Release files / yearly_insights_parser-2025.12.21101922-py3-none-any.whl
| Download URL | yearly_insights_parser-2025.12.21101922-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14ca873e1d5826269e1471eca87c5dea336bde19905e5c695c9019eaaa38202b
|
|
BLAKE2b-256 checksum How to use checksums |
4470c1bab64b090f74aebdb37cd307e1d31b889f9b39586e553bab9b33260fbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.11
|