abductive-analyst_skill

This skill guides abductive qualitative analysis, helping you generate novel theories from interview anomalies by applying theory-first reasoning.

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 abductive-analyst

  • SKILL.md11.3 KB

Overview

This skill guides researchers through abductive analysis of qualitative interview data following Timmermans & Tavory. It structures a theory-first, iterative workflow that surfaces surprises, develops alternative theoretical casings, and produces memos and publishable syntheses. The goal is to turn anomalies and puzzles in interviews into novel, defensible theoretical claims.

How this skill works

The agent leads you through six phases: theoretical preparation, familiarization and open coding, theoretical casing, anomaly and variation analysis, memo-driven theory development, and integration plus write-up. At each phase it prescribes concrete outputs (reports, codebooks, memos, drafts), pauses for your review, and recommends model types for different analytic tasks. It emphasizes systematic identification of surprises, iterative re-reading, and testing emerging claims against the full dataset.

When to use it

  • When you want a theory-driven qualitative analysis that privileges surprises over inductive generalization.
  • When you have interview transcripts ready and want a reproducible analytic workflow.
  • When you aim to generate middle-range theoretical claims from puzzling or contradictory data.
  • When preparing a publishable article that must show how data disrupts existing expectations.
  • When you need structured support for memoing, negative-case analysis, and rhetorical abduction.

Best practices

  • Start with extensive theoretical preparation: assemble map and compass theories before coding.
  • Flag and preserve context for every surprising excerpt; don’t smooth over contradictions.
  • Use multiple theoretical lenses deliberately—compare what each lens reveals and obscures.
  • Write iterative memos and treat writing as analysis: drafts often expose analytic gaps.
  • Pause between phases to review outputs with collaborators or advisors before proceeding.

Example use cases

  • A sociologist studying workplace emotion who finds interviewees describing unexpected pride in rule-breaking.
  • A health researcher exploring patient narratives where reported behaviors contradict clinical expectations.
  • A migration scholar encountering respondents whose experiences challenge dominant assimilation models.
  • A doctoral student preparing a theory-driven article by deriving a novel mechanism from puzzling cases.
  • A mixed-methods team needing a reproducible codebook and memo trail to defend interpretive claims.

FAQ

Yes: abductive analysis requires prior theoretical sensitivity so you can recognize surprises against clear expectations.

Can I iterate back to theory later?

Absolutely. The method is recursive: you revisit theory and data repeatedly as new puzzles and memos emerge.

What outputs will I get?

Phase-specific reports (theory synthesis, interview summaries, casings, anomaly catalog, memos) plus a final integration document and article-ready draft.

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