generated: '2026-08-26'
method: generated
source: >-
  Authored from openapi/namely-api-openapi.json and the developers.namely.com articles. Every
  operationId referenced in these skills was grepped against the published contract before being
  written; none is invented.
name: Namely Agent Skills
description: >-
  Two packaged Agent Skills for the Namely API v1, covering its two genuinely distinct jobs -
  reading the employee directory, and changing the profile schema. Namely publishes no skills,
  AGENTS.md or agent instructions of its own; these are generated by API Evangelist. They are
  deliberately heavy on warnings because the Namely contract omits every failure mode: no 4xx/5xx
  responses, no idempotency, no dry-run, and no delete for the highest-consequence write in the
  API.
provider_published_skills: false
provider_published_skills_note: >-
  No skills/, AGENTS.md, llms.txt tool list or agent instructions were found on
  developers.namely.com or in github.com/namely.
skills:
  - name: namely-employee-directory-sync
    file: namely-employee-directory-sync.md
    consequence: read-only
    operations:
      - GET_companies-info
      - GET_profiles
      - GET_profiles-id
      - GET_job_titles
      - GET_groups
      - GET_teams
    summary: >-
      Page the employee directory within the 100 req/min limit on GET /profiles, resolve
      relationships from the JSON API sideload rather than by refetching, and handle the 406
      throttle status that generic clients misread.
  - name: namely-profile-schema-management
    file: namely-profile-schema-management.md
    consequence: high
    operations:
      - GET_profiles-fields
      - GET_profiles-fields-id
      - GET_profiles-fields-sections
      - GET_profiles-fields-sections-id
      - POST_profiles-fields
      - PUT_profiles-fields-id
      - PUT_profiles-fields-sections-id
    summary: >-
      Inspect and extend the tenant's profile schema. Gated on human confirmation because
      POST /profiles/fields has no delete, no rename of the underlying key, no dry-run and no
      idempotency key.
not_written:
  - reason: >-
      No skill was written for profile creation/update (POST /profiles, PUT /profiles/{id})
      despite these being marquee operations. Both are irreversible - no delete, no revision
      history, no rollback - and they write PII including SSN. A packaged skill for them would be
      an instruction to take an unrecoverable action on real employee records, which is not
      appropriate to ship without a provider-published reversal path.