can you solve this for us: what should we call it? So the whole agent store got the team thinking and we will definitely do it, but what we will likely change is that instead of Agents, we will have a skill shop for Agento.

It works just like a prebuilt agent but we'll call it skills. What the skill approach allows on top is that you can as a technical person download the skill and run them locally, and we can also easily publish other open source skills that agento can execute.

So Agento will then be a simple to use, consumer agent that can have many skills for whatever the user wants to do. Thoughts? André Jørgensen - OSL1 (sentry.co) [5:30 PM]

isnt claude. calling smth skills as well? [5:31 PM] and wasnt the skills more like .md docs of how to do smth? i dunno. never got into it. [5:31 PM] what about calling it smth else than skills? just to differentiate ? Felix Wunderlich [5:33 PM]

yea claude does it but I think skills will be quite big going forward. it's what you said, like a custom instruction, in the end more like a very advanced prompt as far as I understood it. but for a non technical user the concept of a skill is quite cool I think - ah you want to teach agento to do this, install this skill kind of André Jørgensen - OSL1 (sentry.co) [5:38 PM]

Assessment The concern about “Skills” naming is valid. Claude has a major feature called “Skills” launched in late 2025, which allows users to extend Claude with modular, reusable task components. These Skills can be created by Anthropic or custom-built, and they work similarly to what André describes—packaged capabilities that Claude can invoke during conversations.claude+1[youtube] Naming Collision Risk The overlap is significant because: Claude Skills are defined by schemas describing inputs, outputs, and permissions[infoq] They’re designed to be discoverable and executable by the agent—the same concept Agento is pursuing[lucek] The “Agent Skills” terminology is also emerging as a broader packaging standard in the AI ecosystem, with .SKILL.md files defining workflows and instructions[lucek] Using “Skills” could cause confusion with Claude’s feature, especially since technical users are the target audience and likely familiar with Claude’s terminology. Alternative Naming Ideas TermProsConsModulesTechnical, suggests composabilityGeneric, overused in softwareAbilitiesClose synonym, intuitiveSlightly vagueTalentsUnique, memorableSlightly informalKitsSuggests downloadable packagesMay imply bundled toolsPowersConsumer-friendly, differentiatedPerhaps too playful for B2BCraftsUnique, suggests expertiseUnfamiliar in tech context

Recommendation The pivot from “Agents” to downloadable, locally-runnable capabilities is smart for differentiation and developer appeal. However, given Claude’s prominent use of “Skills,” consider alternatives like “Kits” (emphasizes the downloadable/package aspect) or “Abilities” (close meaning but not trademarked by a competitor). The key is finding something that signals modularity and capability without direct overlap with Anthropic’s naming. support.claude.com What are Skills? | Claude Help Center https://support.claude.com/en/articles/12512176-what-are-skills YouTube | GritAI Studio I Tried Anthropic's NEW Claude Skills Feature (You Need to See This) InfoQ Anthropic Introduces Skills for Custom Claude Tasks Anthropic has unveiled a new feature called Skills, designed to let developers extend Claude with modular, reusable task components. https://www.infoq.com/news/2025/10/anthropic-claude-skills/ Adam Łucek Agent Skills - Yet Another Tool Standard? The new standard for packaging reusable workflow capabilities for filesystem-based agent harnesses. https://lucek.ai/blogs/agent-skills.html [5:39 PM] its just you dont want to be seen as a copycat. a me2. by having a different name. you also build your own identitity sort of. [5:41 PM] Screenshot 2026-01-23 at 17.40.37.png [5:42 PM] “premade” “readymade” “template” “off-the-shelf” [5:42 PM] Here are some more abstract and original options that could work well with the “Agento” brand: Single-Syllable / Punchy Moves — implies action, like chess moves or dance moves Plays — suggests strategy and execution Runes — mystical, suggests encoded capabilities Sparks — energy, activation, lightweight feel Glyphs — abstract symbols that unlock functionality Two-Syllable / Brandable Facets — different “sides” of Agento’s capability Aspects — similar vibe, modular personality traits Motifs — patterns that can be applied/reused Vectors — directional, technical, implies purpose Prisms — refracts one agent into many capabilities Playful / Consumer-Friendly Tricks — what Agento “knows how to do” Feats — accomplishments, things it can achieve Perks — benefits you add on Boosts — upgrades for your agent Invented / Coined Agentlets — mini-agents, ties directly to brand Gentos — derived from Agento, unique and ownable Actums — from “actum” (Latin: deed/act) Praxes — from Greek “praxis” (practice/action) My Picks If aiming for something memorable and brandable that sounds native to “Agento”: Moves — simple, intuitive, action-oriented (“Install new moves for Agento”) Gentos — completely ownable, brand-aligned (“Browse the Gento shop”) Facets — elegant, suggests depth without complexity What vibe are you going for—more technical/developer-focused or consumer-friendly? [5:43 PM] I would explore this a bit. or go with skills. it might just become like a insustry name for instructions AI / Bots do. Felix Wunderlich [3:56 PM]

