grad-agenda-setting
Apply agenda-setting theory (McCombs & Shaw) to analyze how media salience transfers to public perception. Use this skill when the user needs to study media influence on public opinion priorities, evaluate issue salience transfer across media and public agendas, or design communication strategies that leverage agenda-setting effects — even if they say 'why is everyone talking about this topic', 'how does media shape public priorities', or 'which issues get attention and why'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/grad-agenda-setting”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/grad-agenda-settingmetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
72 words · 480 chars — "Apply agenda-setting theory (McCombs & Shaw) to analyze how media salience trans…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 72 words.
Documentation present and substantive
Documentation present (SKILL.md, 617 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Agenda-Setting Theory
Overview
Agenda-setting theory posits that mass media may not tell people what to think, but powerfully influences what they think about. By selecting, emphasizing, and repeating certain issues, media transfers issue salience from the media agenda to the public agenda.
When to Use
Trigger conditions:
- Analyzing how media coverage shapes public issue priorities
- Evaluating the relationship between media attention and public concern
- Designing strategic communication to elevate issue salience
When NOT to use:
- When analyzing HOW people think about issues (use framing theory instead)
- When studying long-term worldview formation (use cultivation theory instead)
- When examining minority opinion suppression (use spiral of silence instead)
Assumptions
IRON LAW: Media May Not Tell People WHAT to Think, But It Tells Them WHAT TO THINK ABOUT
Issue salience is transferred from media to public agenda. The MORE
coverage an issue receives, the MORE important the public perceives it
to be — regardless of objective importance. This operates at two levels:
1. First level: OBJECT salience (which issues matter)
2. Second level: ATTRIBUTE salience (which aspects of issues matter)
Methodology
Step 1: Identify Agendas
Define the media agenda (content analysis of coverage frequency/prominence) and public agenda (survey data on "most important problem").
Step 2: Measure Salience
Quantify issue salience on both agendas. Media: column inches, airtime, front-page placement. Public: survey rankings, social media volume.
Step 3: Analyze Transfer
Examine the correlation between media salience and public salience over time. Account for time lag (typically 4-8 weeks for traditional media).
Step 4: Assess Contingent Conditions
Evaluate moderators: need for orientation (relevance + uncertainty), obtrusiveness of issues, media credibility, audience characteristics.
Output Format
# Agenda-Setting Analysis: {Issue/Context}
## Media Agenda
- Issues ranked by salience: {list with coverage metrics}
- Time period: {dates analyzed}
- Sources: {media outlets examined}
## Public Agenda
- Issues ranked by perceived importance: {survey/social data}
- Measurement method: {MIP survey, social media analysis, etc.}
## Salience Transfer
- Correlation: {media-public agenda correlation}
- Time lag: {observed lag period}
- Direction: {media→public, public→media, or intermedia}
## Moderating Factors
- Need for orientation: {high/low and why}
- Issue obtrusiveness: {obtrusive vs unobtrusive}
## Implications
{Strategic recommendations based on findings}
Gotchas
- Correlation ≠ causation: High media-public correlation doesn't prove media caused the salience shift — reverse agenda-setting (public→media) and real-world cues both exist.
- Obtrusive vs unobtrusive issues: Agenda-setting effects are STRONGER for unobtrusive issues (those people don't experience directly). For obtrusive issues, personal experience competes with media influence.
- Digital fragmentation: In fragmented media environments, there may be no single "media agenda" — different audiences consume different media with different agendas.
- Second-level conflation: Don't confuse attribute agenda-setting (which attributes are salient) with framing (how attributes are interpreted). They overlap but are theoretically distinct.
- Time lag varies: The optimal lag between media coverage and public opinion change varies by issue type, media type, and cultural context. There is no universal "correct" lag.
References
- For second-level and network agenda-setting models, see
references/advanced-models.md - For content analysis methodology, see
references/content-analysis.md
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/grad-agenda-setting