diskusi-skill

Interpret findings, compare literature, and clarify implications for discussion stage outputs.

Updated Dec 13, 2025
One-click install
npx skills add https://github.com/Posteriot/makalah-app --skill diskusi-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diskusi-skill
Source: https://github.com/Posteriot/makalah-app/tree/main/docs/skill-per-stage/skills/diskusi-skill
Command: npx skills add https://github.com/Posteriot/makalah-app --skill diskusi-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents discussion stage drift by guiding AI to interpret findings, compare them to literature, and surface implications tied to approved outputs.

Core Features & Use Cases

  • Context-aware interpretation: Reads approved hasil output, references, feedback, and living outline checklist status to keep the analysis aligned with project progress.
  • Literature comparison: Prompts focused comparisons so implications and limitations connect directly to cited sources.
  • Validation guardrails: Enforces stage-specific tool policies, ensures ringkasan storage, and waits for user confirmation before submitting.
  • Use Case: When currentStage equals diskusi, ask for an analytical discussion summarizing findings, theoretical/practical implications, and next-step recommendations.

Quick Start

Ask the diskusi skill to summarize findings, compare them with literature, and record implications and limitations.

Frequently Asked Questions about diskusi-skill

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

FAQPage Schema
How do I write an analytical discussion section comparing research findings with literature?

To write an analytical discussion, interpret findings, compare them to cited literature, and surface implications tied to approved outline progress. This prevents discussion drift by keeping summaries aligned with project references and feedback.

Can I track bibliography references automatically while generating a discussion stage summary?

Yes, bibliography tracking is handled via compileDaftarPustaka preview during the discussion stage. This tracks references while you interpret findings and formulate implications, ensuring citations connect directly to sources without premature submissions.

How do I enforce tool policies when searching for literature during the discussion stage?

Enforce tool policies by limiting external searches to google_search active mode. This constrains the discussion stage workflow to approved search parameters while generating analytical summaries and theoretical implications.

Do I need approved hasil output and an outline checklist before starting the discussion stage?

Yes, approved hasil output, references, feedback, and a living outline checklist are required inputs. This context-aware interpretation ensures your discussion analysis remains aligned with established project progress and approved outputs.

Why does my AI research discussion drift away from the approved outline progress?

Discussion drift occurs when analysis loses connection to approved outputs and feedback. Steer discussion stage outputs by enforcing validation guardrails, ensuring ringkasan storage, and waiting for user confirmation before final submissions.