Thanks for that mate, it's for sure a valid concern, I'll run this by the team and give it a longer think as well. My spotaneous feeling is either to stay with the agents since it does make sense, or go with the skills since this might become a more generic term and even replace prompts / agents to some extent. (edited) André Jørgensen - OSL1 (sentry.co) [5:17 PM]

Skill is tennis. Skill is painting. Etc. A series of steps is not a skill sort of. Recipe, job to be done. Smth. I dunno maybe a new word will emerge? Feed our convo to an ai and see what it thinks maybe? Felix Wunderlich [3:33 PM]

yea I do get your point, it's def not 100% but I feel like skills are everywhere rn and hot and my idea is to ride that wave. I'd market it like that, a luxury goods researcher, a sales outreacher, you can be quite playful with it in the communication, adding a skill, like leveling up the base agento with this kind of skill, now he's great at it. [3:34 PM] I did check with claude and it kinda did like it, but I'll do some testing on the communication and show you, let's see then what you think André Jørgensen - OSL1 (sentry.co) [8:29 PM]

Yeh tht makes sense. A research skill, a sales skill. But stargazer cron job is not a skill. Its a recipe. A skilled person has many recipes. It semantics

This is a great discussion to weigh in on. André's semantic point is sharp—a "skill" in the traditional sense (tennis, painting) refers to embodied expertise developed over time, not a packaged recipe or workflow. Let me offer some perspective.

The Semantic Tension

André is right that there's a mismatch: Claude's Skills and the broader "Agent Skills" standard are essentially packaged workflows—instructions, scripts, and resources that an agent can load and execute. A "stargazer cron job" isn't really a skill in the human sense; it's a recipe or procedure. A skilled person has many recipes, but the recipes themselves aren't the skill.¹

However, Felix's counterpoint is also valid: "skills" is becoming industry shorthand for modular agent capabilities, and riding that wave has marketing advantages.²³

Naming Considerations

Term	Pros	Cons
Skills	Industry momentum; intuitive for consumers ("add a sales skill")	Claude collision risk; semantic mismatch with true expertise
Recipes	Matches what they actually are (step-by-step instructions); unique in AI space	Feels domestic/culinary; less "tech"
Moves	Action-oriented; chess/strategy connotations; short	Vague; less immediately clear
Kits	Emphasizes downloadable/package aspect; developer-friendly	May imply bundled tools rather than capabilities
Plays	Strategic; playbook metaphor works well	Could be confused with media playback
Routines	Technically accurate; common in automation	Sounds boring; "routine" has negative connotations

A Possible Middle Path

Given André's semantic critique, consider "Plays" or "Playbook" as the framing:

"Install a new play for Agento" (like a football playbook)
"The Agento Playbook Shop"
A play is a defined sequence of actions to achieve an outcome—semantically closer to what these actually are
Unique in the AI agent space; not claimed by Claude/OpenAI

