feedback-loops

Coordinate feedback loops to improve CTI quality across production workflows.

15|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Liberty91LTD/cti-skills --skill feedback-loops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-loops
Source: https://github.com/Liberty91LTD/cti-skills/tree/main/skills/feedback-loops
Command: npx skills add https://github.com/Liberty91LTD/cti-skills --skill feedback-loops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feedback is Phase 6 of the CTI Hyperloop. Without it, the cycle is open-ended and quality degrades over time.

Core Features & Use Cases

  • Consumer feedback collection and evaluation
  • Source quality tracking across intelligence products
  • Analyst retrospectives to update SOPs and capture lessons
  • Detection-feedback integration to sharpen future analyses

Quick Start

Instruct the system to initiate a feedback loop for a CTI project and capture the first retrospective entry.

Frequently Asked Questions about feedback-loops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a CTI feedback loop to improve intelligence quality?

Initiating a CTI feedback loop involves coordinating consumer feedback collection, running analyst retrospectives, and tracking source quality to enforce governance and capture lessons learned for continuous improvement.

What is a CTI retrospective and how does it update intelligence workflows?

A CTI retrospective is an analyst review session that captures lessons learned to update standard operating procedures, ensuring intelligence production and detection workflows continuously improve over time.

Can I use this to track source reliability across intelligence products?

Yes, source quality tracking is a core feature that evaluates source reliability across intelligence products, enforcing governance to ensure feedback collection actively guides future CTI work.

What is the best way to integrate detection feedback into CTI production?

The best way to integrate detection feedback is to coordinate it within your CTI workflows, applying retrospective lessons and source-quality tracking to sharpen future analyses and enforce governance.

Why does CTI quality degrade over time without a feedback loop?

CTI quality degrades over time without a feedback loop because the intelligence cycle becomes open-ended, lacking the consumer feedback and analyst retrospectives necessary to enforce governance and capture lessons learned.

Do I need any specific dependencies to run CTI feedback governance?

No specific dependencies are required to run CTI feedback governance, as the skill independently coordinates feedback collection, source reliability evaluation, and retrospective tracking within your workflows.