Help us improve
Share bugs, ideas, or general feedback.
From decipon
Generate formal NCI analysis report in JSON or Markdown format for sharing and archiving
npx claudepluginhub synaptiai/synapti-marketplace --plugin deciponHow this command is triggered — by the user, by Claude, or both
Slash command
/decipon:reportThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Generate NCI Report Generate formal NCI analysis report in JSON or Markdown format. ## Usage ## Arguments - `$ARGUMENTS`: Content to analyze plus optional flags - Content: URL, file path, or text - `--format`: Output format (default: markdown) - `--output`: Save to file (optional) ## Purpose Generate a formal, shareable NCI analysis report: - Complete 20-category breakdown - Dual perspectives with confidence - Structured format for sharing/archiving - Machine-readable (JSON) or human-readable (Markdown) ## Workflow 1. **Parse Arguments** - Extract content from flags ...
/reportGenerates a self-contained HTML report with per-file scores, score trends, cross-component graphs, vocabulary maps, drift candidates, and findings. Opens directly via file:// with no server or build step.
/generate-reportGenerates advanced SEO and GEO analysis reports for a domain, supporting executive-summary, technical-analysis, geo-comprehensive, competitive-intelligence types and Markdown, HTML, PDF, JSON, Excel formats.
/reportGenerates reports on task execution, progress, and metrics including executive summaries, sprint burndowns, standups, performance analysis, and dependencies.
/reportGenerates reports on task execution, progress, and metrics including executive summaries, sprint burndowns, standups, performance analysis, and dependencies.
/reportGenerates formatted terminal report of AI experiments with stats, top tools, rating distribution, tags, recent activity, and latest details. Supports optional tool, tag, days, rating filters.
/reportGenerates a submission-ready bug bounty report in HackerOne, Bugcrowd, Intigriti, or Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation.
Share bugs, ideas, or general feedback.
Generate formal NCI analysis report in JSON or Markdown format.
/decipon:report <URL or text> [--format json|markdown] [--output filename]
$ARGUMENTS: Content to analyze plus optional flags
--format: Output format (default: markdown)--output: Save to file (optional)Generate a formal, shareable NCI analysis report:
Parse Arguments
Perform Full Analysis
Generate Perspectives
Format Report
Output/Save
--output specified# NCI Analysis Report
**Generated**: [ISO timestamp]
**Protocol Version**: 1.0
**Content Source**: [URL or "Direct input"]
---
## Executive Summary
**Overall Score**: 72/100 [!!!]
**Confidence**: 82%
**Risk Level**: HIGH
**Key Finding**: This content exhibits strong manipulation patterns,
particularly in emotional manipulation and missing information dimensions.
---
## Composite Factor Scores
### Emotional Manipulation: 4.2/5
Confidence: 85%
| Category | Score | Evidence |
|----------|-------|----------|
| Base Emotional | 4 | [Evidence] |
| Urgent Action | 5 | [Evidence] |
| Novelty | 4 | [Evidence] |
| Repetition | 4 | [Evidence] |
| Manufactured Outrage | 4 | [Evidence] |
### Suspicious Timing: 4.7/5
[Continue for each composite...]
---
## Perspectives
### Manipulative Interpretation
**Confidence**: 80%
[Full manipulative interpretation...]
### Legitimate Interpretation
**Confidence**: 55%
[Full legitimate interpretation...]
---
## Detailed Category Analysis
[All 20 categories with full evidence...]
---
## Methodology
This analysis follows NCI Protocol v1.0:
- Pattern-based detection (not truth-based)
- 20 manipulation indicators across 5 dimensions
- Weighted scoring with confidence metrics
- Dual perspective generation
---
## Appendix: Raw Scores
[JSON-formatted raw data for programmatic use]
{
"nci_report": {
"version": "1.0",
"generated_at": "2025-01-15T10:30:00Z",
"content_metadata": {
"source": "https://example.com/article",
"type": "url",
"word_count": 1250,
"fetch_date": "2025-01-15T10:29:55Z"
},
"score": {
"overall": 72,
"confidence": 0.82,
"severity": "HIGH",
"severity_indicator": "[!!!]"
},
"composite_factors": {
"emotional_manipulation": {
"value": 4.2,
"confidence": 0.85,
"categories": {
"emotional_manipulation_base": {
"score": 4,
"evidence": "Fear vocabulary: 'devastating', 'threat'",
"confidence": "HIGH"
}
}
}
},
"perspectives": {
"manipulative": {
"summary": "...",
"confidence": 0.80,
"key_techniques": ["...", "...", "..."],
"likely_intent": "...",
"beneficiaries": ["..."]
},
"legitimate": {
"summary": "...",
"confidence": 0.55,
"supporting_factors": ["...", "...", "..."],
"genuine_concerns": "...",
"explanatory_context": "..."
}
},
"methodology": {
"protocol": "NCI Protocol",
"version": "1.0",
"approach": "Pattern-based manipulation detection",
"categories_scored": 20,
"composite_factors": 5
}
}
}
Markdown report to console:
/decipon:report https://example.com/article
JSON report to console:
/decipon:report https://example.com/article --format json
Save markdown report to file:
/decipon:report https://example.com/article --output nci-analysis.md
Save JSON report to file:
/decipon:report https://example.com/article --format json --output analysis.json
When generating formal reports, consider:
/deep-research first for claims verification| Scenario | Recommended Format |
|---|---|
| Sharing with colleagues | Markdown |
| Archiving for records | JSON |
| Integration with tools | JSON |
| Presentation/documentation | Markdown |
| Comparative analysis | JSON |
| Command | Output | Use Case |
|---|---|---|
/decipon:score | Quick score only | Triage |
/decipon:analyze | Console report | Investigation |
/decipon:report | Formal document | Sharing/archiving |
Use the AskUserQuestion tool when:
Missing content:
User: /report
→ Use AskUserQuestion tool:
Question: "What content would you like me to generate a report for?"
Options:
- "Provide a URL to analyze"
- "Paste text content"
- "Generate report from previous analysis"
Format selection:
User: /report https://example.com/article
→ Use AskUserQuestion tool:
Question: "What format would you like for the report?"
Options:
- "Markdown (human-readable)" (Recommended)
- "JSON (machine-readable, for tools)"
- "Both formats"
Output destination:
User: /report https://example.com/article --format json
→ Use AskUserQuestion tool:
Question: "Where should I save the report?"
Options:
- "Display in console only"
- "Save to file (specify filename)"
- "Both display and save"
Report customization:
After generating initial report
→ Use AskUserQuestion tool:
Question: "Report ready. Any customizations needed?"
Options:
- "Include claim verification results"
- "Add executive summary for stakeholders"
- "Report is complete as-is"