Alternatively, lean into the recipe metaphor: "A skilled chef has many recipes." The agent (Agento) is the skilled entity; what you're downloading are recipes it can execute. This would differentiate clearly from Claude's "Skills" while being semantically honest .

Recommendation

If brand differentiation matters (and it should for a startup), avoid "Skills" despite the industry momentum—you'll constantly be explaining "not like Claude Skills." Plays, Recipes, or even Routines are more defensible and semantically accurate. If you want something playful and brand-aligned, Gentos (as suggested in the thread) is ownable and ties directly to "Agento".⁴ ⁵⁶⁷⁸⁹¹⁰¹¹¹²¹³¹⁴¹⁵

⁂

what about sequence? Sequence library. Then you use Agents with certain skills that are tuned to handle these sequences better than other agents. Dev agent. would do stargazer sequence better than marketing agent etc

This is a clever reframe that actually solves André's semantic objection. Here's why it works:

Why "Sequence" Fits Better Semantically

André nailed the problem: a "skill" is embodied expertise, but what you're packaging is a series of steps—which is literally a sequence. The word is honest about what the thing actually is.¹⁶¹⁷

The hierarchy you're proposing:

Agent (Dev Agent, Marketing Agent) = the skilled entity with domain expertise
Sequence = the recipe/workflow the agent executes
Skills = the agent's underlying capabilities that make it good at certain sequences

This maps cleanly to: "A skilled chef (agent) has many recipes (sequences). The Dev Agent runs the stargazer sequence better because it has the right skills."

Competitive Landscape

Term	Used By	Collision Risk
Skills	Claude (Anthropic), emerging standard	High
Workflows	Zapier, n8n, most automation tools	Medium
Sequences	Sales tools (Outreach, Apollo) but NOT AI agents	Low
Routines	Generic automation	Low

"Sequence" is surprisingly unclaimed in the AI agent space. The sales/outreach world uses it heavily, but that's actually good—it signals "automated multi-step process" to users without direct competitor collision.¹⁸¹⁹

Branding Potential

"Sequence Library" or "Sequence Shop" sounds professional and technical
"Run a sequence" is intuitive—everyone understands it
Pairs well with Agento: "Agento runs sequences. Pick the right agent for the job."
Opens up nice UX language: "Start sequence," "Sequence complete," "Sequence failed at step 3"

One Consideration

"Sequence" is more B2B/developer-coded than consumer-playful. If you want mass-market appeal, it's slightly colder than "Skills." But for a product where technical users can download and run locally, that might be a feature, not a bug.

Verdict: This is semantically clean, competitively differentiated, and creates a sensible agent-skill-sequence hierarchy. Strong option. ²⁰²¹²²²³²⁴²⁵²⁶²⁷²⁸²⁹³⁰

⁂

what about workflow? vs sequence? vs routines

Here's a direct comparison based on how these terms are actually used in the market:

Head-to-Head Comparison

Aspect	Workflow	Sequence	Routines
Market saturation	Extremely high (Zapier, n8n, Workato, Make)	Medium (sales tools only)	Low
Implied complexity	Complex, branching, multi-system	Linear, step-by-step	Simple, recurring
Associations	Enterprise, IT, ops teams	Sales outreach, CRM	Habits, daily tasks, home automation
Connotation	Professional but generic	Methodical, ordered	Mundane, repetitive
Technical users	Familiar, maybe too familiar	Fresh in AI context	Neutral

The Problem with "Workflow"

"Workflow" is essentially owned by the automation industry—Zapier calls them "Zaps," but everyone else uses "workflows". Using it would make Agento sound like another n8n or Make.com clone rather than something new. It's also associated with complex enterprise processes, which may be heavier than what you're going for.³¹³²³³

Why "Sequence" Has an Edge

In the CRM/sales world, "sequence" specifically means a linear series of automated steps (emails, tasks, follow-ups). The key distinction from HubSpot's terminology: Sequences are simpler and more personal than Workflows. That actually maps well to Agento's concept—downloadable, focused, single-purpose automations.³⁴³⁵³⁶

It's also not yet claimed in the AI agent space, which gives you room to own it.³⁵

The Case Against "Routines"

"Routine" carries baggage—it implies boring repetition ("my morning routine"). It's also used in home automation (Alexa Routines, Google Home Routines), which pulls it toward consumer IoT rather than AI agents. The word itself suggests something you do every day, not a one-off powerful action.

Verdict

If you want...	Choose
Maximum differentiation from automation tools	Sequence
Developer credibility but risk of blending in	Workflow
Consumer simplicity but "boring" vibes	Routines

Sequence wins for Agento because it's semantically honest (a series of steps), unclaimed in AI agents, and lighter than "workflow" without the negative connotations of "routine." ³⁷³⁸³⁹⁴⁰⁴¹⁴²⁴³⁴⁴⁴⁵

⁂

workflow is generic. dont worry about marketing.

Fair point. Stripping away the marketing lens, here's the functional comparison:

Pure Semantics

Term	What it literally means
Workflow	A complete process from start to finish, potentially with branches, conditions, parallel paths
Sequence	Steps executed in order, one after another (A → B → C)
Routine	Something repeated regularly, habitual

Which Matches What Agento Actually Does?

If your packaged capabilities are:

Linear step-by-step executions → Sequence fits best
Branching logic with conditionals → Workflow fits best
Scheduled/recurring tasks → Routine fits best

Most real-world use cases are probably a mix. A "stargazer cron job" is technically a routine (recurring) that runs a sequence (steps). A "sales outreach" might be a workflow (if/then branching based on responses) or a sequence (fixed steps).

The Honest Answer

Workflow is the most technically accurate umbrella term because it covers all patterns—linear, branching, conditional, recurring. "Sequence" is a subset of workflow. "Routine" implies scheduling that may not always apply.⁴⁶⁴⁷

If you don't care about differentiation and just want the right word: Workflow is the correct generic term for "a series of automated steps an agent executes."

The only functional reason to avoid it: if Agento's capabilities are intentionally simpler than full workflows (no branching, no conditionals), then "Sequence" is more honest about the scope.

⁂

eonist/agento-skill-term.md

Select an option

No results found

Select an option

No results found

can you solve this for us: what should we call it? So the whole agent store got the team thinking and we will definitely do it, but what we will likely change is that instead of Agents, we will have a skill shop for Agento.

The Semantic Tension

Naming Considerations

A Possible Middle Path

Recommendation

what about sequence? Sequence library. Then you use Agents with certain skills that are tuned to handle these sequences better than other agents. Dev agent. would do stargazer sequence better than marketing agent etc

Why "Sequence" Fits Better Semantically

Competitive Landscape

Branding Potential

One Consideration

what about workflow? vs sequence? vs routines

Head-to-Head Comparison

The Problem with "Workflow"

Why "Sequence" Has an Edge

The Case Against "Routines"

Verdict

workflow is generic. dont worry about marketing.

Pure Semantics

Which Matches What Agento Actually Does?

The Honest Answer

eonist/agento-skill-term.md

can you solve this for us: what should we call it? So the whole agent store got the team thinking and we will definitely do it, but what we will likely change is that instead of Agents, we will have a skill shop for Agento.

The Semantic Tension

Naming Considerations

A Possible Middle Path

Recommendation

what about sequence? Sequence library. Then you use Agents with certain skills that are tuned to handle these sequences better than other agents. Dev agent. would do stargazer sequence better than marketing agent etc

Why "Sequence" Fits Better Semantically

Competitive Landscape

Branding Potential

One Consideration

what about workflow? vs sequence? vs routines

Head-to-Head Comparison

The Problem with "Workflow"

Why "Sequence" Has an Edge

The Case Against "Routines"

Verdict

workflow is generic. dont worry about marketing.

Pure Semantics

Which Matches What Agento Actually Does?

The Honest Answer

Footnotes