new-from-knowledge

Name: new-from-knowledge
Availability: InStock
Author: OgenticAI

Scan org-knowledge to propose Linear tickets for untracked decisions.

1|Updated May 10, 2026

Search Tags:#ticket generation #team decision tracking #Linear ticketing #org-knowledge integration #decision proposal

Ready to run

npx skills add https://github.com/OgenticAI/ogentic-audit --skill new-from-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-from-knowledge
Source: https://github.com/OgenticAI/ogentic-audit/tree/main/.claude/skills/new-from-knowledge
Command: npx skills add https://github.com/OgenticAI/ogentic-audit --skill new-from-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires orgknowledge, mcp, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies team decisions made without Linear tickets and suggests creating tickets for them, closing the gap between decision-making and tracking.

Core Features & Use Cases

Identifies Decisions: Scans org-knowledge for decisions not documented in Linear tickets.
Proposal Creation: Generates draft Linear tickets based on the identified decisions.
Operator Approval: Allows operators to review and approve proposed tickets before creation.
Use Case: Useful for ensuring that all decisions are tracked in Linear, improving project and task management.

Quick Start

Use the new-from-knowledge skill to propose tickets for untracked decisions.

Frequently Asked Questions about new-from-knowledge

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

FAQPage Schema

How do I create Linear tickets for team decisions that lack documentation?▼

To create Linear tickets for undocumented team decisions, this Skill scans org-knowledge for decision patterns and generates draft tickets. It cross-references existing Linear issues for de-duplication before proposing the new tickets for operator approval.

What is the best way to track team decisions in Linear automatically?▼

Tracking team decisions in Linear automatically is handled by scanning org-knowledge content to find decisions without tickets. The system proposes draft Linear issues, allowing operators to review and approve them before final creation.

Do I need an org-knowledge API to generate Linear tickets from past decisions?▼

Yes, you need the org-knowledge API available to generate Linear tickets from past decisions. The Skill requires this API for knowledge retrieval, MCP for feature flag checking and task scheduling, and Python for execution.

How does de-duplication work when proposing Linear tickets for untracked decisions?▼

De-duplication when proposing Linear tickets works by integrating with the Linear issue tracking system. The Skill cross-references identified org-knowledge decisions against existing Linear issues to prevent duplicate ticket creation.

Can I review proposed Linear tickets before they are actually created?▼

Yes, you can review proposed Linear tickets before creation through an operator approval step. The Skill generates draft tickets based on org-knowledge decisions and requires operator approval to finalize the creation in Linear.

Why are my team decisions not showing up as Linear ticket proposals?▼

Team decisions may not show up as Linear ticket proposals if the restricted feature flag context is inactive. Successful execution requires MCP for feature flag checking and a functional org-knowledge API to scan for matching decision patterns.