tyrealq/q-skills/q-intro

Claude Code and agent skill by tyrealq/q-skills

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Draft or refine introduction sections for academic manuscripts from phenomenon to theory to contribution. Use for writing introductions, literature framing, or research question development.

Install

npx vskill@latest install tyrealq/q-skills/q-intro

SKILL.md

Q-Intro

Draft and refine introduction sections for academic manuscripts. Supports interview-based drafting from scratch and diagnostic refinement of existing drafts.

References

  • references/introduction_template.md — structural guidance (draft dynamically, not verbatim)
  • references/interview_questions.md — interview protocol and refinement diagnostic
  • ../references/apa_style_guide.md — APA formatting, numbers, notation, formulas

Core Principles

  • Narrative prose; no bullet points, em-dashes, or standalone introductory paragraphs
  • Prefer 3-12 sentence paragraphs; each paragraph has one clear through-line
  • Trace a single narrative arc through the literature, grounded in the target discipline first
  • Introduce theoretical frameworks as the resolution to a need established in the preceding paragraph
  • Bridge every paragraph transition explicitly: each opening resolves or extends the prior paragraph's conclusion
  • Design research questions with clear scope progression (e.g., descriptive, relational, conditional)
  • Enumerate contributions with parallel structure; include a brief roadmap at conclusion

Argumentative Architecture

The templates describe what goes where; this section describes why and how paragraphs connect.

Paragraph Roles

A full introduction is typically 3 to 5 paragraphs; P1 to P5 may combine or split depending on venue length.

P1 (Phenomenon and Stakes): Establish the broader trend, signal the specific context, end with what is at risk or unknown. The final sentence should implicitly raise a question P2 will address.

P2 (Literature and Gaps): Begin from the target discipline's core traditions. Progress outward as the discipline's tools prove insufficient. Reframe the central question. Let gaps emerge as consequences of the trajectory, not disconnected items.

P3 (Theory, Study, and RQs): Open with a bridge resolving P2's gaps. Introduce the primary framework as the answer to P2's question. If using a complementary framework, explain what dimension it captures that the primary framework alone cannot. Describe the empirical context and justify its selection. State research questions in progressive scope with a brief methods preview.

P4 (Contributions): Enumerate theoretical, methodological, and empirical contributions. Signal applicability beyond the immediate context.

P5 (Roadmap): Brief orientation to remaining sections.

Bridge Patterns
  • P1 to P2: stakes or implicit question; P2 opens by grounding in the discipline's response
  • P2 to P3: gaps that constrain understanding; P3 states what is needed to address them
  • P3 to P4: methods preview; P4 opens with contributions
  • P4 to P5: final contribution; P5 opens with roadmap
Within-Paragraph Logic

Literature streams enter because the previous stream raised a question it cannot answer. Gaps feel like inevitable consequences of the trajectory. The theoretical framework is introduced as the resolution to a problem, not as background information. Key variable terms should capture the full dimensionality of what is being studied.

Workflow

StepActionReference
1Interview: begin with target venue to anchor disciplinary groundingreferences/interview_questions.md
2Draft the five-component introductionreferences/introduction_template.md
3Tighten: vary sentence length, cut filler, favor direct subject-verb openingsCore Principles above
4Refinement (existing drafts): run diagnostic, then revise per Architecturereferences/interview_questions.md (final section)

Scope

Include: Phenomenon contextualization, prior literature and gaps (narrative arc), theoretical framework (motivated), research questions (progressive scope) with brief method preview, contributions, roadmap.

When a standalone lit review exists: Compress the intro's literature to 1-2 sentences per stream with parenthetical citations. Introduce theory by stating what it does, not its full definition. Place concrete examples in the lit review. Integrate gaps as narrative consequences, not enumerated lists.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/tyrealq/q-skills/q-intro/badge)](https://verified-skill.com/skills/tyrealq/q-skills/q-intro)

Something wrong with this skill or its page? Tell us.