Name: push-by-techulus
Rating: 60 (1 reviews)
Author: membranedev

push-by-techulus

Push by Techulus integration. Manage data, records, and automate workflows. Use when the user wants to interact with Push by Techulus data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/push-by-techulus/SKILL.md

Quality

Content

82%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 strong, action-oriented integration guide dominated by executable commands and a clear connect→search→run workflow with state-based validation checkpoints. Its main weaknesses are minor: a little soft padding and 'Step 2' references to unlabeled steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, leading with executable commands and a flag table rather than concept explanation; only minor padding remains (e.g. 'so you can focus on the integration logic rather than auth plumbing' and the opening product blurb), fitting the 'efficient, minor over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage — install, login, connection ensure/get with --wait, action list/run with --input JSON, and the proxy request flags table — covering the common cases with fully executable guidance, matching the top anchor.	5 / 5
Workflow Clarity	The connect→poll→search→run sequence is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), but 'skip to Step 2' references steps that are never explicitly numbered, a minor gap keeping it below the fully-checkpointed 5.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers with an appropriate one-level external reference (the official docs URL) and no bundle-file indirection; it is appropriately self-contained for a medium-length skill, though a few dense blocks (connection-state handling, the proxy flag table) could optionally live in a reference file.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly identifies a specific product niche and includes an explicit 'Use when' trigger, but the action language is generic ('manage data, records, automate workflows') rather than concrete. It is clearly above the vague baseline but stops short of the specificity and trigger-term richness of the top anchors.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Send and schedule push notifications, manage registered devices, and view delivery status.'

Add natural trigger terms users would actually say, such as 'push notification', 'send a notification', or 'scheduled notification' alongside 'interact with Push by Techulus data'.

Tighten the 'when' clause to name the concrete scenarios, e.g. 'Use when the user wants to send, schedule, or inspect Push by Techulus push notifications.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Push by Techulus integration') but the actions are generic and minimal — 'Manage data, records, and automate workflows' gives no concrete operations, matching the anchor for naming a domain with minimal/generic actions rather than specific ones.	2 / 5
Completeness	Both 'what' (Push by Techulus integration managing data, records, workflows) and 'when' ('Use when the user wants to interact with Push by Techulus data') are explicitly present, though the 'when' is somewhat broad and the 'what' lacks concrete specifics, matching the 'both present but could be more explicit' anchor.	4 / 5
Trigger Term Quality	It includes the product name and an explicit trigger clause ('Use when the user wants to interact with Push by Techulus data'), but 'interact with... data' is generic and misses natural synonyms or concrete terms users would say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Push by Techulus' gives it a clear niche with low conflict risk, but the generic surrounding verbs ('manage data, records') leave minor overlap with other data-management skills, fitting the 'mostly distinct, minor overlap' anchor rather than the fully-distinct 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/push-by-techulus/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.