Needs review
Project:
Drupal AI Initiative
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Nov 2025 at 17:43 UTC
Updated:
12 Feb 2026 at 20:23 UTC
Jump to comment: Most recent
Claude recently launched Agent Skills for use on the platform, which they describe as:
Claude can now use Skills to improve how it performs specific tasks. Skills are folders that include instructions, scripts, and resources that Claude can load when needed.
Claude will only access a skill when it's relevant to the task at hand. When used, skills make Claude better at specialized tasks like working with Excel or following your organization's brand guidelines.
...
Skills are:
- Composable: Skills stack together. Claude automatically identifies which skills are needed and coordinates their use.
- Portable: Skills use the same format everywhere. Build once, use across Claude apps, Claude Code, and API.
- Efficient: Only loads what's needed, when it's needed.
- Powerful: Skills can include executable code for tasks where traditional programming is more reliable than token generation.
Create a Claude skill that the Drupal AI initiative team can use to assist with tasks such as making consistently designed presentations and marketing materials or editing content to ensure it has a consistent voice.
Comments
Comment #2
kristen polThanks for creating this issue.
Note: this was discussed during the weekly Drupal AI Marketing meeting a couple of hours ago.
Comment #3
kristen polMoving to marketing
Comment #4
alex ua commented@kristen-pol - I selected the code component because this will ideally result in code, ie at the very least a skills folder, skills.md file, and any assets we include.
Comment #5
kristen polComment #6
alex ua commentedOkay, I've created an initial Drupal Brand Skill and uploaded it to github: https://github.com/zivtech/drupal-brand-skill
Let me say: it's really incredibly annoying that the design firm delivered the docs in such an inaccessible form. But whatever, I had Claude Code and some nifty MCPs to help me.
@kristen-pol - take a look and let me know what you think!
Comment #7
kristen polFair. I'm not sure who should be reviewing this tbh.
I'll post in the dev channel.
Comment #8
kristen polI've pinged marketing and dev channels.
Comment #9
dunx commentedI'd suggest the group in change of the Drupal brand (if that's not an obvious suggestion). Perhaps we could add some 'testing' notes here @alex.
There's a readme in the github, but without any context it's difficult to know what it is, where to start and how to progress.
Comment #10
alex ua commented@dunx, I've updated the readme to include more context and instructions for how to use it.
I also created an example you can see.
Here's Moshe Weitzman's very retro looking Drupal timeline: https://weitzman.github.io/drupal25-timeline/
Here's a version of the timeline with the skill applied: https://zivtech.github.io/drupal-timeline-viz/
You can see the changes it made in the pull request here: https://github.com/weitzman/drupal-timeline/pull/59
Comment #11
alex ua commentedComment #12
alex ua commentedJust noting that this is a general brand skill and should be useful beyond the AI initiative.
Comment #13
mandclu commentedIt's worth noting that CrafterCMS recently announced the availability of their own Cursor AI skill. Our competitors are already in this space and getting feedback from real users, which means we are already behind. I would suggest that we prioritize adopting *something* as our initial version, with an intent to iterate quickly as Drupal developers start using it and provide feedback.
Comment #14
revagomes commentedI believe this ones will be useful for a couple of people:
https://github.com/Omedia/drupal-skill/
Comment #15
alex ua commentedWe should probably create a directory of Drupal-focused skills. There are already a ton listed on skills.sh: https://skills.sh/?q=drupal
I've been using Jaime's Drupal setup skill: https://github.com/jamieaa64/Drupal-DDEV-Setup-Claude-Skill
I've also been using a couple of the contribute skills, primarily scottfalconer's Drupal Contribute Fix skill , but I'd love to see more collaboration and less overlap. It would be great to turn some of these into "official" skills that push the community to collaborate on these skills instead of competing. For example, shouldn't we have *one* skill that helps people contribute to contrib and core?
Anyway, that's a bit off topic for this. I will say that I separated out the slide building tooling and put it into a generalized skill that gets called from this one-- ai presentation toolkit, but I still don't have it working great and started before skills.sh was launched so I'll likely look around for a better option. Slide building is one giant PITA!