interview-writeup_skill

This skill helps sociologists craft publication-ready interview writeups by guiding methods drafting, findings structure, and evidence presentation.

14

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nealcaren/social-data-analysis --skill interview-writeup

  • SKILL.md6.0 KB

Overview

This skill helps sociologists draft and polish write-ups for qualitative interview research, focusing on argument-driven findings and defensible methods prose. It emphasizes narrative craft over formulaic quote display and produces publication-ready methods, findings, and a quality-check memo. It pairs well with an interview analysis output of organized quotes and participant profiles.

How this skill works

I guide users through intake, methods drafting, findings construction, and revision using clear workflows and technique guides. If you supply a quote database and participant profiles, I map quotes to claims, choose an archetype (Mechanism List, Comparative, Process), and draft subsections using an 8-step rubric and the Anchor-Echo pattern. I also evaluate drafts against concrete quality indicators and flag prohibited moves.

When to use it

  • Draft or revise a methods section for interview-based research
  • Structure findings as an argument-driven narrative rather than a theme list
  • Select and integrate quotes strategically (anchor and echoes)
  • Transform a theme catalog or code list into analytic subsections
  • Perform a quality check before submission to a journal or report

Best practices

  • State analytic claims before presenting quotes so quotes illustrate rather than discover claims
  • Build one anchor case in depth, then use brief echoes to show prevalence and variation
  • Name mechanisms—explain how processes work, not just what happens
  • Bound claims to your sample and report prevalence or limits transparently
  • Avoid stacking quotes; include only as much evidence as necessary for persuasion

Example use cases

  • Convert a coded quote database into a three-finding results section with roadmap and headings
  • Revise an existing findings draft to replace theme-listing with mechanism-focused subsections
  • Draft a transparent methods section describing sampling, protocol, and analysis procedures
  • Run a quality-check memo that highlights gaps, prohibited moves, and revision priorities
  • Integrate participant profiles into anchor case write-ups while minimizing recurrence

FAQ

Not necessarily—organized quote databases and participant profiles are sufficient; raw transcripts help but are not required if quotes and codes are reliable.

Can you produce full journal-ready text from brief notes?

Yes, if you provide a clear main argument, core findings, and representative quotes I can draft publication-ready methods and findings following the 8-step rubric.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational