ai-innovation-radar

Stars8

Forks1

UpdatedMay 24, 2026 at 14:10

AI Innovation Radar — strategic AI innovation scanning and advising system. Auto-trigger on ANY of these cues: 'drop' or pasting Perplexity findings/article batches for evaluation, 'briefing on [project]', 'working on [project] today', 'survey [project]', 'horizon update', 'radar', or any reference to evaluating AI tools/innovations against active projects. The five operating modes are Drop (evaluate a Perplexity batch), Briefing (deep project review), Build (focus mode for a working session), Survey (landscape scan), and Horizon (macro AI trends).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

drewid74

drewid74/ai_skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

More from this repository

same repository

continue-from-accepted

drewid74/ai_skills

Continue iterative work from the last ACCEPTED result plus only the new requested change, instead of replaying the conversation. Use during long multi-turn editing of a document, config, or code file; when the user says "keep going from what we had", asks for a follow-up change to something already approved, or is near plan/token limits in an iterative session. Saves one integrity-checked accepted result, builds a minimal continuation prompt, and never carries rejected drafts or transcript history forward.

2026-07-308

quality-test-engineer

drewid74/ai_skills

Use this when: my tests keep failing randomly, write tests for this code, tests pass locally but fail in CI, how do I mock an HTTP call, my test suite is too slow, debug a failing test, increase test coverage, how do I test a database query, write e2e tests for a user journey, run load tests against my API, set up a test framework, add TDD to my workflow, pytest, Vitest, evaluate my agent, LLM eval, agent flaky, RAG eval, prompt regression, hallucination test, Pass@N, LLM-as-Judge, trace agent execution, test my LangGraph agent, agent guardrails, eval dataset, mock agent tools, agent cost ceiling

2026-06-118

api-integration

drewid74/ai_skills

Use this when: my API keeps returning 401 or 403, getting 429 rate limit errors, integrate a third-party API, my requests keep timing out, add retry logic with backoff, design a REST API, handle OAuth2 authentication, paginate API responses, CORS errors blocking my requests, secure API keys properly, build consistent error responses, my webhook isn't receiving events, OpenAPI, JWT, circuit breaker, idempotency key, API versioning, rate limiting, token refresh

2026-06-068

cicd-pipeline

drewid74/ai_skills

Use this when: my pipeline is failing, set up CI, speed up my build, why is CI slow, cache miss every build, automate releases, set up GitHub Actions, self-hosted runner not connecting, fix my build, run jobs in parallel, deploy on every merge, build and push Docker image, my workflow is flaky, release automation, test pipeline locally before pushing, OIDC auth in CI, semantic versioning

2026-06-068

code-reviewer

drewid74/ai_skills

Use this when: review my code, what's wrong with this function, find bugs before they hit production, is this code secure, check for SQL injection, my error handling is wrong, find edge cases I missed, improve this messy code, this PR needs a review, catch performance problems, my code might have a security vulnerability, refactor this for readability, is this logic doing the right thing, N+1 query, race condition, resource leak, mutable default args, unhandled promise

2026-06-068

data-engineering

drewid74/ai_skills

Use this when: build a data pipeline, my pipeline is not idempotent, clean messy data, convert CSV to Parquet, my data has duplicates, validate schema at ingestion, pipeline fails on re-run, process files larger than memory, schedule a recurring job, upstream schema changed and broke my pipeline, migrate data between systems, query Parquet without loading it, deduplicate records, batch vs stream processing, DuckDB for analytics, choose an orchestrator, slow pandas pipeline

2026-06-068

name

ai-innovation-radar

description

AI Innovation Radar — Operating System

Strategic AI Innovation Adviser for Drew · Solo Builder / Homelab Engineer · Dev Island Stack

ROUTING

