Repository inventory

zircote/sigint

Skills indexed from this repository, with install-style signals scoped to the repo.
5 skills15 GitHub stars0 weekly installsGitHubOwner profile

Overview

This skill helps you turn research and analysis into clear, decision-ready reports for executives, product teams, investors, and analysts. It provides templates, structure patterns, visualization guidance, and a quality checklist so every deliverable is scannable, evidence-backed, and actionable. Use it to produce executive briefs, research summaries, full reports, or data appendices.

How this skill works

The skill inspects your research objectives and data, then recommends an appropriate report type and template based on audience and depth required. It enforces a pyramid structure: lead with the conclusion, follow with supporting evidence, and push detailed methods to an appendix. It also suggests chart types, table formatting, and wording conventions (active voice, quantified claims, calibrated hedges).

When to use it

  • When asked to write a report, executive summary, or research brief
  • When presenting findings to C-suite, investors, or product teams
  • When you need a standardized report structure or templates
  • When preparing visuals or tables for a market analysis
  • When converting findings into prioritized recommendations and risks

Best practices

  • Start with a one-paragraph executive summary that states context, 3–5 key findings, a primary recommendation, and one critical risk
  • Use the pyramid structure: conclusion first, then supporting points, then details in appendix
  • Quantify claims and label confidence (e.g., “data suggests”, “evidence indicates”, “analysis confirms”)
  • Prioritize and number recommendations; for each, state what, why, how, and risk
  • Choose visualizations by data type (bar for comparison, line for trends, scatter for relationships) and label axes, units, and highlights

Example use cases

  • Create a 1-page executive brief for board decision on market entry
  • Produce a 3–5 page research summary for VPs with multiple recommendations and evidence
  • Draft a 10–30 page full report including methodology and detailed tables for analysts
  • Assemble an appendix/data pack with raw tables and source notes for audits or deep dives
  • Convert research findings into prioritized GitHub issues or implementation tasks

FAQ

An executive summary that states context, key findings, a primary recommendation, and any critical caveats.

How long should an executive brief be?

One paragraph to one page; aim for a 5-minute read that highlights only the most important findings and the single recommended action.

5 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational