Apply discourse analysis to examine how language constructs meaning, power relationships, and social reality in texts and communications. Use this skill when the user needs to analyze how a text frames an issue, uncover hidden assumptions in language, examine power dynamics in communication, or deconstruct media/corporate/political messaging — even if they say 'what's really being said here', 'how is this framing the issue', or 'analyze the language in this document'.
npx skills add https://github.com/asgard-ai-platform/skills --skill hum-discourse
Discourse analysis examines how language shapes (not just reflects) reality. It reveals how texts construct identities, power relationships, and social norms through word choice, framing, and what is left unsaid. Especially valuable for analyzing media, corporate communications, policy documents, and political speech.
IRON LAW: Language Constructs Reality, Not Just Describes It
The choice of words is never neutral. "Restructuring" vs "layoffs",
"enhanced interrogation" vs "torture", "undocumented workers" vs
"illegal aliens" — same events, different realities constructed.
Discourse analysis examines WHAT language does, not just what it says.
# Discourse Analysis: {Text/Document}
## Context
- Producer: {who created this text}
- Audience: {intended recipients}
- Purpose: {stated and unstated goals}
- Genre: {press release / policy doc / speech / ad}
## Framing Analysis
| Element | In the Text | Alternative Framing | Effect |
|---------|------------|-------------------|--------|
| {key term} | "{actual language}" | "{what could have been said}" | {how this shapes perception} |
## Subject Positions
- Agent (active): {who does things}
- Patient (passive): {who has things done to them}
- Absent: {who is not mentioned}
## Presuppositions
- {what the text assumes without stating}
## Power Analysis
- This framing benefits: {who}
- This framing disadvantages: {who}
## Key Findings
{What the discourse analysis reveals that a surface reading misses}
Scenario: Analyzing a tech company's layoff announcement
Text: "We are making the difficult decision to right-size our organization to better position ourselves for long-term growth."
| Element | Text | Alternative | Effect |
|---------|------|-------------|--------|
| "right-size" | Implies current size is wrong | "lay off 500 employees" | Euphemism hides human impact |
| "our organization" | Company as abstract entity | "our colleagues" | Removes personal connection to affected people |
| "difficult decision" | Positions management as suffering | "decision that will displace 500 families" | Redirects sympathy toward decision-makers |
| "long-term growth" | Forward-looking justification | No mention of what caused over-hiring | Skips accountability for the situation |
Subject positions: Management = agents making "difficult decisions" (sympathetic). Employees = completely absent as subjects. ✓
references/cda-framework.mdPrepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
> This skill generates, creates, or builds brand voice guidelines from source materials. It should be used when the user asks to "generate brand guidelines", "create a style guide", "extract brand voice", "create guidelines from calls", "consolidate brand materials", "analyze my sales calls for brand voice", "build a brand playbook from documents", "synthesize a voice and tone guide", or uploads brand documents, transcripts, or meeting recordings for brand analysis. Also triggers when the user has a discovery report and wants to convert it into actionable guidelines.
Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.
Share a Google Docs document with edit access and email collaborators the link.
> Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, Gmail attachments, or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal agreement.
Search across all connected sources in one query. Trigger with "find that doc about...", "what did we decide on...", "where was the conversation about...", or when looking for a decision, document, or discussion that could live in chat, email, cloud storage, or a project tracker.
Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this URL, process this source, read and file this source, batch ingest, ingest these sources.
Take asgard-ai-platform/hum-discourse from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.