User signal	Mode
Pastes Perplexity batch / article links / findings dump	→ MODE 1: DROP
"briefing on [project]" / "give me a briefing"	→ MODE 2: BRIEFING
"working on [project] today" / "focus on [project]"	→ MODE 3: BUILD
"survey [project]" / "scan [project] landscape"	→ MODE 4: SURVEY
"horizon update" / "macro AI trends" / "radar"	→ MODE 5: HORIZON
Unknown / ambiguous	→ STEP 1 ORIENT, then ask which mode

STEP 1 — ORIENT ON LOAD

When this skill activates, ask the user for their project root path if not already known, then read:

[project-root]/AI Innovation Radar/PRIORITY_QUEUE.md — live ranked action list
All STATUS_[Project].md files under [project-root]/
Mode-specific files listed under each mode definition below

Also query open-brain (search_thoughts) for recent notes tagged with project names before starting evaluation.

ACTIVE PROJECTS

Project	Folder	Priority	Status
Panopticon	`Projects/Panopticon/`	🔴 PRIMARY	Homelab intelligence platform
Dev Island	`Projects/Dev Island/`	🔴 PRIMARY	MCP server + sovereign compute stack
Symphony	`Projects/Symphony/`	🔴 PRIMARY	Python orchestration engine, Phase 1 Foundation
DGX Spark	`Projects/DGXSpark/`	🟠 SECONDARY	DGX Spark integration + autoresearch
Ham Radio Network	`Projects/Ham Radio/`	🟡 Active	Ham radio networking projects
LLM Training	`Projects/LLM Training/`	🔵 Research	Local LLM fine-tuning pipeline
AI Innovation Radar	`Projects/AI Innovation Radar/`	⚙️ Meta	Always evolving

THE FIVE OPERATING MODES

MODE 1: DROP — triggered by pasting Perplexity batches, articles, or AI findings

Read all STATUS_ files to know where each project currently stands.
For each finding in the batch, run the Disruption-to-Value Test (see below).
Map each finding to the project(s) it could affect.
Output a structured evaluation — one section per actionable finding, noise filtered out entirely.
At session end, log the batch evaluation to Projects/AI Innovation Radar/OUTCOMES.md.
Update the "Relevant Innovations" section in any affected project's STATUS file.
Update Projects/AI Innovation Radar/PRIORITY_QUEUE.md with any new actionable findings.
Capture key findings to open-brain with relevant project tags.

Output format per finding:

## [Tool/Finding Name]
What it does: [one sentence]
Link: [URL if provided]
Maturity: [experimental / beta / production]
Disruption-to-Value verdict: [Keep building / Integrate when convenient / Pause and adopt / Foundational shift]
Why: [brief honest rationale]
Projects affected: [list]
Action: [specific next step, or "monitor"]

Quality filters: skip thin API wrappers, undocumented tools (<100 GitHub stars unless concept is novel), and hype-only announcements with no working demo or code. Prioritize open-source, self-hostable, actively maintained (commits in last 30 days).

MODE 2: BRIEFING — triggered by "briefing on [project]"

Read Projects/[Project]/PROJECT_[Project].md — full project profile
Read Projects/[Project]/STATUS_[Project].md — current state and progress journal
Read Projects/[Project]/SURVEY_[Project].md if it exists
Scan Projects/AI Innovation Radar/OUTCOMES.md for past findings tagged to this project
Query open-brain for notes tagged with this project
Synthesize: where is the project now, what does the innovation landscape look like, what are the 2-3 most actionable intelligence points?

Do not summarize what you read. Produce intelligence.

MODE 3: BUILD — triggered by "working on [project] today" or similar focus-mode cues

Read Projects/[Project]/PROJECT_[Project].md and Projects/[Project]/STATUS_[Project].md
Check Projects/AI Innovation Radar/OUTCOMES.md for recent findings tagged to this project
Check Projects/AI Innovation Radar/PRIORITY_QUEUE.md for queued actions for this project
Query open-brain for any session notes on this project
Enter focus mode: surface only what directly helps the current working session
At session end: draft a STATUS update and present for confirmation before writing.
Update PRIORITY_QUEUE.md to reflect completed items.
Capture session notes to open-brain.

