CtrlK
BlogDocsLog inGet started
Tessl Logo

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

75

Quality

94%

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

The canonical home for this skill is pulse in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

The body is a well-sequenced, highly actionable multi-phase research workflow with strong validation and error handling. Its main weakness is that the progressively-disclosed bundle files (references/ and scripts/) it points to are not present in the bundle.

Suggestions

Ship the referenced references/*.md and scripts/*.py files (research_pack_conventions.md, cross_platform_synthesis.md, parallel_execution_discipline.md, citation_tracker.py, time_window_calculator.py, topic_slug_generator.py) so the one-level-deep navigation actually resolves.

De-duplicate the platform-dominance rationale (Reddit=sentiment, HN=technical/builder, Web=breadth, X=breaking) — state it once and reference it from the per-phase sections instead of repeating it.

Tighten the 'why I'm asking' intake blocks to one line each; the forcing-question value is already evident from the question itself.

DimensionReasoningScore

Conciseness

The body is directive and mostly lean, but the platform-dominance rationale (Reddit=sentiment, HN=technical, etc.) recurs in Q4 and the phase sections, and the repeated 'why I'm asking' blocks add length that could be trimmed — efficient with minor over-explanation rather than fully tight.

4 / 5

Actionability

Provides real endpoints (reddit.com/search.json, hn.algolia.com/api/v1/), concrete query parameters, full script-invocation syntax (citation_tracker.py --action record_sent ...), and a copy-paste-ready X export import command, covering the common cases.

5 / 5

Workflow Clarity

Phases 0–4 are clearly sequenced with parallel/sequential discipline, explicit validation checkpoints (confirm response before next call, retry policy, 3-consecutive-failure stop), feedback loops, and a full error-handling table — satisfying the batch-operation validation requirement.

5 / 5

Progressive Disclosure

Clear section structure with well-signaled one-level-deep references to references/*.md and scripts/*.py, but the referenced references/ and scripts/ bundle directories are absent from the skill bundle, so the disclosed detail is not actually present to navigate to.

4 / 5

Total

18

/

20

Passed

Description

100%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.

The description is exemplary: third-person, concrete, comprehensive in trigger coverage, and fully answers both what and when. It is dense but every clause earns its place and none is pure fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'takes the pulse', 'forcing intake clarifies topic specificity, angle...time window, and platform scope', and 'returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis' — covering the workflow comprehensively rather than with vague language.

5 / 5

Completeness

Explicitly answers both what (multi-source recency research producing a synthesized briefing with citations, metrics, and pattern analysis) and when (a 'Use when...' clause with concrete trigger phrases and named use cases), matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers with synonym variations — 'pulse on [topic]', 'what's happening with', 'what are people saying about', 'current conversation about', 'take the pulse of', 'trending:', 'find me info on' — plus use-case synonyms like competitor research and sentiment analysis, which a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — cross-platform recency intelligence over a configurable window with specific platform list and distinctive 'pulse' trigger phrasing — making conflict with other skills minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 14 missing

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.