CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twig-development

Use when authoring, refactoring, debugging, or optimizing Twig templates across any PHP framework or CMS (Symfony, Drupal, Craft CMS, Prestashop, FOSSBilling, Timber/WordPress, Grav). Covers Twig 3.x syntax, defensive strict-variables handling, template inheritance and block architecture, macros, filters, components, auto-escaping, sandboxing, and performance optimization. Excludes framework-specific PHP controller routing or backend database queries.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with excellent concrete code examples and a genuinely valuable treatment of strict-variables semantics and escaping security. It is held back by tutorial-style re-explanation of basic Twig concepts and by being a monolithic single file where reference material should be split out.

Suggestions

Move the standard filter reference (section 6) and basic engine fundamentals (section 1: delimiters, whitespace control, caching pipeline) into a references/ file, keeping SKILL.md focused on the defensive rules, invariants, and checklist that Claude cannot derive on its own.

Trim or remove explanations of concepts Claude already knows (what Twig is, include/embed/use basics, macro basics, |trim/|replace/|date behavior) to cut token cost without losing the skill's distinctive value.

Add an explicit feedback loop to the checklist, e.g., 'run the lint command; if compilation fails, fix the reported template and line and re-run until clean', to upgrade workflow clarity for the debugging/refactoring use cases the description advertises.

DimensionReasoningScore

Conciseness

Section 1 ("Twig is a modern, fast, and secure template engine for PHP", delimiters, whitespace trimming, the caching pipeline) and section 6's standard filter reference ("|trim: Strips leading/trailing whitespace") re-explain Twig knowledge Claude already has. Valuable non-obvious material (the ?? vs |default falsy-semantics table, strict-variable rules, the final checklist) is interwoven, so it sits at "mostly efficient but includes some unnecessary explanation" rather than "noticeably verbose".

3 / 5

Actionability

Guidance is fully executable throughout: complete copy-paste-ready base layout, embed component, and macro templates; a concrete bug-vs-fix pair for "product.stock_control|default(true)" vs "?? true"; sandbox PHP configuration; and the specific command "php bin/console lint:twig templates/". Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Not a procedural skill, but sections build logically from fundamentals to security and close with an explicit validation checklist ("Strict Variables Audit", "XSS Audit", "Syntax Compilation Check") including a lint command. It is not 5 because there is no error-recovery feedback loop (e.g., 'if lint fails, fix and re-run') and no ordered procedure for the debugging/refactoring scenarios the description promises; not 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The body has good section structure but is a single ~350-line file with no bundle files at all — content such as the section 6 filter reference and the long layout/component examples "clearly belongs in separate files" that is currently inlined. It is not 4 because there is no reference split whatsoever, and the under-50-line simple-skill exception plainly does not apply; not 2 because the section headers and tables provide solid in-file navigation.

3 / 5

Total

15

/

20

Passed

Description

87%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 description with an explicit 'Use when' trigger clause, a concrete topic coverage list, and a helpful exclusion boundary. Its only weaknesses are generic action verbs and the absence of a few natural trigger variants such as the '.twig' file extension.

DimensionReasoningScore

Specificity

Lists a comprehensive, topic-specific coverage set ("defensive strict-variables handling, template inheritance and block architecture, macros, filters, components, auto-escaping, sandboxing"), but the action verbs ("authoring, refactoring, debugging, or optimizing") are generic, so it stops short of the fully concrete-action anchor 5.

4 / 5

Completeness

Explicitly answers both questions: "Use when authoring, refactoring, debugging, or optimizing Twig templates..." (when, with concrete trigger activities) and "Covers Twig 3.x syntax, defensive strict-variables handling..." (what), plus an exclusion clause. This clearly matches the anchor-5 example structure; it is not 4 because the 'when' guidance is explicit rather than merely present.

5 / 5

Trigger Term Quality

"Twig templates" plus the enumerated frameworks ("Symfony, Drupal, Craft CMS, Prestashop, FOSSBilling, Timber/WordPress, Grav") are exactly what affected users would say, but natural variants like the ".twig" file extension and "template engine" phrasing are absent, matching "good keyword coverage; a few natural terms missing" rather than anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Twig templates" is a clear niche trigger, and "Excludes framework-specific PHP controller routing or backend database queries" explicitly fences off adjacent PHP skills, giving minimal conflict risk per anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/development-skills/twig-development/SKILL.md

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.