grammarly-ci-integration
Configure Grammarly CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Grammarly tests into your build process. Trigger with phrases like "grammarly CI", "grammarly GitHub Actions", "grammarly automated tests", "CI grammarly".
What this skill does
# Grammarly CI Integration
## Overview
Set up CI/CD for Grammarly text analysis integrations: run unit tests with mocked grammar check and suggestion responses on every PR, validate live API connectivity for text scoring on merge to main. Grammarly's Text API provides writing quality scores, grammar corrections, and tone detection, so CI pipelines verify content quality gates, documentation linting, and automated writing feedback workflows.
## GitHub Actions Workflow
```yaml
# .github/workflows/grammarly-ci.yml
name: Grammarly CI
on:
pull_request:
paths: ['src/**', 'docs/**', 'tests/**']
push:
branches: [main]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm test -- --reporter=verbose
integration-tests:
if: github.ref == 'refs/heads/main'
needs: unit-tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm run test:integration
env:
GRAMMARLY_CLIENT_ID: ${{ secrets.GRAMMARLY_CLIENT_ID }}
GRAMMARLY_CLIENT_SECRET: ${{ secrets.GRAMMARLY_CLIENT_SECRET }}
```
## Mock-Based Unit Tests
```typescript
// tests/grammarly-service.test.ts
import { describe, it, expect, vi } from 'vitest';
import { checkDocumentation } from '../src/grammarly-service';
vi.mock('../src/grammarly-client', () => ({
GrammarlyClient: vi.fn().mockImplementation(() => ({
checkText: vi.fn().mockResolvedValue({
overall_score: 87,
alerts: [
{ type: 'grammar', message: 'Subject-verb disagreement', offset: 12, length: 5, replacements: ['are'] },
{ type: 'clarity', message: 'Consider simplifying', offset: 45, length: 20, replacements: ['use'] },
],
tone: { formal: 0.8, confident: 0.7 },
}),
getSuggestions: vi.fn().mockResolvedValue({
suggestions: [{ text: 'Rephrase for clarity', category: 'engagement' }],
}),
})),
}));
describe('Grammarly Service', () => {
it('checks documentation quality and returns score', async () => {
const result = await checkDocumentation('The data is ready for review.');
expect(result.overall_score).toBeGreaterThan(80);
expect(result.alerts).toHaveLength(2);
});
});
```
## Integration Tests
```typescript
// tests/integration/grammarly.integration.test.ts
import { describe, it, expect } from 'vitest';
const hasCredentials = !!process.env.GRAMMARLY_CLIENT_ID;
describe.skipIf(!hasCredentials)('Grammarly Live API', () => {
it('analyzes text via Text API', async () => {
const tokenRes = await fetch('https://api.grammarly.com/v1/oauth/token', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
client_id: process.env.GRAMMARLY_CLIENT_ID,
client_secret: process.env.GRAMMARLY_CLIENT_SECRET,
grant_type: 'client_credentials',
}),
});
expect(tokenRes.status).toBe(200);
const { access_token } = await tokenRes.json();
expect(access_token).toBeDefined();
});
});
```
## Error Handling
| CI Issue | Cause | Fix |
|----------|-------|-----|
| `401 Unauthorized` | Invalid client credentials | Regenerate at developer.grammarly.com |
| OAuth token expired | Token TTL exceeded | Implement token refresh before each test run |
| Score below threshold | Content quality regression | Set minimum score in CI config (e.g., 75) and fix flagged alerts |
| Rate limit (429) | Too many text check requests | Batch text submissions and add throttling |
| Empty suggestions | Text too short for analysis | Ensure test inputs are at least 50 characters |
## Resources
- [Grammarly Developer API](https://developer.grammarly.com/)
- Grammarly Text API Reference
- [GitHub Actions Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets)
## Next Steps
For deployment, see `grammarly-deploy-integration`.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.