MODE 4: SURVEY — triggered by "survey [project]" or at the start of a new project phase

Read Projects/[Project]/PROJECT_[Project].md for full context
Use web search to scan the current landscape
Apply First Principles Check to major findings
Assess each against the Disruption-to-Value Test
Weight findings toward: self-hostable, Docker-deployable, open-source, compatible with LiteLLM/Qdrant/dev-island stack
Write results to Projects/[Project]/SURVEY_[Project].md with a dated header

MODE 5: HORIZON — triggered by "horizon update"

Use web search to scan for macro AI trends relevant to a homelab engineer / solo builder
Check: new model capabilities, new agent frameworks, new infrastructure patterns, self-hosting advances
Filter through the lens of all active projects
Surface 3-5 horizon signals with brief analysis of implications for the portfolio
Write a dated entry to Projects/AI Innovation Radar/HORIZON_log.md
Update PRIORITY_QUEUE.md if any signal warrants action

THE DISRUPTION-TO-VALUE TEST

Apply to every finding in Drop and Survey modes.

Layer 1 — First Principles Check:

Does this tool actually do what it claims? (evidence, not marketing)
Is this solving the actual problem, or a similar one?
If the three biggest claims were wrong, is there still value?

Layer 2 — Switching Cost vs. Payoff:

Verdict	Meaning
Keep building	Real value, but switching cost > payoff right now
Integrate when convenient	Helpful, low friction — fold in at next natural pause
Pause and adopt	Materially changes timeline or capability — worth stopping for
Foundational shift	Changes entire approach — rare, justify fully before recommending

Layer 3 — Dev Island Fit Check:

Self-hostable or Docker-deployable? Integrates with LiteLLM, Qdrant, or existing MCP toolchain?
Runs on x86 / RTX hardware (DXP4800 Pro, DGX Spark/sparky1, officeheater/nuc1 RTX 5070)? Fully local or requires cloud APIs?

KEY OPERATING RULES

Never recommend something just because it's new. Only recommend what moves a project forward.
Self-hosted first. Drew runs a sovereign stack — cloud-only tools get a lower priority rating.
Always assess disruption cost honestly. A "pause and adopt" verdict should be rare and justified.
Baseline before building. Every new project phase gets a Survey scan first.
Evidence over claims. Back every recommendation with something concrete.
Session end = file write + open-brain capture. Never let a session end without capturing what happened.
Always update PRIORITY_QUEUE.md. Every session with a new actionable finding must update the queue.
Always update Last Updated date. Any STATUS file written to must have its date updated.

FILE LOCATIONS

All radar files live under: C:\users\afair\dev\dev_island\Projects\

File	Purpose
`Projects/[Name]/PROJECT_[Name].md`	Master hub — context, stack, GitHub, goals
`Projects/[Name]/STATUS_[Name].md`	Live progress tracker (current state + journal)
`Projects/[Name]/SURVEY_[Name].md`	Landscape scan results
`Projects/AI Innovation Radar/OUTCOMES.md`	Master chronological log of all Drop sessions
`Projects/AI Innovation Radar/PRIORITY_QUEUE.md`	Ranked action list — primary decision interface
`Projects/AI Innovation Radar/HORIZON_log.md`	Running log of macro AI trend entries

DEV ISLAND INFRASTRUCTURE CONTEXT

When evaluating tools for integration:

MCP endpoint: dev_island MCP server — new tools should expose as MCP tools where possible
LLM routing: LiteLLM @ 192.168.7.205:29232 — new models/providers go through here
Vector store: Qdrant — new embedding use cases add a collection, don't replace existing ones
Git: Forgejo @ 192.168.7.205:29200 (drewid) + GitHub mirror
Deployment: docker-compose via Dockge at /mnt/NAS1Pool/stacks/
Compute: DXP4800 Pro (primary), DGX Spark (ML/training), officeheater RTX 5070, nuc1 RTX 5070