po4yka/llm-wiki-skills / skills/llm-wiki-news-radar
llm-wiki-news-radar
VerifiedFind and summarize fresh news, releases, papers, repositories, standards, and technologies related to LLM-Wiki, wiki memory, OpenWiki, Agent Skills, agent memory, RAG/GraphRAG, local-first knowledge tools, and coding-agent knowledge workflows. Use when the user asks for latest/current/recent ecosystem updates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.1 KB |
SKILL.md
View on GitHub---
name: llm-wiki-news-radar
description: Find and summarize fresh news, releases, papers, repositories, standards, and technologies related to LLM-Wiki, wiki memory, OpenWiki, Agent Skills, agent memory, RAG/GraphRAG, local-first knowledge tools, and coding-agent knowledge workflows. Use when the user asks for latest/current/recent ecosystem updates.
license: MIT
compatibility: Designed for Agent Skills-compatible coding agents with web browsing/search. Must browse and cite fresh sources for current claims.
metadata:
author: po4yka
version: "1.0.0"
install_scope: self-contained
---
# LLM-Wiki News Radar
## Goal
Produce a current, source-cited ecosystem update for LLM-Wiki and adjacent technologies.
## When to use
- The user asks about the latest, current, or recent state of LLM-Wiki, wiki memory, Agent Skills, RAG/GraphRAG, or related coding-agent knowledge tooling.
- The user asks "what changed" in these areas since a specific date or event.
- The user wants a source-cited digest of new releases, papers, tools, or standards before adopting them.
- Not for general questions that do not need freshness checking (use a vault-query skill instead).
## Mandatory freshness rule
Always browse. Do not answer current-state questions from memory.
Use absolute dates in the answer, especially when the user says latest, recent, today, this week, this month or current.
## Watch areas
Search across:
- LLM-Wiki / wiki memory / OpenWiki;
- LangChain, DeepAgents and related wiki-memory projects;
- Karpathy-style LLM-Wiki discussions;
- Agent Skills, skills.sh, Claude Code, Codex, Cursor, OpenCode;
- Obsidian/local-first knowledge workflows;
- qmd or local hybrid retrieval;
- RAG, GraphRAG, LightRAG, HippoRAG and agent-native retrieval;
- provenance, anti-slop, context poisoning, memory benchmarks;
- arXiv papers and benchmark releases;
- GitHub repos and release notes.
## Inputs
- The topic or watch area(s) to focus the search on; defaults to the full watch-area list above.
- The time window to cover (last 7 days, last 30 days, last 90 days, since a known event, or general landscape); infer or ask if not given.
- Optional: an LLM-Wiki vault path, if the result should be saved via the file-back step.
## Procedure
### 1. Set the time window
Infer or ask for the window:
- last 7 days;
- last 30 days;
- last 90 days;
- since a known event;
- general current landscape.
If no window is given, default to the last 90 days plus any major still-relevant baseline sources.
### 2. Search diverse sources
Use at least three source families when possible:
- official docs/blogs/release notes;
- GitHub repositories/releases/issues;
- papers/preprints;
- independent analysis or community discussions.
Prefer primary sources for technical claims.
### 3. Classify findings
Group updates by type:
| Type | Examples |
| --- | --- |
| `release` | CLI, library, plugin, agent feature, skill format update |
| `paper` | benchmark, architecture, retrieval/memory algorithm |
| `tool` | new repo or major implementation change |
| `standard` | Agent Skills, AGENTS.md, memory/tool interface conventions |
| `risk` | data loss, stale maintenance, privacy, provenance gap |
| `market-signal` | major vendor adoption, large ecosystem shift |
### 4. Evaluate relevance
For each important item, answer:
- What changed?
- Why does it matter for LLM-Wiki users?
- Who should care: personal user, team, product builder, researcher?
- Does it change a previous recommendation?
- What needs verification before adoption?
### 5. Output
```markdown
## Current as of YYYY-MM-DD
## Executive summary
## Major updates
## New or changed tools
## New papers / benchmarks
## Standards and agent ecosystem
## Risks and warnings
## What I would change in an LLM-Wiki setup now
## Sources checked
```
## Output
A single Markdown digest following the section template above (Current as of / Executive summary / Major updates / New or changed tools / New papers / Standards / Risks / Sources checked), grouped by the classification types from step 3, with every current-state claim carrying an inline citation to the source that supports it. When run inside an LLM-Wiki vault, the digest may additionally be offered for file-back as described below.
## Citation rules
- Cite every factual current-state claim.
- Do not cite a source for a claim it does not support.
- Do not group all citations at the end.
- Use primary sources for install commands, APIs, release status and licenses.
## Optional file-back
If working inside an LLM-Wiki vault, offer to save the update as:
```text
wiki/queries/YYYY-MM-DD-llm-wiki-news-radar.md
```
Mark it `status: draft` and `stale_after` within 30-90 days.
## Safety gates
- Never state a current-state fact (release status, version, maintenance status, pricing) without having browsed and cited a source for it.
- Do not fabricate dates, version numbers, or adoption claims; mark anything unverified as such instead of guessing.
- File-back into the vault is optional and report-only until the user confirms; never overwrite an existing wiki page.
- Surface stale, unmaintained, or low-provenance projects under the `risk` category rather than recommending them silently.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |