ta-framework-writer

ta-framework-writer is a skill for Claude Code, Codex from yipng05-max/-skills. It costs 104 tokens per session (1,565 once invoked), scanned A, original, MIT.

A writing tool that turns a thematic analysis theory framework into a paper section. Thematic analysis is a method for finding and interpreting patterns in qualitative data.

In plain words
What is it for?
Use it to write a theory-led framework chapter, a short theory-orientation section for data-led analysis, or a section using theory as a flexible lens.
Why use it?
It helps researchers explain why a theory fits their research question instead of producing a generic theory summary. It also adjusts the section's role and length to the chosen theory approach.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write a theory-led framework chapter, a short theory-orientation section for data-led analysis, or a section using theory as a flexible lens.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yipng05-max/-skills/ta-framework-writer
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add yipng05-max/-skills --skill ta-framework-writer
Clone the repo
git clone --depth 1 https://github.com/yipng05-max/-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ta-framework-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/yipng05-max/-skills/ta-framework-writer.svg)](https://agentmods.dev/skills/yipng05-max/-skills/ta-framework-writer)
Your own site
<a href="https://agentmods.dev/skills/yipng05-max/-skills/ta-framework-writer"><img src="https://agentmods.dev/badge/skills/yipng05-max/-skills/ta-framework-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,565 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.01565
Opus 5 $0.00052 $0.00783
Sonnet 5 $0.00021 $0.00313
Haiku 4.5 $0.00010 $0.00156

Measured 8d ago against content hash 0d7355878d57, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ta-framework-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ta-framework-writer/SKILL.md · 136 lines

How it starts

The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TA 理论框架章节写作

将理论框架转化为可直接放入论文的章节文字。 根据理论定位(A/B/C)生成不同形态的输出——位置不同、篇幅不同、承担的论证工作不同。

入口选择

启动时询问研究者:

你是否已完成 ta-framework-builder 的框架建构?

入口 A(已有框架文档):请提供 framework_[研究主题].md 的路径,或直接粘贴内容, 我将直接进入章节写作。

入口 B(尚未建构框架):我将先快速引导你确认框架要素(约5分钟),再进入写作。

入口 B 快速确认流程(精简版,不替代 ta-framework-builder)

⚠️ 如果在 ta-research-AFP 工作流中调用:理论定位(A/B/C)已在检查点 2 锁定,入口 B 不得重新询问或修改理论定位。若框架文档丢失,应请研究者重新提供 framework_[研究主题].md,而非重新建构框架。

仅在独立使用时收集以下最小信息:

  1. 理论定位(A/B/C)
  2. 选定的主理论(+ 辅助理论,如有)及选择理由(1–2句)
  3. 3–5个核心概念及其操作化定义
  4. 概念间关系的简要说明

根据理论定位生成对应章节

A 型:独立理论框架章节(理论驱动)

章节位置:在研究方法章节之前,文献综述之后 篇幅参考:1500–2500字(C刊)/ 2000–4000字(SSCI)

章节结构

一、[主理论名称]:核心命题与解释机制
  - 理论的核心关注是什么
  - 解释机制:通过什么逻辑解释现象(不只是"该理论认为……")
  - 理论的内部张力与局限(诚实呈现)

二、理论选择的依据
  - 为什么这个理论适合本研究
  - (如有辅助理论)两个理论如何分工与整合

三、核心概念界定
  - 逐一界定每个核心概念
  - 每个概念:来源定义 → 本研究的操作化含义 → 与其他概念的关系

四、理论框架对本研究的指导意义
  - 框架如何指导编码与主题命名
  - 在发现章节中,哪些主题预期与哪些理论概念对话

写作要求

  • 理论介绍不是教科书式的"理论综述",而是论证"为什么这个理论能解释我的研究问题"
  • 必须呈现理论的解释机制(causal mechanism),不能只堆砌理论观点
  • 核心概念界定必须回到原著,不能只引二手解读
  • 如果文献引用不确定真实性,必须标注"此引用需研究者自行核实"

B 型:理论取向简述(经验驱动,嵌入方法章节)

章节位置:在研究方法/方法论章节内,作为分析取向说明的一部分 篇幅参考:300–500字

内容

  1. 说明本研究采用经验驱动的归纳取向,理论是在主题涌现后才引入的
  2. 交代进入分析时的理论"留白"——研究者如何保持对数据的开放性
  3. 说明理论将在讨论章节中被召唤:届时用于解释和理解涌现的主题

写作要求

  • 语气要诚实——不要假装"完全没有理论预设"(任何研究都不可能),而是说明理论在分析中的角色是"事后解释"而非"事先框定"
  • 为讨论章节预留空间:此处不展开理论,只说明立场

C 型:理论取向说明(敏感性概念,嵌入方法章节)

章节位置:在研究方法/方法论章节内,数据收集和分析方法说明之前 篇幅参考:600–1000字

内容

  1. 说明本研究以[理论]为分析透镜,而非预设框架
  2. 点明 2–3 个作为"敏感性概念"的核心概念:
    • 每个概念的来源与基本含义(简短,不展开)
    • 它如何帮助研究者"看到"资料中的某些维度
    • 明确声明:这些概念是进入分析的透镜,不预设分析结论
  3. 说明理论将在讨论章节中深化:届时将发现与这些理论概念进行更充分的对话

写作要求

  • 区分"透镜"(sensitizing concept)和"框架"(theoretical framework)的差异,用语要准确
  • 不要在方法章节里展开全面的理论论证,那是讨论章节的工作
  • 保留分析的开放性:读者应能感受到研究者在进入资料时并没有把结论框死

写作过程中的质量检验

写完后,自动对输出做以下检查,并将结果告知研究者:

  1. 贴标签检验:是否只是提到了理论名称然后直接套用结论?(如有,指出哪个段落需要深化)
  2. 机制检验:是否说明了理论的解释机制,而不只是理论的结论?
  3. 引用真实性:涉及的文献引用是否有把握?标注存疑引用。
  4. A/B/C 一致性:章节的形态和位置说明是否与选定的理论定位一致?

Read the full file on GitHub · 136 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 136 lines · 104 tokens per session scan A 0d7355878d57

Subscribe to this mod's changes

ta-framework-writer is a skill published in the GitHub repository yipng05-max/-skills (284 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 1,565 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens