CtrlK
BlogDocsLog inGet started
Tessl Logo

instantly-ci-integration

Configure CI/CD pipelines for Instantly.ai integrations with GitHub Actions. Use when setting up automated testing, deployment pipelines, or continuous validation of Instantly API integrations. Trigger with phrases like "instantly ci", "instantly github actions", "instantly pipeline", "instantly automated testing", "instantly ci/cd".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A highly actionable, well-sequenced CI/CD guide with strong validation checkpoints and error-recovery guidance. Its main weaknesses are verbosity from embedding multiple full files inline and the absence of bundle files to split that detail out.

Suggestions

Move the full integration test suite and the secondary deploy workflow into bundle files under references/ or scripts/, keeping only the primary CI workflow inline and linking out to the rest to reduce token bulk.

Split the large inline code blocks (workflow YAML, validate-types.ts, integration test suite) into separate bundle files with clearly signaled one-level-deep links from the Overview so navigation is explicit.

Fix the empty mock-server URL in the Overview ('Uses the mock server at ``') by filling in the URL (it already appears in the workflow env as https://developer.instantly.ai/_mock/api/v2) or removing the empty backticks to avoid a broken reference.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but embeds two complete YAML workflows, a full TypeScript validation script, a full 5-test integration suite, a deploy workflow, and a pre-commit hook all inline; much of this full-file code could be tightened or moved to bundle files. It is mostly efficient but not lean enough for the score-3 'every token earns its place' bar.

2 / 3

Actionability

Provides complete, executable, copy-paste-ready GitHub Actions YAML and TypeScript (workflows, validate-types.ts, integration tests, deploy with health check), matching the score-3 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced with validation checkpoints throughout (type check, lint, unit tests, integration tests, deploy health-check verify) and an Error Handling table giving cause→solution feedback loops, matching the score-3 anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a monolithic ~230-line SKILL.md with full-file code inline; sections are well-organized (avoiding score 1) but content that could be split into separate files is inline with no one-level-deep bundle references, and the under-50-lines sections-only exemption does not apply.

2 / 3

Total

10

/

12

Passed

Description

90%

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 description that clearly states its niche, supplies an explicit 'Use when' clause, and lists natural trigger phrases. The only weakness is that the capability list stays at the category level rather than enumerating concrete granular actions.

DimensionReasoningScore

Specificity

Names the domain and main action ('Configure CI/CD pipelines for Instantly.ai integrations with GitHub Actions') plus testing/deployment/validation use categories, but these are higher-level categories rather than the granular multi-action list (e.g. 'extract text, fill forms, merge documents') of the score-3 anchor.

2 / 3

Completeness

Explicitly answers both what ('Configure CI/CD pipelines...') and when ('Use when setting up automated testing, deployment pipelines, or continuous validation...') with explicit trigger guidance, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Provides explicit, natural trigger phrases a user would say ('instantly ci', 'instantly github actions', 'instantly pipeline', 'instantly automated testing', 'instantly ci/cd'), giving good coverage of likely real-world phrasings.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to Instantly.ai integrations with all triggers prefixed by 'instantly', making it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.