CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-discourse

Research what people are actually saying about a topic in the last 30 days across Reddit, X / Twitter, YouTube, Hacker News, dev.to, Medium, and other public discourse platforms. API-free; uses WebSearch with platform-targeted site operators plus recency filters. Produces DISCOURSE.md (a structured brief) and JSON output the writer can consume. Complements blog-researcher (which focuses on authority sources) with a recency-and-engagement lens. Use when user says "blog discourse", "discourse research", "what are people saying about", "research what people are saying", "voice of customer", "social listening", "30-day research", "trend research", "what's the discussion on", "real-time research", "practitioner discourse", "/blog discourse".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable workflow document with strong sequencing, validation checkpoints, and a thoughtful untrusted-data security contract. Its main weaknesses are minor verbose asides and the absence of the referenced bundle files (notably the Python helper) that the workflow depends on.

Suggestions

Ship the referenced bundle files — at minimum scripts/discourse_research.py, references/research-quality.md, and references/synthesis-contract.md — so the executable workflow steps and the LAWs/trap-classes they cite actually exist.

Trim pedagogical asides that don't change agent behavior, e.g. the 'functionally harmless to leak ... but pedagogically correct' note on os.close(fd) and the 'This mirrors the WebFetch contract' cross-reference.

Confirm the cross-skill paths (skills/blog/references/..., agents/blog-researcher.md) resolve from this skill's install location, or rewrite them as bundle-relative paths so progressive-disclosure navigation does not break.

DimensionReasoningScore

Conciseness

Mostly efficient — phases, command table, JSON schema, and the security contract all earn their tokens — but a few asides could be trimmed, e.g. 'functionally harmless to leak in a short-lived subprocess but pedagogically correct' and 'This mirrors the WebFetch contract in agents/blog-researcher.md'.

4 / 5

Actionability

Provides copy-paste-ready commands (the tempfile.mkstemp one-liner, the full discourse_research.py invocation with flags) and a concrete result-item JSON schema, but the core scripts/discourse_research.py is referenced yet not present in the bundle, leaving a gap between instruction and executability.

4 / 5

Workflow Clarity

Clear Phase 0–5 sequence with explicit validation checkpoints (mandatory pre-flight trap checks with STOP conditions, untrusted-data snippet scanning, LAW verification before delivery), a decomposition checklist, and an error-handling section with feedback loops (reframe/widen, never overwrite silently).

5 / 5

Progressive Disclosure

Well-organized overview with clearly signaled one-level-deep references (research-quality.md, synthesis-contract.md, discourse_research.py), but none of the referenced files exist in the bundle, so the navigation structure is sound yet currently leads nowhere.

4 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states what the skill does and when to use it, with an unusually rich set of natural trigger phrases. The only weakness is minor overlap risk with sibling research skills on a few generic triggers.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'uses WebSearch with platform-targeted site operators plus recency filters', 'Produces DISCOURSE.md (a structured brief) and JSON output' — across an enumerated platform set, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' ('Research what people are actually saying... Produces DISCOURSE.md') and 'when' ('Use when user says...') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Lists a comprehensive set of natural trigger phrases users would say — 'what are people saying about', 'voice of customer', 'social listening', '30-day research', 'trend research', 'what's the discussion on', '/blog discourse' — covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Has a clear recency-and-engagement niche and explicitly distinguishes itself from blog-researcher ('Complements blog-researcher which focuses on authority sources'), but several broad research triggers ('trend research', 'real-time research') carry minor overlap risk with the other blog-* research skills it lists.

4 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

13

/

16

Passed

Repository
AgriciDaniel/claude-blog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.